Overview
KDOS entries are designed to be deterministic: consistent front matter, consistent headings, and consistent ordering.
Core Idea
A fixed schema makes the archive scalable: content can be generated, validated, searched, refactored, and cross-linked without manual cleanup.
Formal Definition (if applicable)
Not applicable. This is a style and publishing standard rather than a formal concept.
Intuition
If every page has the same “shape”, you can automate everything around it: tags, related pages, revision tracking, and bulk generation.
Examples
- Good: every page includes “Common Misconceptions” even if it’s short.
- Bad: pages that rename headings or delete sections break tooling and consistency.
Common Misconceptions
- “I can skip sections if I don’t need them.” (No — keep the skeleton; write “Not applicable.”)
- “Tags don’t matter.” (They become your navigation layer at scale.)
Related Concepts
- Taxonomies
- Information architecture
- Content contracts
Applications
- Batch content generation
- Quality validation scripts
- Consistent TOC rendering in PaperMod
Criticism / Limitations
A rigid structure can feel restrictive for essays; KDOS can support essays too, but those should be a separate type (e.g., essay) with a different contract.
Further Reading
- Hugo: Archetypes, Content Organization, Taxonomies
- PaperMod documentation (TOC, tags, section nav)