title: Content Lifecycle last_updated: 2026-03-21

Content Lifecycle

How content moves from idea to published in this repository.

Stages

  Intake          Draft           Review          Published       Maintenance
  ------          -----           ------          ---------       -----------
  New info        Author writes   Peer review     Merged to       Staleness
  arrives in      content using   + CI checks     main branch     monitoring
  meta/intake/    template                                        + updates

1. Intake

New information enters through meta/intake/ using the intake template. Sources include:

  • Tool release notes and changelogs
  • Community pattern discoveries
  • Conference talks and blog posts
  • Reader feedback and issue reports

Weekly triage: Intake items are reviewed weekly and either:

  • Assigned to update an existing module/entry
  • Queued for a new reference entry or case study
  • Deferred with a documented reason

2. Draft

The author (contributor or maintainer) writes content using the appropriate template:

  • Curriculum modules: create all files (concepts.md, tool-specific, exercises.md)
  • Reference entries: use the _TEMPLATE.md in the target directory
  • Case studies: use case-studies/_TEMPLATE.md

Checklist before submitting for review:

  • YAML frontmatter complete
  • Follows style guide
  • All code examples tested
  • "When NOT to use" section included (for patterns)
  • Internal links use relative paths
  • Terms defined on first use

3. Review

Pull request review checks:

  • Automated (CI): Markdown lint, link validation, frontmatter schema, prose lint
  • Human: Accuracy, clarity, completeness, adherence to dual-layer rule

Review criteria:

  • Is the content accurate and tested?
  • Does it follow the dual-layer split (concepts vs tool-specific)?
  • Are the code examples copy-paste ready?
  • Would a developer at the stated difficulty level understand this?

4. Published

Once merged to main, content is live. The last_updated field in frontmatter records when it was last modified.

5. Maintenance

Staleness Detection

Content is flagged for review when:

  • last_updated is more than 90 days old
  • tested_with version is more than 2 minor versions behind the current tool release
  • A tool-update issue is filed that affects the content

Update Process

  1. Tool update issue is filed (manually or via automated monitoring)
  2. Affected files are identified from the issue
  3. Tool-specific files (claude-code.md, codex-cli.md) are updated
  4. concepts.md is updated only if the mental model changes
  5. tested_with and last_updated are bumped
  6. Normal review process applies

Deprecation

Content that is no longer relevant (e.g., a pattern superseded by a better approach):

  1. Add a deprecation notice at the top of the file
  2. Link to the replacement content
  3. Document the change in CHANGELOG.md under "Pattern Evolution"
  4. Keep the file for 90 days, then remove