toolz/goplt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update dead links

Browse Source
This commit is contained in:
0x1d
2025-11-05 11:00:36 +01:00
parent b4f8875a0e
commit 66b0c3b40d
20 changed files with 126 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/content/index.md
View File

@@ -20,17 +20,16 @@ Go Platform is a modular, extensible platform designed to support multiple busin
- **[Playbook](playbook.md)**: Detailed implementation guide and best practices
### 🏛️ Architecture
- **[Architecture Overview](architecture.md)**: System architecture with diagrams
- **[Module Architecture](architecture-modules.md)**: Module system design and integration
- **[Module Requirements](module-requirements.md)**: Detailed requirements for each module
- **[Component Relationships](component-relationships.md)**: Component interactions and dependencies
### 📐 System Specifications
- **[System Behavior Overview](system-behavior.md)**: How the system behaves end-to-end
- **[Service Orchestration](service-orchestration.md)**: How services work together
- **[Module Integration Patterns](module-integration-patterns.md)**: How modules integrate with the platform
- **[Operational Scenarios](operational-scenarios.md)**: Common operational flows and use cases
- **[Data Flow Patterns](data-flow-patterns.md)**: How data flows through the system
- **[Architecture Overview](architecture/architecture.md)**: System architecture with diagrams
- **[Module Architecture](architecture/architecture-modules.md)**: Module system design and integration
- **[Module Requirements](architecture/module-requirements.md)**: Detailed requirements for each module
- **[Component Relationships](architecture/component-relationships.md)**: Component interactions and dependencies
- **System Specifications**
- **[System Behavior Overview](architecture/system-behavior.md)**: How the system behaves end-to-end
- **[Service Orchestration](architecture/service-orchestration.md)**: How services work together
- **[Module Integration Patterns](architecture/module-integration-patterns.md)**: How modules integrate with the platform
- **[Operational Scenarios](architecture/operational-scenarios.md)**: Common operational flows and use cases
- **[Data Flow Patterns](architecture/data-flow-patterns.md)**: How data flows through the system
### 🏗️ Architecture Decision Records (ADRs)
All architectural decisions are documented in [ADR records](adr/README.md), organized by implementation epic: