chore: add UTM parameters to altimate.ai website links

[anandgupta42]

Summary

Tags the 6 user-facing links to the marketing website (utm_source=altimate-code, utm_medium=github|docs|marketplace) so traffic from GitHub/npm/docs surfaces is attributable in PostHog/GA4. Part of opening the product→website funnel across all three repos (companions: AltimateAI/vscode-dbt-power-user#2056, AltimateAI/vscode-altimate-mcp-server#430).

• CONTRIBUTING.md + github/README.md Discord/site links (GitHub surfaces)
• docs/ benchmarks link + mkdocs social link (render on help.altimate.ai/code)
• sdks/vscode/README.md ×3 (marketplace listing)

Deliberately untouched (functional URLs, not marketing links): provider HTTP-Referer headers, $schema/config.json/theme.json URLs, github/index.ts API base URL, CHANGELOG, and other Altimate properties (help.altimate.ai, altimate.sh, altimate.studio).

🤖 Generated with Claude Code

---

Summary by cubic

Add UTM parameters to six altimate.ai links so traffic from GitHub, docs, and Marketplace is attributed in PostHog/GA4. Updated links in CONTRIBUTING, docs (benchmarks + mkdocs social), GitHub Action README, and VS Code extension README; left non-marketing and service URLs unchanged.

^{Written for commit 1366b01. Summary will update on new commits.}

Summary by CodeRabbit

• Documentation
  • Updated project, setup, and extension documentation links with tracking parameters.
  • Refreshed community and resource links across the documentation site and README files.
  • Added marketplace tracking information to extension introduction and prerequisite links.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1df5f534-decc-4202-9b2f-a754ab7fd63e

📥 Commits

Reviewing files that changed from the base of the PR and between 28caf71 and 1366b01.

📒 Files selected for processing (5)

• CONTRIBUTING.md
• docs/docs/getting-started/index.md
• docs/mkdocs.yml
• github/README.md
• sdks/vscode/README.md

---

📝 Walkthrough

Walkthrough

Documentation and README links now include UTM tracking parameters. The parameters identify the source and medium for links in contribution guidance, project documentation, GitHub, and the VS Code marketplace.

Changes

Tracking link updates

Layer / File(s)	Summary
Update documentation and README links CONTRIBUTING.md, docs/docs/getting-started/index.md, docs/mkdocs.yml, github/README.md, sdks/vscode/README.md	Contact, benchmark, Discord, and product links now include UTM tracking parameters for their publication context.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

I’m a rabbit with links in a row,
Adding UTM tags wherever they go.
GitHub and docs now tell,
Which paths served the link well.
Hop, track, and onward we grow!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the changes and scope but omits the required issue, change type, verification, and checklist sections.	Complete the template sections for the issue, change type, verification steps, and checklist; state whether screenshots are not applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: adding UTM parameters to altimate.ai links.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/utm-website-links

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 5 files

_{Re-trigger cubic}

[dev-punia-altimate]

🤖 Code Review — OpenCodeReview (Gemini) — No Issues Found

No supported files changed.

[ralphstodomingo]

Engineering review of head 1366b01c:

• Docs/README-only diff; every tagged URL curl-verifies 200 with params attached, and the website's analytics allowlist keeps utm_* (verified in src/lib/pageViewTracking.js on altimate-website), so attribution will record.
• Convention-checked against the merged companions (vscode-dbt-power-user#2056, vscode-altimate-mcp-server#430): identical param shape/order and per-product utm_source slug. utm_medium=github is a taxonomy refinement the other repos couldn't express (their READMEs double as marketplace listings; here the GitHub-rendered files are separate from sdks/vscode/README.md). Bare altimate.ai host is canonical — www. 301s to it — so this PR avoids the extra hop the earlier ones take.
• Exclusions are right: provider HTTP-Referer headers, $schema/config URLs, and the github/index.ts API base are functional URLs, correctly untouched.
• Heavy CI matrix legitimately SKIPPED by the changed-files gate for a markdown-only diff; all executed checks green. The failing Kilo check is the same "provider API key hit its rate limit" bot flake seen on the website PRs — not a finding.

Ship path: CONTRIBUTING.md/github/README.md are live at merge, docs/ auto-deploys via docs.yml, sdks/vscode/README.md reaches the Marketplace with the next v* release.