docs-manager

Automating MkDocs site scaffolding and Markdown generation is orchestrated through a six-phase workflow covering discovery, setup, analysis, planning, generation, and integration. It initializes project structures and generates documentation assets end-to-end across repositories.

Keeping standalone Markdown files and MkDocs documentation in sync with code changes is handled by generating change summaries and updating documentation artifacts. This ensures documentation remains consistent with codebase modifications across multiple formats.

Yes, this documentation workflow supports both MkDocs sites and standalone Markdown files. It provides automated scaffolding, updates, and summarization capabilities across multiple documentation formats within a single project.

Generating change summaries and documentation plans involves running a discovery and analysis phase to assess the codebase, followed by planning and generation phases to produce synchronized documentation artifacts and changelog summaries.

This documentation orchestration workflow operates without external dependencies or plugins. It independently manages the end-to-end documentation lifecycle from initial discovery through final integration.

An orchestrated documentation workflow should be used when projects need consistent docs generation across MkDocs sites and standalone Markdown files, requiring automated scaffolding, multi-format synchronization, and change summaries that manual writing cannot efficiently scale to.