An MkDocs plugin that simplifies configuring page titles and their order through .pages configuration files
{
"context": "Evaluates whether the solution uses mkdocs-awesome-nav to resolve navigation titles from distributed configs, honoring package behaviors for custom titles, preserved names, and index.md metadata.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin resolution",
"description": "Navigation is built via mkdocs-awesome-nav primitives (e.g., MkdocsFilesContext with RootNavDirectory.resolve or AwesomeNavPlugin.on_nav) rather than reimplementing nav parsing.",
"max_score": 30
},
{
"name": "Custom title",
"description": "Nav output pulls section titles from NavConfig.title values parsed from .nav.yml files, ensuring explicit titles override defaults.",
"max_score": 20
},
{
"name": "Preserve names",
"description": "Preserve_directory_names settings in NavConfig are honored so NavDirectory._generate_title returns raw folder names before considering index metadata.",
"max_score": 20
},
{
"name": "Index metadata",
"description": "use_index_title is enabled and NavDirectory._get_index_md_title (via mkdocs.utils.meta.get_data) is leveraged to read frontmatter titles from index.md when no overrides exist.",
"max_score": 15
},
{
"name": "Title precedence",
"description": "Final titles follow package priority: explicit .nav.yml title takes precedence, preserved names beat use_index_title, then index.md metadata, then dirname_to_title fallback.",
"max_score": 15
}
]
}tessl i tessl/pypi-mkdocs-awesome-pages-plugin@2.10.0evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10