- fix GSDFC spec contradictions in __init__ docstring (parenthesized types, fenced-block rule) and sync generated README - rewrite docstrings across loaders, models, nav, servers, renderers, cli; sync .pyi stubs - add pydoclint (google style) gate to dev extras and pyproject config - fix mcp nav resources doc:// -> docs:// - refresh docs/lib and docs/mcp, drop stale docforge/ duplicate group - update wiki pages and add GSDFC + MCP guides under 05_development
1.1 KiB
1.1 KiB
Iterative Workflow
A docs build runs through the CLI in a single pass.
Build commands
# Library reference only
doc-forge build --mkdocs --module docforge
# Wiki + library combined (single MkDocs build)
doc-forge build --wiki --mkdocs --module docforge
# Wiki only — no module required
doc-forge build --wiki --site-name docforge
# MCP structured bundle
doc-forge build --mcp --module docforge
What a combined build does
- Validates the requested modes (
--mkdocs,--api,--wiki,--mcp). - Generates library sources under
docs/lib/**withMkDocsRenderer. - Generates API sources under
docs/api/**when--apiis given. - Derives wiki navigation from
docs/wiki/**. - Writes
mkdocs.ymlwith merged navigation — wiki first, generated groups appended, and the wikiHomereplacing any specHomeentry. - Runs
mkdocs buildonce and emits the site.
Explore the site
doc-forge build --wiki --mkdocs --module docforge
doc-forge serve --mkdocs --mkdocs-yml mkdocs.yml
Serve the MCP bundle
doc-forge build --mcp --module docforge
doc-forge serve --mcp --module docforge