How to Create Documentation
Purpose
This guide explains how to create and update documentation for RDEToolKit. It provides a comprehensive documentation creation process including multilingual support, structured writing, and quality assurance procedures.
Prerequisites
Before starting documentation creation, please ensure the following:
- Development Environment: Development environment setup completed
- MkDocs Knowledge: Basic understanding of Markdown and MkDocs
- Multilingual Support: Ability to write in both Japanese and English
Steps
1. Understand Documentation Structure
Directory Structure
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | |
File Naming Convention
- Japanese Version:
[filename].ja.md - English Version:
[filename].en.md - Paired Files: Create both Japanese and English versions for all pages
2. Determine Page Type
Four Page Types
| Type | Purpose | Naming Example | Components |
|---|---|---|---|
| Tutorial | Experiential Learning | quick-start.en.md |
Steps, expected results, achievement |
| How-to Guide | Problem Solving | installation.en.md |
Prerequisites, steps, verification |
| Concept Explanation | Understanding | structured-processing.en.md |
Background, key concepts, summary |
| Technical Reference | Specification | api/workflows.en.md |
Parameters, return values, examples |
Page Type Selection Criteria
graph TD
A[New Page] --> B{User's Purpose?}
B -->|Want to Learn| C[Tutorial]
B -->|Want to Solve Problem| D[How-to Guide]
B -->|Want to Understand| E[Concept Explanation]
B -->|Want to Check Specs| F[Technical Reference]
3. Create Japanese Version
Basic Template
| template.ja.md | |
|---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | |
Subsection 2
Tip
Provide additional information useful to readers.
Warning
Emphasize important precautions.
Summary
Summarize key points in bullet points:
- Point 1
- Point 2
- Point 3
Next Steps
Provide links to related pages:
- Developer Guide - Development environment setup
- Contributing - How to contribute
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
#### Writing Guidelines **Structured Writing**: - Actively use bullet points and tables - Avoid long sentences, prioritize readability - Set clear purpose for each section **Code Block Writing**: ```python title="config_example.py" # Load configuration file config = load_config("rdeconfig.yaml") # Get important configuration values extended_mode = config.system.extended_mode # Specify processing mode save_raw = config.system.save_raw # Enable raw saving
Admonition Usage:
1 2 3 4 5 6 7 8 | |
4. Translate to English
Translation Principles
- Natural Technical English: Avoid literal translation, use natural English expressions
- Term Consistency: Consistent translation of technical terms
- Cultural Adaptation: Explanation methods suitable for English-speaking readers
Term Correspondence Table
| Japanese | English | Notes |
|---|---|---|
| 構造化処理 | Structuring Processing | Core concept |
| 設定ファイル | Configuration File | General term |
| 前提条件 | Prerequisites | Standard expression |
| 手順 | Steps / Instructions | Choose based on context |
| 確認 | Verification | Meaning of result confirmation |
Translation Example
Japanese:
1 2 3 4 5 6 7 8 | |
1 2 3 4 5 6 7 8 9 10 | |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | |
Link Verification
| terminal | |
|---|---|
1 2 3 4 5 | |
6. Build MkDocs Site
Local Verification
| terminal | |
|---|---|
1 2 3 4 5 6 7 8 | |
Handle Build Errors
| terminal | |
|---|---|
1 2 3 4 5 | |
Verification
Quality Checklist
Content Quality
- [ ] Purpose is clearly described
- [ ] Structured writing is used
- [ ] Code blocks have titles
- [ ] Appropriate admonitions are used
- [ ] Next steps are provided
Multilingual Support
- [ ] Both Japanese and English files exist
- [ ] Terms are consistent
- [ ] Internal links are correctly set
- [ ] Language switching functions
Technical Quality
- [ ] MkDocs build succeeds
- [ ] No broken links
- [ ] Images display correctly
- [ ] Code blocks are properly highlighted
Automated Checks
| terminal | |
|---|---|
1 2 3 4 5 6 7 8 | |
Troubleshooting
Common Issues and Solutions
MkDocs Build Error
1 | |
Solution: Check nav section in mkdocs.yml and remove non-existent files
Broken Links
1 | |
Solution: Add page to mkdocs.yml or delete unnecessary files
Multilingual Display Issues
Check items:
1. extra.alternate settings in mkdocs.yml
2. File naming convention (.ja.md/.en.md)
3. Language-specific nav section settings
Related Information
Detailed information about documentation creation:
- Developer Guide - Development environment setup
- Contributing - How to contribute
- MkDocs Official Documentation - Detailed MkDocs specifications
Continuous Improvement
Documentation should be continuously improved. Actively collect user feedback and conduct regular reviews.