Documentation Reorganization Plan¶
Overview¶
Based on the documentation review and answered questions, here's a plan to reorganize the documentation for better clarity and implementation guidance.
Current Structure¶
docs/
├── cli/ # 9 files covering all CLI commands
├── directory-structure/ # 1 file showing .gira/ layout
├── planning/ # 1 file with implementation phases
├── project-structure/ # 1 file with technical architecture
├── DOCUMENTATION_REVIEW.md # Review with answered questions
└── MISSING_DOCUMENTATION.md # Gaps to fill
Proposed New Structure¶
Phase 1: Core Reorganization (Immediate)¶
-
Create overview section
-
Create getting-started section
-
Consolidate user guide
mkdir -p docs/02-user-guide # Move CLI docs here with cleaner names: # - cli/02_ticket_management.md → tickets.md # - cli/03_epic_management.md → epics.md # - cli/04_sprint_management.md → sprints.md # - cli/05_comments_and_collaboration.md → comments.md # - cli/06_attachments.md → attachments.md # - cli/09_subtasks_and_dependencies.md → subtasks.md # - Create workflows.md (new, based on answered questions)
-
Create integrations section
-
Create administration section
-
Create reference section
-
Create development section
Phase 2: Content Creation (Priority Order)¶
- Week 1: Essential Getting Started
- installation.md - System requirements, pip/pipx install
- quickstart.md - 5-minute tutorial
-
concepts.md - Core concepts explained
-
Week 2: Technical References
- file-formats.md - JSON schemas from MISSING_DOCUMENTATION.md
- cli-reference.md - Complete command reference
-
workflows.md - Based on answered workflow questions
-
Week 3: Integration & Advanced
- github.md - Git workflows and CI/CD
- ai-agents.md - AI integration patterns
-
api.md - Python API documentation
-
Week 4: Team & Maintenance
- migration.md - Moving from other systems
- maintenance.md - Best practices
- contributing.md - Development guide
Migration Script¶
#!/bin/bash
# docs/reorganize.sh
# Create new structure
mkdir -p docs/{00-overview,01-getting-started,02-user-guide,03-integrations,04-administration,05-reference,06-development}
# Move files with git mv to preserve history
git mv docs/project-structure/PROJECT_STRUCTURE.md docs/00-overview/architecture.md
git mv docs/cli/01_initialization_and_configuration.md docs/01-getting-started/initialization.md
git mv docs/cli/02_ticket_management.md docs/02-user-guide/tickets.md
git mv docs/cli/03_epic_management.md docs/02-user-guide/epics.md
git mv docs/cli/04_sprint_management.md docs/02-user-guide/sprints.md
git mv docs/cli/05_comments_and_collaboration.md docs/02-user-guide/comments.md
git mv docs/cli/06_attachments.md docs/02-user-guide/attachments.md
git mv docs/cli/09_subtasks_and_dependencies.md docs/02-user-guide/subtasks.md
git mv docs/cli/07_jira_integration.md docs/03-integrations/jira.md
git mv docs/cli/08_reports_and_utilities.md docs/04-administration/reports.md
git mv docs/directory-structure/directory-structure.md docs/05-reference/directory-structure.md
git mv docs/planning/HIGH_LEVEL_PLAN.md docs/06-development/implementation-plan.md
git mv docs/DOCUMENTATION_REVIEW.md docs/06-development/design-decisions.md
git mv docs/MISSING_DOCUMENTATION.md docs/06-development/todo.md
# Remove old directories
rmdir docs/cli docs/directory-structure docs/planning docs/project-structure
Benefits of New Structure¶
- Logical Flow: Overview → Getting Started → User Guide → Advanced Topics
- Easier Navigation: Numbered sections show progression
- Clear Separation: User docs vs developer docs
- Implementation Ready: Aligns with phased development plan
- Extensible: Easy to add new docs in appropriate sections
Next Steps¶
- Execute the reorganization script
- Create placeholder files for missing documentation
- Add navigation README.md in each section
- Update root docs/README.md with table of contents
- Begin filling in missing documentation per priority order