Guide for humans adding or editing documentation on this site.
git checkout develop
source venv/bin/activate
make serve # Live preview at localhost:8000cp docs/templates/page.template.md docs/<section>/<name>.<ext>.md| Type | Extension | Example |
|---|---|---|
| Cloud platform | .cloud.md |
aws.cloud.md |
| Tool / CLI | .tool.md |
terraform.tool.md |
| Service / API | .service.md |
github-rest-api.service.md |
| Operating System | .os.md |
linux.os.md |
| AI Platform | .ai.md |
vertex-ai.ai.md |
| Security | .1337.md |
offensive-security.1337.md |
Each page has these required sections:
- YAML frontmatter —
title,description,tags: [](array format) - Intro — 2-3 cynical, practical sentences
- Quick Hits — 3 tabs: Essential / Common Patterns / Pro Tips & Gotchas
- Optional sections — Installation, Configuration, Architecture (as needed)
- Reference — Links to docs, GitHub, related content
- Footer —
Last Updated+Vibe Check+Tags
Add an entry to the nav: block in zensical.toml:
{ "Page Title" = "section/page-name.ext.md" },make validate # zensical build --strict
make lint # ruff + codespell + yamllint- Respect the 3-tab Quick Hits structure
- Keep the cynical/practical tone
- Update
Last Updateddate - Run
make validatebefore committing
- Cynical but helpful — realistic about trade-offs
- No marketing speak, no buzzwords
- Technical but accessible to juniors
- Use Lucide:
:lucide-...: - Never plain emojis
- Common:
:lucide-list-check:/:lucide-bolt:/:lucide-flame:
- Include inline annotations
# (1)! - Language tag on every block
- Realistic examples, not "hello world"
Every page ends with a Vibe Check in the footer:
**Last Updated:** 2026-06-01 | **Vibe Check:** :lucide-flame: **Short Label** - One-sentence assessment.
- All
{{PLACEHOLDER}}replaced - Lucide icons only (no emojis)
- Code blocks have language
- Vibe Check in footer
- Tags at bottom
- Added to
nav:inzensical.toml -
make validatepasses -
make lintpasses
git checkout -b feat/my-new-page
# ... make changes ...
git add docs/<section>/<file>.md
git commit -m "feat: add <topic> reference page"
git push origin feat/my-new-pageThen open a PR against develop using conventional commits: feat:, fix:, docs:, refactor:, chore:.
Open an issue or ask in the repo discussions.