Contribute

The spec is open on GitHub. Issues, pull requests, and even straight-up disagreements are welcome. Three rules.

1. Cite your sources

Every page lists at least one source. If you are adding or changing a claim, link the standard, the official documentation, or the maintained reference behind it. No source, no merge.

2. Stay platform-agnostic

The spec describes outcomes, not implementations. “Set Content-Security-Policy” is in scope. “Add this to your next.config.mjs” is not — link out to platform docs instead.

3. Be honest about status

Required means the web platform breaks without it. Recommended means a modern site should do it. Optional means it depends. Avoid means it is outdated or harmful. If a status is wrong, fix it — with reasoning in the PR.

How to propose a change

1. Open an issue describing the topic, gap, or fix.
2. For a new spec page, copy an existing file in src/content/spec/<category>/ and adjust front-matter.
3. Run npm run dev locally on port 31337 and check the page renders.
4. Open a PR. The CI will type-check, build, and lint links.

Repository

https://github.com/jdevalk/specification.website