Overview of the documentation generation stages
mainThe generation pipeline follows these sequential stages:
- Preprocess definitions: Downloads/reads
.d.tsfiles, extracts host sections, and prepares inputs for API Extractor. - Generate requirement-set definitions: Uses
version-removerto create specific API versions andwhats-newto generate comparison tables. - Run API Extractor: Converts
.d.tsinputs into API model JSON files. - Prepare JSON and snippets: Repairs canonical references, cleans enums, and merges Script Lab/local snippets.
- Run API Documenter: Converts API model JSON into DocFX YAML.
- Apply Office-specific YAML enhancements: Inserts snippets, converts annotations to links, and builds "Used by" sections.
- Generate Outlook item object model tables: Creates specific Markdown include files for Outlook properties, methods, and events.
- Assemble publishing output: Moves YAML to
docs/docs-ref-autogen/, combines TOCs, and normalizes formatting. - Update requirement-set page dates: Updates
ms.datebased on changes in include files. - Validate reference coverage: Runs
reference-coverage-testerto check for missing links or incomplete coverage.