Skip to content

chore: standardize mkdocs.yml footer, copyright, and theme across all sub-repos #38

@kristopherjturner

Description

@kristopherjturner

Summary

Track and coordinate standardization of MkDocs theme, footer, copyright, and branding across all Azure Local sub-repositories. This is a cross-repo issue to ensure consistent user experience across the documentation ecosystem.

Background

All sub-repos use MkDocs Material theme. A canonical template has been defined and partially applied. This issue tracks remaining work.

Canonical Template Requirements

Every sub-repo's mkdocs.yml must include:

Theme Block

  • Dark mode palette toggle (scheme: default and scheme: slate with blue/teal brand colors)
  • navigation.footer feature
  • content.code.annotate feature
  • icon.repo: fontawesome/brands/github
  • Logo and favicon pointing to the repo's icon SVG

Extra Block

Copyright

Copyright &copy; 2026 Azure Local. Designed and maintained by <a href="https://www.hybridsolutions.cloud">Hybrid Cloud Solutions</a>.

site_author

Azure Local Cloud

Status

Repo Dark Mode Footer Copyright 2026 site_author Logo/Favicon Social Links
azurelocal-avd ❌ (issue #45)
azurelocal-sofs-fslogix ❌ (issue #86)
azurelocal-loadtools ❌ (issue #22)
azurelocal-vm-conversion-toolkit ❌ (issue #15)
azurelocal-nutanix-migration ❌ (issue #5)
azurelocal-training ❌ (issue #26)
azurelocal-ranger
azurelocal-S2DCartographer
azurelocal-copilot ❌ (inactive mkdocs.yml) N/A N/A N/A ❌ (issue #2) N/A

Related Issues

  • Per-repo logo/banner issues: avd#45, sofs-fslogix#86, loadtools#22, vm-conversion-toolkit#15, nutanix-migration#5, training#26, copilot#2

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions