docs: add mkdocs, update links, add architecture documentation
This commit is contained in:
63
docs/content/stories/README.md
Normal file
63
docs/content/stories/README.md
Normal file
@@ -0,0 +1,63 @@
|
||||
# Implementation Tasks
|
||||
|
||||
This directory contains detailed task definitions for each phase of the Go Platform implementation.
|
||||
|
||||
## Task Organization
|
||||
|
||||
Tasks are organized by phase, with each major task section having its own detailed file:
|
||||
|
||||
### Phase 0: Project Setup & Foundation
|
||||
- [Phase 0 Tasks](./phase0/README.md) - All Phase 0 tasks
|
||||
|
||||
### Phase 1: Core Kernel & Infrastructure
|
||||
- [Phase 1 Tasks](./phase1/README.md) - All Phase 1 tasks
|
||||
|
||||
### Phase 2: Authentication & Authorization
|
||||
- [Phase 2 Tasks](./phase2/README.md) - All Phase 2 tasks
|
||||
|
||||
### Phase 3: Module Framework
|
||||
- [Phase 3 Tasks](./phase3/README.md) - All Phase 3 tasks
|
||||
|
||||
### Phase 4: Sample Feature Module (Blog)
|
||||
- [Phase 4 Tasks](./phase4/README.md) - All Phase 4 tasks
|
||||
|
||||
### Phase 5: Infrastructure Adapters
|
||||
- [Phase 5 Tasks](./phase5/README.md) - All Phase 5 tasks
|
||||
|
||||
### Phase 6: Observability & Production Readiness
|
||||
- [Phase 6 Tasks](./phase6/README.md) - All Phase 6 tasks
|
||||
|
||||
### Phase 7: Testing, Documentation & CI/CD
|
||||
- [Phase 7 Tasks](./phase7/README.md) - All Phase 7 tasks
|
||||
|
||||
### Phase 8: Advanced Features & Polish (Optional)
|
||||
- [Phase 8 Tasks](./phase8/README.md) - All Phase 8 tasks
|
||||
|
||||
## Task Status
|
||||
|
||||
Each task file includes:
|
||||
- **Task ID**: Unique identifier (e.g., `0.1.1`)
|
||||
- **Title**: Descriptive task name
|
||||
- **Phase**: Implementation phase
|
||||
- **Status**: Pending | In Progress | Completed | Blocked
|
||||
- **Priority**: High | Medium | Low
|
||||
- **Dependencies**: Tasks that must complete first
|
||||
- **Description**: Detailed requirements
|
||||
- **Acceptance Criteria**: How to verify completion
|
||||
- **Implementation Notes**: Technical details and references
|
||||
- **Related ADRs**: Links to relevant architecture decisions
|
||||
|
||||
## Task Tracking
|
||||
|
||||
Tasks can be tracked using:
|
||||
- GitHub Issues (linked from tasks)
|
||||
- Project boards
|
||||
- Task management tools
|
||||
- Direct commit messages referencing task IDs
|
||||
|
||||
## Task Naming Convention
|
||||
|
||||
Tasks follow the format: `{phase}.{section}.{subtask}`
|
||||
|
||||
Example: `0.1.1` = Phase 0, Section 1 (Repository Bootstrap), Subtask 1
|
||||
|
||||
Reference in New Issue
Block a user