- 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
23 lines
670 B
Markdown
Executable file
23 lines
670 B
Markdown
Executable file
---
|
|
title: Legacy Documentation
|
|
linkTitle: Docs (Old)
|
|
menu:
|
|
main:
|
|
weight: 50
|
|
weight: 50
|
|
cascade:
|
|
- type: docs
|
|
---
|
|
|
|
# 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](../docs/) section for current information.
|
|
|
|
## Available Sections
|
|
|
|
* [Architecture](architecture/) - System architecture and diagrams
|
|
* [Documentation](documentation/) - Meta documentation about the documentation system
|
|
* [Platform Overview](platform-overview/) - Overview document
|
|
* [v1 (Legacy)](v1/) - Original v1 documentation
|