sync-website

To keep GitHub Pages website docs in sync, you audit canonical source files like README and code directories, then edit website/index.html to match existing HTML patterns, verify item counts, and push to main for deployment.

Your marketing website shows stale features because website/index.html is not automatically linked to source code; you must manually read canonical sources, update the corresponding HTML blocks, and verify structure to eliminate incorrect public documentation.

The best way to update installation instructions is to read the authoritative source files, edit the install cards in website/index.html while preserving CSS and markup, verify counts, and push to main to trigger the GitHub Pages deploy workflow.

Yes, you can auto-deploy website content changes by editing website/index.html to reflect the current codebase and pushing to main, which relies on the repository's existing GitHub Pages workflow to publish the update.

To verify website structure and item counts, review the edited website/index.html after applying changes, confirming that features, CLI references, agents tables, and install cards match the canonical sources before pushing to main.

You should avoid this approach if your website does not use static HTML files hosted on GitHub Pages, as it specifically targets editing website/index.html patterns and relies on that specific deployment workflow.