feat(website): add VCS landing pages and sitemap alias

[benvinegar]

Summary

• add substantive /git/, /jujutsu/, and /sapling/ workflow landing pages
• publish matching .md variants for coding agents and answer engines
• add canonical metadata, Open Graph tags, structured data, cross-links, and sitemap entries
• publish Astro's generated URL set at conventional /sitemap.xml and point robots.txt at it

Verification

• bun run --cwd website check
• bun run --cwd website build
• verified each HTML page, Markdown variant, and sitemap entry in website/dist
• cmp website/dist/sitemap.xml website/dist/sitemap-0.xml

Platform: Linux

This PR description was generated by Pi using GPT-5.6 Sol

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
hunk-web	Ready	Preview	Sep 2, 2026 2:37am UTC

[greptile-apps]

Greptile Summary

This PR publishes Astro’s generated URL set at /sitemap.xml, updates crawler and deployment references to use that path, and retains the original sitemap outputs.

• Adds a post-build script that copies sitemap-0.xml to sitemap.xml.
• Updates robots.txt and deployment verification for the new alias.
• Adds an empty changeset for the website-only change.

Confidence Score: 4/5

The PR appears safe to merge, with the non-blocking concern that the new production-build behavior lacks required automated coverage.

The alias generation is compatible with the current sitemap output and build environments, but filename or artifact regressions would currently be detected only through manual verification.

Files Needing Attention: website/package.json, website/scripts/publish-sitemap-alias.ts

Important Files Changed

Filename	Overview
website/scripts/publish-sitemap-alias.ts	Adds the fixed-path sitemap copy operation; behavior is straightforward but lacks the repository-required automated coverage.
website/package.json	Extends every website production build with the sitemap alias publication step.
website/public/robots.txt	Updates the advertised sitemap URL to the newly generated conventional alias.
website/src/content/docs/docs/help/deployment.md	Updates the deployment smoke check to verify the new sitemap URL.

Prompt To Fix All With AI

### Issue 1
website/package.json:7
**Sitemap alias lacks test coverage**

The production build now relies on fixed sitemap output paths and filenames without an automated test covering the generated alias. A regression in the Astro output or copy behavior can fail deployment or publish an incorrect sitemap without being caught by the test suite.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix(website): publish sitemap.xml" | Re-trigger Greptile}

[greptile-apps]

Sitemap alias lacks test coverage

The production build now relies on fixed sitemap output paths and filenames without an automated test covering the generated alias. A regression in the Astro output or copy behavior can fail deployment or publish an incorrect sitemap without being caught by the test suite.

Context Used: guidelines.mdc Cursor rule (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: website/package.json
Line: 7

Comment:
**Sitemap alias lacks test coverage**

The production build now relies on fixed sitemap output paths and filenames without an automated test covering the generated alias. A regression in the Astro output or copy behavior can fail deployment or publish an incorrect sitemap without being caught by the test suite.

**Context Used:** guidelines.mdc Cursor rule ([source](https://github.com/modem-dev/modem/blob/main/.cursor/rules/guidelines.mdc))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!