- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
3.6 KiB
3.6 KiB
Contributor Guidelines
Last Updated: 2025-01-20
Document Version: 1.0
Status: Active Documentation
Overview
This document provides guidelines for contributing to the documentation, including style standards, review process, and approval workflow.
Style Guide Reference
Primary Reference:
Key Standards:
- File naming:
UPPERCASE_WITH_UNDERSCORES.md - Headers: Include Last Updated, Document Version, Status
- Cross-references: Use Related Documentation sections
- Code blocks: Include language identifiers and expected output
Contribution Process
Step 1: Identify Need
Ways to contribute:
- Fix errors or outdated information
- Add missing documentation
- Improve existing documentation
- Add examples or use cases
- Create diagrams or visualizations
Step 2: Follow Standards
Before contributing:
- Read DOCUMENTATION_STYLE_GUIDE.md
- Review similar documents for consistency
- Use templates where available
- Follow naming conventions
Step 3: Create/Update Document
For new documents:
- Use appropriate directory structure
- Follow style guide header format
- Include Related Documentation section
- Add to MASTER_INDEX.md
For updates:
- Update Last Updated date
- Increment Document Version if significant changes
- Update change log if document has one
- Verify all links still work
Step 4: Review and Test
Self-review checklist:
- Follows style guide
- All links work
- Code examples tested (if applicable)
- No placeholder content
- Proper cross-references
- Added to index files
Step 5: Submit for Review
Review process:
- Create pull request or notify team
- Include description of changes
- Reference related issues/tasks
- Wait for review approval
Approval Workflow
Review Levels
Level 1: Self-Review
- Minor corrections
- Formatting fixes
- Link updates
Level 2: Peer Review
- New documents
- Significant updates
- Configuration changes
Level 3: Team Review
- Architecture changes
- Major procedure changes
- Policy updates
Examples and Templates
New Document Template
# Document Title
**Navigation:** [Home](../README.md) > [Category](README.md) > Document Title
**Last Updated:** YYYY-MM-DD
**Document Version:** 1.0
**Status:** 🟢 Active Documentation
---
## Overview
[Document purpose and scope]
---
[Content sections]
---
## Related Documentation
- **[Related Doc 1](path/to/doc1.md)** ⭐⭐⭐ - Description
- **[Related Doc 2](path/to/doc2.md)** ⭐⭐ - Description
---
**Last Updated:** YYYY-MM-DD
**Review Cycle:** [Monthly/Quarterly/As Needed]
Common Contribution Types
Adding Examples
Guidelines:
- Use real-world scenarios
- Include expected outputs
- Test examples before documenting
- Update if procedures change
Fixing Errors
Process:
- Identify error
- Verify correct information
- Update document
- Update related documents if needed
- Test fix
Adding Diagrams
Guidelines:
- Use Mermaid for new diagrams
- Follow diagram standards
- Reference in text
- Update visual index
Related Documentation
- DOCUMENTATION_STYLE_GUIDE.md ⭐⭐⭐ - Style guide
- MASTER_INDEX.md ⭐⭐⭐ - Documentation index
- MAINTENANCE_REVIEW_SCHEDULE.md ⭐ - Review schedule
Last Updated: 2025-01-20
Review Cycle: Quarterly