Follow-up to #96, found while checking the Terraform repo against the nav change.
The problem
lyrathorpe/docs-site#2 removes the hardcoded nav: so awesome-pages can discover the synced trees. That nav also carried the section labels:
nav:- Terraform:terraform- nixfiles:nixfiles
Without it, MkDocs derives each section name from its directory and title-cases it. terraform still renders as "Terraform", so that section is unaffected — but nixfiles becomes "Nixfiles".
The fix
Set title: nixfiles in docs/.pages. That keeps the label where the section owns it, rather than putting a nav entry back in the site repo.
Validation
Rebuilt the aggregated site locally with both source trees synced exactly as build.yml does (mkdocs 1.6.1, mkdocs-material 9.7.7, awesome-pages 2.10.1): no nav warnings, section renders as nixfiles, page order unchanged. nix flake check passes.
Follow-up to #96, found while checking the Terraform repo against the nav change.
## The problem
`lyrathorpe/docs-site#2` removes the hardcoded `nav:` so awesome-pages can discover the synced trees. That nav also carried the section labels:
```yaml
nav:
- Terraform: terraform
- nixfiles: nixfiles
```
Without it, MkDocs derives each section name from its directory and title-cases it. `terraform` still renders as "Terraform", so that section is unaffected — but `nixfiles` becomes **"Nixfiles"**.
## The fix
Set `title: nixfiles` in `docs/.pages`. That keeps the label where the section owns it, rather than putting a nav entry back in the site repo.
## Validation
Rebuilt the aggregated site locally with both source trees synced exactly as `build.yml` does (mkdocs 1.6.1, mkdocs-material 9.7.7, awesome-pages 2.10.1): no nav warnings, section renders as `nixfiles`, page order unchanged. `nix flake check` passes.
With no entry in the docs-site nav (removed there so awesome-pages can
discover the synced trees), MkDocs derives the section name from the directory
and title-cases it, rendering "Nixfiles". The previous hardcoded nav spelled it
lowercase. Setting title in docs/.pages restores that without reintroducing a
nav entry.
Verified by rebuilding the aggregated site locally with both source trees
synced as the workflow does.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #96, found while checking the Terraform repo against the nav change.
The problem
lyrathorpe/docs-site#2removes the hardcodednav:so awesome-pages can discover the synced trees. That nav also carried the section labels:Without it, MkDocs derives each section name from its directory and title-cases it.
terraformstill renders as "Terraform", so that section is unaffected — butnixfilesbecomes "Nixfiles".The fix
Set
title: nixfilesindocs/.pages. That keeps the label where the section owns it, rather than putting a nav entry back in the site repo.Validation
Rebuilt the aggregated site locally with both source trees synced exactly as
build.ymldoes (mkdocs 1.6.1, mkdocs-material 9.7.7, awesome-pages 2.10.1): no nav warnings, section renders asnixfiles, page order unchanged.nix flake checkpasses.