DocBuilder Documentation

Welcome to the DocBuilder documentation! This documentation follows the Diátaxis framework, organizing content by user needs.

Documentation Structure

📚 Tutorials

Learning-oriented - Step-by-step lessons to get you started.

Best for: First-time users, learning the basics

🛠️ How-To Guides

Task-oriented - Practical guides for specific tasks.

Best for: Users with specific goals, solving problems

📖 Reference

Information-oriented - Technical specifications and API documentation.

Best for: Looking up specific information, API details

💡 Explanation

Understanding-oriented - Conceptual documentation and design rationale.

Architecture Documentation

Architecture Decision Records (ADRs)

Best for: Understanding why things work the way they do, architectural decisions

Quick Start Guide

New Users

  1. Start with Getting Started Tutorial
  2. Review CLI Reference for commands
  3. Check Configuration Reference for options

Developers/Contributors

  1. Read Architecture Documentation Index
  2. Study Comprehensive Architecture
  3. Review Package Architecture Guide
  4. Check Contributing Guide

Operations/DevOps

  1. Review Getting Started Tutorial
  2. Check How-To: Run Incremental Builds
  3. Review Build Report Reference
  4. Study operational considerations in Comprehensive Architecture

Documentation by Feature

Basic Usage

Multi-Repository Aggregation

Theme Integration

Performance Optimization

Customization

Advanced Topics

Additional Resources

Project Documentation

Architecture & Planning

Examples

Documentation Principles

This documentation follows these principles:

  1. User-Centric - Organized by what users want to achieve
  2. Progressive Disclosure - Start simple, add complexity as needed
  3. Searchable - Clear structure, consistent terminology
  4. Maintained - Updated with code changes
  5. Tested - Examples are verified to work

Contributing to Documentation

We welcome documentation contributions! When contributing:

  1. Follow the Diátaxis framework structure
  2. Use clear, concise language
  3. Include code examples where applicable
  4. Test all commands and configurations
  5. Update index files when adding new documents

See Contributing Guide for details.

Getting Help

Documentation Status

Last Major Update: December 2025

Coverage:

  • ✅ Getting Started Tutorial
  • ✅ CLI Reference
  • ✅ Configuration Reference
  • ✅ Build Report Reference
  • ✅ Comprehensive Architecture Documentation
  • ✅ Package-Level Documentation
  • ✅ Visual Architecture Diagrams
  • ✅ How-To Guides
  • ⏳ Additional tutorials (in progress)

Feedback: Documentation feedback is highly appreciated! Please open an issue if you find areas that need improvement.