π Basic UsageΒΆ
Documentation for π Basic Usage.
This section demonstrates the markdown inclusion feature with practical examples.
Quick Start ChecklistΒΆ
Use this checklist to get started with markdown includes:
- Install Introligo and Sphinx
- Create introligo configuration file
- Identify existing markdown files to include
- Add
markdown_includesto module configuration - Run Introligo to generate RST files
- Build documentation with Sphinx
- Preview generated documentation
Including Multiple Markdown FilesΒΆ
Multiple markdown files can be included in module documentation:
# Include multiple markdown files
modules:
my_module:
title: "My Module"
description: "Module with markdown documentation"
module: "myproject.my_module"
# Include markdown files
markdown_includes:
- "docs/user_guide.md"
- "docs/api_reference.md"
- "CONTRIBUTING.md"
Single Markdown FileΒΆ
For simpler cases, a single file can be specified:
# Include single file (string instead of list)
modules:
my_module:
title: "My Module"
markdown_includes: "README.md"
Relative PathsΒΆ
All paths are resolved relative to the configuration file:
# Config file at: docs/composition/introligo_config.yaml
modules:
my_module:
title: "My Module"
# Include from project root
markdown_includes:
- "../../README.md"
- "../../docs/guides/setup.md"
Advantages of Markdown IncludesΒΆ
BenefitsΒΆ
Reuse existing documentation: Include README.md and other markdown files directly
DRY principle: Avoid documentation duplication across formats
Easy maintenance: Update once, changes reflect everywhere
Version control friendly: Markdown files are easily reviewed in pull requests
Familiar format: Write in markdown, generate RST documentation automatically
Recommended Use CasesΒΆ
Project overviews and README files
Detailed user guides and tutorials
Contributing guidelines
Changelog and release notes
FAQ sections