Skip to content

docs: Create documentation structure guidelines template for ecosystem #305

Description

@kcenon

Summary

Create a standardized documentation structure guidelines document (DOCUMENTATION_GUIDELINES.md) that defines the official documentation organization pattern for all ecosystem systems, serving as a reference for maintaining consistency across projects.

Background (Why)

  • No formal documentation structure standard exists across ecosystem
  • Each system evolved its own documentation organization
  • New contributors don't have a reference for documentation placement
  • Inconsistent structures make cross-system navigation difficult
  • Documentation cleanup efforts need a target standard to work toward

Current problems:

  • Where should a new guide go? docs/ or docs/guides/?
  • Should Korean translations use .kr.md or _KO.md suffix?
  • Which documents are required vs optional?
  • How should advanced topics be organized?

Scope (What)

Deliverables

  1. DOCUMENTATION_GUIDELINES.md - Main guidelines document
  2. docs/templates/ - Template files for common document types
  3. docs/.structure - Optional structure validation config

Guidelines Content

# Documentation Structure Guidelines

## Required Documents

Every system MUST have these files:
- README.md (root) - Project overview, badges, quick links
- README.kr.md (root) - Korean translation
- docs/ARCHITECTURE.md - System architecture overview
- docs/API_REFERENCE.md - Complete API documentation
- docs/FEATURES.md - Feature list and descriptions
- docs/CHANGELOG.md - Version history
- docs/PROJECT_STRUCTURE.md - Codebase organization

## Standard Folder Structure

docs/
├── README.md              # Documentation navigation index
├── ARCHITECTURE.md        # System architecture (required)
├── API_REFERENCE.md       # API documentation (required)
├── FEATURES.md            # Feature documentation (required)
├── CHANGELOG.md           # Change history (required)
├── PROJECT_STRUCTURE.md   # Code organization (required)
├── PRODUCTION_QUALITY.md  # Production readiness (optional)
│
├── advanced/              # Internal implementation details
│   ├── ARCHITECTURE.md    # Detailed architecture
│   ├── MIGRATION.md       # Migration guides
│   └── STRUCTURE.md       # Internal structure
│
├── guides/                # User-facing guides
│   ├── QUICK_START.md     # Getting started (recommended)
│   ├── INTEGRATION.md     # Integration with other systems
│   ├── BEST_PRACTICES.md  # Usage recommendations
│   ├── FAQ.md             # Frequently asked questions
│   └── TROUBLESHOOTING.md # Problem resolution
│
├── performance/           # Performance documentation
│   ├── BASELINE.md        # Performance baselines (required)
│   └── TUNING.md          # Optimization guide
│
├── contributing/          # Contributor guides
│   ├── CONTRIBUTING.md    # How to contribute
│   └── CI_CD_GUIDE.md     # CI/CD setup
│
└── integration/           # System integration docs
    └── README.md          # Integration overview

## Naming Conventions

| Pattern | Usage | Example |
|---------|-------|---------|
| UPPER_CASE.md | Core documents | ARCHITECTURE.md |
| lower_case.md | Guides and tutorials | quick_start.md |
| .kr.md suffix | Korean translations | README.kr.md |
| _KO.md suffix | (deprecated) | Do not use |

## Translation Requirements

- All required documents should have Korean translations
- Korean files use `.kr.md` suffix (not `_KO.md`)
- Place translations alongside originals
- Keep translations in sync with English versions

## Document Templates

### Architecture Document
- Overview section with diagram
- Component descriptions
- Data flow explanation
- Design decisions rationale

### API Reference
- Public interfaces/classes
- Method signatures with descriptions
- Usage examples
- Error handling

### Feature Document
- Feature list with descriptions
- Use cases
- Configuration options
- Performance characteristics

Impact Analysis (Where)

Affected Systems

System Current Compliance Changes Needed
common_system High Add guidelines doc
thread_system Medium Restructure per guidelines
logger_system High Minor adjustments
container_system High Minor adjustments
monitoring_system High Minor adjustments
database_system Medium Minor adjustments
network_system Low Significant restructure

New Files to Create

  • docs/contributing/DOCUMENTATION_GUIDELINES.md
  • docs/templates/ARCHITECTURE_TEMPLATE.md
  • docs/templates/FEATURE_TEMPLATE.md
  • docs/templates/GUIDE_TEMPLATE.md

Implementation Plan (How)

Phase 1: Create Guidelines Document

  1. Draft DOCUMENTATION_GUIDELINES.md with all sections
  2. Define required vs optional documents
  3. Define folder structure standard
  4. Define naming conventions
  5. Define translation requirements

Phase 2: Create Templates

  1. Create ARCHITECTURE_TEMPLATE.md
  2. Create FEATURE_TEMPLATE.md
  3. Create GUIDE_TEMPLATE.md
  4. Create CHANGELOG_TEMPLATE.md (if not exists)

Phase 3: Documentation

  1. Add examples for each template
  2. Add checklist for document compliance
  3. Add migration guide from old structures

Phase 4: Validation (Optional)

  1. Create structure validation script
  2. Add to CI/CD for documentation PRs

Phase 5: Distribution

  1. Add guidelines to common_system
  2. Link from all other systems
  3. Announce in ecosystem documentation

Acceptance Criteria

  • DOCUMENTATION_GUIDELINES.md created with all sections
  • Standard folder structure clearly defined
  • Required vs optional documents clearly specified
  • Naming conventions documented
  • Korean translation requirements documented
  • At least 3 document templates created
  • Guidelines linked from all ecosystem system READMEs
  • Compliance checklist available

Related Issues

Labels

  • documentation
  • enhancement
  • template

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationenhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions