Thanks for your interest. This guide is written in the open, and every pattern is expected to be reviewed by people who maintain real projects.
- Search existing issues first.
- For a new pattern, describe the problem it solves, when it should not be used, and at least one public project that applies it (with a link).
- For a correction, link the page and the source that contradicts it.
- For a security concern about the site itself, do not post exploit details in a public issue; open an issue asking the maintainers for a private contact.
- Open or pick an issue and say you are working on it.
- Create a branch from
mainand keep each pull request focused on one issue. - Follow the pattern page template once it exists (Problem, When to use, When not to use, Template, Real examples, References).
- Every external claim needs a working link to a primary source. Every real-world example needs a link to the public file, pull request or announcement that shows it.
- Reference the issue in the description (
Closes #N) and describe what changed and why.
Contributions are accepted under the repository license, CC BY 4.0.
Decisions that shape the project (site generator, page structure, translation workflow, deploy target) are recorded as Architecture Decision Records in docs/adr/, one decision per file, named NNNN-short-title.md, using the format described by Michael Nygard: Context, Decision, Status, Consequences. Propose the ADR in a pull request before or together with the change it justifies.
All participation follows the UnitedOpen-Source Code of Conduct.