Skip to main content

Content Types

Content Type is a single-select enum on each document in the Content Register. It is one of exactly nine values, split into two tiers:

  • Free — public, fully indexable, build topical authority.
  • Premium — gated behind a SureMembers membership and used for monetization.

Free Tier​

Content TypeMeaningBest ForExample
cheatsheetCompact syntax/command reference. Assumes you already know the concept — you just need the exact command or syntaxcode, devopsGit Quick Reference, Python Quick Reference
quick-referencePractical summary of a topic or its elements. Broader than a cheatsheet — explains the pieces and when to use them, still scannableai, codeArticle Body Styling Sample
checklistA repeatable, ordered process you follow step by step. Answers "what do I do, in what order?"devops, securityKeyword Research Checklist
glossaryTerm → definition entries. Answers "what is X?" — one term per H2, definition-first (1–3 sentences), ~8–15 terms, ~250–450 wordscode, aia Python Glossary (module, package, duck typing…)

Premium Tier​

Content TypeMeaningBest ForExample
promptA reusable, copy-paste AI prompt or prompt pattern. Answers "give me a prompt that reliably produces X"aiData Extraction Prompt, Code Review Prompt
snippetA single, ready-to-run code block with minimal context. Answers "give me the exact code for one task"codePython Retry-With-Backoff Snippet
patternA reusable approach to a recurring problem, with structure and rationale. Deeper than a snippet, less prose than a tutorialcode, devopsIdempotent Deploy Pattern, Config-as-Code Pattern
templateA complete, copy-paste starting file or scaffold (Docker Compose, nginx conf, CI pipeline, systemd unit). Answers "give me a working starting point"devops, code, securityDocker Compose Template, Cloudflare Worker Template
runbookAn ordered operational or incident procedure with verification steps. Answers "what do I do when this breaks?"devops, securityBackup Restore Runbook, Certificate Rotation Runbook

Mental model: cheatsheet = "give me the syntax", quick-reference = "summarize this topic", checklist = "walk me through the steps", glossary = "what does this word mean", prompt = "give me a prompt that works", snippet = "give me the code for one task", pattern = "show me the reusable approach", template = "give me a working starting file", runbook = "tell me what to do when it breaks".

Glossary format​

A glossary is one term per H2, not a bold list under a single Terms heading. This gives each term a heading anchor (deep-linkable, surfaced in the page outline) and turns every term into a scannable section that answers what is X?. The body contract's rule — title is H1, body starts at H2 — makes ## Term fully compliant. See Article Body Elements → Glossary for the full template.

Rules:

  • Each term = ## Term (sentence case, no trailing period).
  • Definition-first: sentence 1 answers "what is it"; sentence 2 (optional) adds usage, command, or a relevant cross-link.
  • No ## Terms wrapper heading — it becomes empty once terms are H2s. Add an optional lead-in paragraph before the first term instead.
  • Keep 8–15 terms and roughly 250–450 words so every heading carries real definition content.
  • Cross-link each term to the deepest existing post on that concept (descriptive anchor text, one target per term, no dead-ends). This builds the topical cluster that lets terms rank beyond the page's own keyword. See Glossary SEO.

Brief depth (SCS alignment)​

When a document moves through the SCS pipeline, its brief depth is derived from its content type:

Content typeBrief depthRequired sections
cheatsheet, quick-referencelight1–5 + 7 + 8
checklist, reference, glossarystandard1–8 + 10
prompt, snippet, pattern, template, runbookfull1–10

new-doc.py sets brief_depth (via the SCS scaffolding) at scaffold time. See the SCS Brief Gate for the full section list and check rules.

Choosing a Type​

Pick the type that matches the question the page answers:

  • You already know the concept and just need the command → cheatsheet.
  • You want a scannable explainer of the pieces and when to use them → quick-reference.
  • You want a repeatable, ordered process → checklist.
  • You want one term, one definition → glossary.
  • You want a reusable AI prompt → prompt.
  • You want the exact code for one task → snippet.
  • You want a reusable approach to a recurring problem → pattern.
  • You want a complete copy-paste starting file → template.
  • You want an operational procedure for an incident → runbook.

Where the Type Is Used​

PlaceField / Value
content-inventory.csvContent Type column — single select, one of the nine values
Markdown frontmatterRequired content_type: field on every document (e.g. content_type: cheatsheet). sync.py requires it and validate-inventory.py enforces it matches the CSV. It becomes _id86_content_type post meta on WordPress
new-doc.py`--type cheatsheet
id86-publish-scheduled.sh / id86-push-published.shThe register row drives publish; the type has no separate sync path

When scaffolding with scripts/new-doc.py, the generated Markdown frontmatter carries the type, for example:

content_type: cheatsheet

Author the body per the Article Body Elements contract regardless of the type — the type decides the page's shape and scope, not the Markdown elements allowed.

Tier vs Access​

  • Free types are public, indexed by search engines, and drive topical authority and traffic.
  • Premium types (prompt, snippet, pattern, template, runbook) are gated by SureMembers and require a membership to view. They are the monetization surface; see Monetization & Disclosures.
  • A premium document's excerpt and meta description remain visible so search can confirm the answer exists, but the full body requires membership.
  • The register records the tier in the access_tier column (free / premium), derived from the content type. new-doc.py sets it at scaffold time and validate-inventory.py enforces that premium types carry access_tier: premium.

Working Examples​

Four live demo posts in the demo category exercise the free formats on a common topic (tmux), so the formats are directly comparable:

Content TypeExample PostWhat it shows
cheatsheetTmux CheatsheetKeybinding and command tables, one action per row
quick-referenceTmux ReferenceExplains the client–server model and when to use each feature
checklistTmux Setup ChecklistOrdered, checkable setup steps with a verification pass
glossaryTmux GlossaryOne term per H2, definition-first

Sources live at content/demo/DEM-000002-* … DEM-000005-* in the local mirror, and the matching rows are published in content-inventory.csv.

Guide examples (documentation)​

These pages are documentation-side walkthroughs of each type's shape and authoring contract. They are not live posts, but they mirror the production format.

Content TypeGuide pageWhat it shows
cheatsheetExample — CheatsheetCompact command tables and copy-paste snippets
quick-referenceExample — Quick ReferenceBroader explainer with model, use cases, and commands
checklistExample — ChecklistOrdered, checkable steps with verification and rollback
glossaryExample — GlossaryOne term per H2, definition-first, cross-links
promptExample — PromptReusable AI prompt with variables and output format
snippetExample — SnippetSingle ready-to-run code block
patternExample — PatternReusable approach with structure and rationale
templateExample — TemplateComplete copy-paste starting file
runbookExample — RunbookOrdered incident procedure with verification

Note: the former faq type and its DEM-000006 tmux demo were retired when the taxonomy moved to the Free + Premium tiers.