website-update

name	website-update
description	Update kickstart-cli.org content - release notes, version metadata, and command examples - and verify the changes against the tests that enforce them. Use when asked to update the website, changelog page, or showcased examples.

Website Update

Use When

Use this skill when changing what kickstart-cli.org shows: release notes, version metadata, positioning copy, or the showcased command examples. The site deploys automatically on release tags; this skill is about editing the source truthfully.

Where Things Live

• Copy and data: website/src/site/content.ts — defaultProjectMeta (version metadata), releaseNotes (the changelog), commandExamples (the showcased scaffolds), positioning points.
• HTML rendering: website/src/site/html.ts.
• Deploy-time metadata: injected from pyproject.toml by website/scripts/render-release-config.ts; local dev fallbacks live in website/wrangler.toml.

Enforced Invariants

These tests fail when the site drifts — keep them green instead of bypassing them:

• website/tests/content.test.ts: the current pyproject.toml version must have a releaseNotes entry, newest first, no duplicates.
• tests/integration/test_website_examples.py: every file path a command example advertises must really be generated by that command.
• website/tests/worker.test.ts: rendering, asset versioning, and changelog presence on the page.

Workflow

1. Edit website/src/site/content.ts (and CHANGELOG.md for release entries — the two carry the same story).

2. Verify both sides:

   cd website && bun run check && cd ..
   PYTHONPATH=$(pwd) poetry run python -m pytest tests/integration/test_website_examples.py -q
   

3. Preview locally with cd website && bun run dev when copy changes are substantial.

4. Merge; the release workflow deploys on the next stable tag (or retag the current release line for same-version copy fixes per docs/release-policy.md).

Rules

• Never list a file in commandExamples[].output that the generator does not emit; regenerate and check rather than guessing.
• Release notes are curated highlights, not commit dumps; keep entries to three or four load-bearing bullets.
• Version metadata moves together: defaultProjectMeta, releaseNotes, website/wrangler.toml dev vars, and render-release-config.ts defaults.

Report Back

Report which sections changed, the test commands run with their results, and whether the change needs a new version or a same-version retag.