Stephan Lo
62999b41d0
- Archive old docs to docs-old/ for reference - Create new top-down documentation structure: * Platform Overview: purpose, audience, product structure * Components: individual platform components (Forgejo, Kubernetes, Backstage) * Getting Started: onboarding and quick start guides * Operations: deployment, monitoring, troubleshooting * Governance: ADRs, project history, compliance - Add DOCUMENTATION-GUIDE.md with writing guidelines and templates - Add component template (TEMPLATE.md) for consistent documentation - Simplify root README and move technical docs to doc/ folder - Update test configuration: * Exclude legacy content from markdown linting * Relax HTML validation for theme-generated content * Skip link checking for legacy content in test:links * Keep 'task test' clean for technical writers (100% pass) * Add 'task test:full' with comprehensive link checking - Update home page with corrected markdown syntax - Fix internal links in archived content BREAKING CHANGE: Documentation structure changed from flat to hierarchical top-down approach
670 B
Executable file
670 B
Executable file
| title | linkTitle | menu | weight | cascade | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Legacy Documentation | Docs (Old) |
|
50 |
|
Legacy Documentation
This section contains the previous version of the documentation for reference purposes.
Note: This documentation is archived and may be outdated. Please refer to the main Documentation section for current information.
Available Sections
- Architecture - System architecture and diagrams
- Documentation - Meta documentation about the documentation system
- Platform Overview - Overview document
- v1 (Legacy) - Original v1 documentation