Contributing overview
This site only works if people write things down. Across years of the community, only a handful of people have documented what they know — so the single most valuable thing you can do is add or improve a page.
The contribution model
Section titled “The contribution model”- The source is open in the GitHub repository.
- Anyone can contribute by editing Markdown and opening a pull request — you do not need repo access.
- Core contributors who help maintain the site get direct access and review incoming pull requests.
- Writers are a first-class need. Plenty of people have deep knowledge but find it hard to write up clearly — pairing a knowledgeable person with a strong writer is an explicit goal. You don’t have to be both.
Ways to help
Section titled “Ways to help”- Fill in a stub. Pages flagged stub in the sidebar already have an outline — the easiest way in.
- Fix what’s wrong or unclear. Small corrections matter; use the Edit link at the bottom of any page.
- Write something new. Found a gap? Add a page in the right discipline.
- Improve examples. Worked examples and sample assets are especially valuable.
Before you write
Section titled “Before you write”A few pages worth reading first:
- Writing docs — how to structure a page that’s actually useful.
- Style guide — voice, tone, and conventions.
- Pull-request process — what happens after you open a PR.
House rules
Section titled “House rules”- Quality over volume. The aim is genuinely useful material, not re-feeding people what an LLM could already tell them. A flood of low-value pages would just recreate the problem this site exists to solve.
- Respect the EULA. No de-binarization tools or workflows (e.g. DeODOL), and no redistributing other people’s assets.
- Build a staircase, don’t pull the ladder up. Be welcoming. This project is a reaction to a gatekeeping culture; the way we collaborate should model the opposite.