Skip to main content
AstraProjectAstraUserbotProjectGeminiAgentBridgeProjectTelDrive LabProjectVAJRAProjectVGU SignalProjectEngineering Through FailureWritingFrom Projects to Engineering KnowledgeWritingProduction Readiness Is a BoundaryWriting
← Documentation

Reference / Publishing

Content Workflow

The repository is the publishing system. Content is created, verified and released through Git.

Create

npm run new:content -- projects my-project --title "My Project"
npm run new:content -- notes durable-boundary --title "A Durable Boundary"
npm run new:content -- writing technical-essay --title "A Technical Essay"

The generator creates collection-specific draft metadata and durable section structure.

Verify

npm run validate
astro check
npm run build
npm run audit
npm run audit:performance

The GitHub Quality workflow runs the repository, build, browser and performance gates automatically.

Connect

Use the existing related: model for project, knowledge, evidence and chronology relationships. Do not create a second graph database or manual index.

Publish

Move from draft to a published state only after the content is complete and verified. A normal release is draft → review → validation → build → browser audit → performance audit → Git checkpoint → GitHub → Vercel.

Long-term rule

Do not add a CMS, database, paid API or runtime search service merely to make publishing easier. Git already provides history, review, rollback and provenance.