# 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>
136 lines
3.8 KiB
Python
136 lines
3.8 KiB
Python
"""
|
|
Navigation specification model.
|
|
|
|
This module defines the ``NavSpec`` class, which represents the navigation
|
|
structure defined by the user in the doc-forge navigation specification
|
|
(typically ``docforge.nav.yml``).
|
|
"""
|
|
|
|
from pathlib import Path
|
|
from typing import Dict, List, Optional
|
|
|
|
import yaml
|
|
|
|
|
|
class NavSpec:
|
|
"""
|
|
Parsed representation of a navigation specification.
|
|
|
|
A ``NavSpec`` describes the intended documentation navigation layout before
|
|
it is resolved against the filesystem.
|
|
|
|
Attributes:
|
|
home: Relative path to the documentation home page (for example
|
|
``index.md``).
|
|
groups: Mapping of navigation group titles to lists of file patterns
|
|
or glob expressions.
|
|
"""
|
|
|
|
def __init__(
|
|
self,
|
|
home: Optional[str],
|
|
groups: Dict[str, List[str]],
|
|
) -> None:
|
|
"""
|
|
Initialize a NavSpec instance.
|
|
|
|
Args:
|
|
home: Relative path to the home document.
|
|
groups: Mapping of group names to lists of path patterns
|
|
(glob expressions).
|
|
"""
|
|
self.home = home
|
|
self.groups = groups
|
|
|
|
@classmethod
|
|
def load(cls, path: Path) -> "NavSpec":
|
|
"""
|
|
Load a navigation specification from a YAML file.
|
|
|
|
Args:
|
|
path: Filesystem path to the navigation specification file.
|
|
|
|
Returns:
|
|
A ``NavSpec`` instance representing the parsed configuration.
|
|
|
|
Raises:
|
|
FileNotFoundError: If the specified file does not exist.
|
|
ValueError: If the file contents are not a valid navigation
|
|
specification.
|
|
"""
|
|
if not path.exists():
|
|
raise FileNotFoundError(path)
|
|
|
|
data = yaml.safe_load(path.read_text(encoding="utf-8"))
|
|
|
|
if not isinstance(data, dict):
|
|
raise ValueError("Nav spec must be a mapping")
|
|
|
|
home = data.get("home")
|
|
groups = data.get("groups", {})
|
|
|
|
if home is not None and not isinstance(home, str):
|
|
raise ValueError("home must be a string")
|
|
|
|
if not isinstance(groups, dict):
|
|
raise ValueError("groups must be a mapping")
|
|
|
|
for key, value in groups.items():
|
|
if not isinstance(key, str):
|
|
raise ValueError("group names must be strings")
|
|
if not isinstance(value, list) or not all(
|
|
isinstance(v, str) for v in value
|
|
):
|
|
raise ValueError(f"group '{key}' must be a list of strings")
|
|
|
|
return cls(home=home, groups=groups)
|
|
|
|
def all_patterns(self) -> List[str]:
|
|
"""
|
|
Return all path patterns referenced by the specification.
|
|
|
|
Returns:
|
|
A list containing the home document (if defined) and all
|
|
group pattern entries.
|
|
"""
|
|
patterns: List[str] = []
|
|
|
|
if self.home:
|
|
patterns.append(self.home)
|
|
|
|
for items in self.groups.values():
|
|
patterns.extend(items)
|
|
|
|
return patterns
|
|
|
|
|
|
def load_nav_spec(path: Path) -> NavSpec:
|
|
"""
|
|
Load a navigation specification file.
|
|
|
|
This helper function reads a YAML navigation file and constructs a
|
|
corresponding ``NavSpec`` instance.
|
|
|
|
Args:
|
|
path: Path to the navigation specification file.
|
|
|
|
Returns:
|
|
A ``NavSpec`` instance representing the parsed specification.
|
|
|
|
Raises:
|
|
FileNotFoundError: If the specification file does not exist.
|
|
ValueError: If the YAML structure is invalid.
|
|
"""
|
|
if not path.exists():
|
|
raise FileNotFoundError(path)
|
|
|
|
data = yaml.safe_load(path.read_text(encoding="utf-8"))
|
|
|
|
if not isinstance(data, dict):
|
|
raise ValueError("Nav spec must be a YAML mapping")
|
|
|
|
return NavSpec(
|
|
home=data.get("home"),
|
|
groups=data.get("groups", {}),
|
|
)
|