Contribute

Guest writing is welcome. Your piece goes through the same contract and review as everything else here, and it carries your name.

What we publish

• Concepts: what something is, with one concrete example.
• Patterns: a reusable design and when to use it.
• Implementations: working code or configuration you have actually run.
• Teardowns: a standard, tool or spec taken apart honestly.
• Glossary terms: one term, one definition.

Bonus points for showing a concept at personal, business and enterprise scale.

Ground rules

1. Real, not theoretical. Say what you did, what broke, and what you would do differently.
2. Cite your sources. Every outside fact gets an entry in sources, with the date you accessed it.
3. Nothing confidential. No employer names, internal system names, real volumes or anything you couldn't say at a public conference. Use synthetic examples.
4. Disclose AI help. If an AI drafted or edited your piece, list it in assisted_by. You remain the author and are accountable for every word.
5. Plain words. Short sentences, one idea per paragraph, an example early.

How to submit

With GitHub (preferred)

1. Fork the repository.
2. Create your file: python scripts/new.py pattern "Your title". This mints a permanent ID and fills in the frontmatter.
3. Write. Link glossary terms with [[term-slug]].
4. Check it: python scripts/build.py --check.
5. Open a pull request. The template walks you through the checklist.

Without GitHub

Open a submission issue and paste your draft. A maintainer will turn it into a file and credit you.

What happens next

Status	Meaning	Who moves it
draft	Submitted; passes the contract	You, on submission
reviewed	Checked for accuracy and clarity	A maintainer, after review
verified	Tested against a real implementation	A maintainer, with verified_by saying how

Drafts are published and labeled, not hidden. Review happens in the open on the pull request.

Licensing

By contributing you agree your content is published under CC BY 4.0 and any code under the MIT license.