Standard templates for structuring extracted documentation. # [Feature Name] [Description of what the feature does and why a user should care.] ### Key Features - [Benefit-oriented feature 1] - [Benefit-oriented feature 2] - [Benefit-oriented feature 3] --- ## Use Case **Before**: [Description of the old way] - [Pain point 1] - [Pain point 2] **With this feature**: [Description of the new experience.] ## How it Works [Simple explanation of the feature's operation.] [Suggest visual representations where helpful.] --- ## Configuration [Explanation of relevant settings.] 1. **[Setting Name]**: - **Setting**: `[technical_name]` - **Description**: [What this does.] - **Default**: [Default value and its meaning.] 2. **[Setting Name]**: - **Setting**: `[technical_name]` - **Description**: [What this does.] - **Default**: [Default value and its meaning.] --- ## FAQ **"[User question]"** - [Answer.] - [Optional tip.] **"[User question]"** - [Answer.] - [Optional tip.] # [Feature Name] Technical Documentation ## Table of Contents 1. Overview 2. Quick Start 3. Architecture 4. API Reference 5. Configuration 6. User Guide 7. Developer Guide 8. Security 9. Performance 10. Troubleshooting 11. FAQ 12. Changelog 13. References [Use this as an internal source-material outline for technical sections; not for final docs.] --- Separate sections. Show tool output or UI elements. Use actual file paths and setting names. Include common errors and solutions. Tutorials Use cases Troubleshooting Benefits Code examples API specs Integration patterns Performance [Link Text](#section-anchor) [See Configuration Guide](#configuration) [Link Text](https://external.url) [Official Documentation](https://docs.example.com)