- Stringify Object.signature() instead of str()-ing the bound method,
which produced "<bound method Class.signature of ...>" reprs
- Skip alias members that cannot resolve (stdlib/third-party imports)
while preserving resolvable package re-exports; return None for empty
signatures (classes without __init__ args)
- Add MCP renderer regression tests for signature cleanliness, alias
filtering, and package re-export preservation
- Renamed `02_architecture.md` to `02_components.md` to match the standard component page naming convention.
- Updated `docs/mkdocs.wiki.yml` to reflect renamed pages and fix navigation label acronym casing (GSDFC, MCP, MkDocs).
- Updated `index.md` to include the mandatory doc model blockquote, standardize section headers with emojis, and accurately map the `Documentation Structure` table to the navigation menu.
- Standardized all wiki pages (`01_overview.md`, `02_components.md`, `03_conventions.md`, `04_iterative_workflow.md`, and `05_development/*`) by:
- Adding horizontal rules (`---`) between major sections.
- Applying emoji-prefixed H2 headings for recognizable section types.
- Appending `## Related` or `## ➡️ Read Next` footers with standard relative cross-links.
- Adjusting H1 headers to match guide anatomy (e.g., `# Library Overview` on the overview page).
- add build_wiki_nav deriving MkDocs nav from docs/wiki file structure
(index.md -> Home, numeric prefixes stripped and title-cased, nested
dirs become groups, natural ordering)
- add --wiki / --wiki-dir to build; wiki-only builds need no --module
- merge wiki nav before generated lib/api nav; wiki Home replaces the
nav spec Home entry
- add mkdocs.wiki.yml template fragment and nav/cli tests
- dogfood doc-forge's own docs/wiki and regenerate site output
# Improve documentation look & feel via MkDocs Material template enhancements
## Summary
This MR improves the overall **documentation experience and visual presentation** of the doc-forge docs by enhancing the MkDocs Material template configuration.
The changes focus on **navigation usability, code readability, and richer Markdown rendering**, resulting in a cleaner and more professional documentation site.
Docstring changes were made across the codebase for consistency, but this MR description focuses on the **template and presentation improvements**.
---
## Navigation Improvements
The navigation system has been enhanced to provide a clearer structure and better discoverability.
Key improvements include:
* Section-aware navigation in the sidebar
* Automatic expansion of module/package hierarchy
* Scroll tracking within the sidebar
* Clickable package index pages
Material navigation features added:
* `navigation.sections`
* `navigation.expand`
* `navigation.tracking`
* `navigation.indexes`
This results in a **single cohesive navigation tree** that exposes the entire documentation hierarchy from the sidebar.
---
## Code Block Improvements
Code blocks previously appeared relatively plain. The template now enables richer syntax highlighting and improved readability.
Enhancements include:
* Syntax highlighting using `pymdownx.highlight`
* Line numbers for code blocks
* Anchored line numbers for deep linking
* Improved fenced code block rendering
Additional Material features:
* `content.code.copy` — copy button for code blocks
* `content.code.annotate` — support for code annotations
These changes significantly improve the readability of examples and API snippets throughout the documentation.
---
## Markdown Rendering Enhancements
Additional Markdown extensions were enabled to support richer documentation features:
* `pymdownx.superfences` for advanced fenced blocks
* `pymdownx.inlinehilite` for inline code highlighting
* `pymdownx.snippets` for reusable snippets
* `admonition` and `pymdownx.details` for callouts and collapsible sections
* `pymdownx.tabbed` for tabbed content blocks
* `pymdownx.tasklist` for checklist-style items
* `tables`, `footnotes`, and advanced formatting extensions
These extensions make it easier to write expressive and structured documentation.
---
## Search Experience
The documentation search experience has been improved using Material search features:
* `search.highlight`
* `search.share`
* `search.suggest`
These enhancements provide:
* highlighted search matches
* sharable search URLs
* auto-suggestions while typing
---
## mkdocstrings Improvements
The mkdocstrings configuration has been expanded to produce clearer API documentation.
Notable improvements include:
* grouping objects by category
* explicit category headings
* improved symbol headings
* cleaner object path display
This results in more structured API documentation pages.
---
## Result
Overall, these changes provide:
* cleaner and more intuitive navigation
* significantly improved code presentation
* richer Markdown capabilities
* better search usability
The documentation now has a **more polished, modern appearance** and improved usability for both readers and contributors.
Reviewed-on: #5
Co-authored-by: Vishesh 'ironeagle' Bangotra <aetoskia@gmail.com>
Co-committed-by: Vishesh 'ironeagle' Bangotra <aetoskia@gmail.com>
- Add MCPRenderer to generate MCP-native JSON bundles (index.json, nav.json, modules/*.json)
- Expose MCPRenderer via public API and CLI (`generate-mcp` command)
- Replace Markdown-based MCP output with structured JSON resources
- Update MCP renderer type stubs to match new JSON-based implementation
- Refactor MCP tests to validate JSON content, bundle structure, and navigation
- Fix MCP module coverage test to use explicit project_root for reliable discovery
