Content

Content rules govern raw Markdown files before any template renders them.

These standards ensure a page written for one property displays correctly across every site in the system, allowing notes to move seamlessly between Bear, GitHub, and Hugo without modification.

Bilingual pagesHow a page exists in two languages: paired files, shared related paths and localized slugs
Cross-referencesThree ways this site points at related content, and the rule for choosing between them
Front matterThe metadata contract for content files: which keys exist, what they mean, and the rules for dates, slugs, aliases and translations
MarkdownMarkdown syntax reference for this site’s pages, from emphasis and headings to tables, footnotes, and emoji
Section archetypesReusable definitions of the blog, TIL, collection, now/then, colophon and wiki sections
Writing mechanicsWhich dash does which job, what the typographer extension fixes automatically, and which emoji data to trust