Skip to content
prod e051e98
Browse

System docs

Architecture · classification · changelog

You are here: ZajLibrarySystem docs
This shelf is for you if: you need to know where content belongs or how the library itself is governed.
Not this shelf? Resources → Reference = how to write pages (voice, components, plugins).

Where does new content go?

Where does new content go? Decision tree with 14 steps and 6 outcomes: Learn & Understand, Build & Create, Resources, Directories, Topic folders, System Docs. New content item one file, folder, kit, or catalog entry What is the reader trying to do? pick the first matching intent Learn understand a topic Build execute an outcome Reuse copy or look up Browse find a record Group category > subcategory > topic Govern manage the library Learn & Understand <topic>/learn/guides · <topic>/learn/handbooks Open guide → Build & Create <topic>/build/playbooks · <topic>/build/blueprints Open guide → Resources <topic>/resources/templates · <topic>/resources/kits Open guide → Directories /directory/tools · /directory/skills Open guide → Topic folders /tech-stack/laravel/codecanyon · /ai-systems/agent-frameworks/mastra Open guide → System Docs /zajlibrary/system/platform · IA · changelog Open guide → Rule: topic path answers subject; shelf and kind answer reader purpose.
Start with reader intent, then pick shelf and type. Use this before creating folders or guessing paths.

SectionHolds
Authoring & agentsAgent read order, intake, links to digests
TemplatesSkeleton map + template → live example
Worked examplesReference-quality pages by doc type
Visuals & diagramsWarrant test, component inventory, when to create SVG
Content architectureShelves, decision tree, taxonomy, shape rules
Collections, categories, tagsMetadata without folder sprawl
File vs folderOne page or a hub of pages
ChangelogWhat changed in the site
Starlight plugins in useDigest — verify against astro.config.mjs
AI writing contractAgent checklist — verify against AGENTS.md

Understand everything — system docs vs reference

System docs = rules about the library (IA, classification, changelog). Reference = how to author pages (Starlight components, writing style, diagram gallery). Agents should read AGENTS.md + reference shelf first; system docs are optional digests when fresh.