^ This + Probably should make a general README.md with that info and seperate it from the specification so people stumbling onto this know what they're reading. It's important people get a good idea without having to necessarily go to the website or read the full spec

These are great ideas to improve the project’s usability and community engagement. I’d especially support adding:
• Clear instructions on how to contribute (including where to submit issues and pull requests) to lower the barrier for new contributors.
• Links to deeper documentation, including design rationale and specification details, as well as pointers to active community channels (forums, chat, mailing lists).
• Information about licensing, governance, and any community codes of conduct or legal guidelines to clarify expectations.

If the maintainers agree, I’d be happy to help draft some of these sections or gather relevant links from the specification and associated repos.