Documentation Structure
Documentation Structure
Section titled “Documentation Structure”Documentation is built with Astro Starlight and follows the Divio documentation system.
Content Organization
Section titled “Content Organization”| Section | Purpose | Example |
|---|---|---|
| Tutorials | Learning-oriented walkthroughs | Setting up the cluster |
| How-To Guides | Problem-oriented procedures | Adding a worker node |
| Explanation | Understanding-oriented concepts | GitOps automation model |
| Reference | Information-oriented lookup | Version matrix |
File Locations
Section titled “File Locations”docs/src/content/docs/├── tutorials/ # Step-by-step learning paths├── how-to/ # Task-specific procedures├── explanation/ # Architecture and concepts├── reference/ # Component catalogs and matrices└── index.mdx # Landing pageFrontmatter Requirements
Section titled “Frontmatter Requirements”Each document must include SEO-optimized frontmatter:
---title: Descriptive Title with Keywordsdescription: Clear description for search results (150-160 chars)keywords: - primary keyword - secondary keyword - related termssidebar: order: 1---Naming Conventions
Section titled “Naming Conventions”- Use lowercase kebab-case:
add-worker-node.md - Use task-based names:
deploy-apps.mdnotapps.md - Avoid numeric prefixes in filenames
Mermaid Diagrams
Section titled “Mermaid Diagrams”Diagrams are rendered with the astro-mermaid plugin:
flowchart LR Git[Git] --> ArgoCD[ArgoCD] ArgoCD --> K8s[Kubernetes API]
Writing Guidelines
Section titled “Writing Guidelines”- Follow AGENTS.md conventions
- Use tables instead of numbered lists for steps
- Avoid inline YAML comments
- Keep prose professional without marketing language