[Project] Create and integrate 10 new Azure Local solution repos

[kristopherjturner]

Summary

Create, configure, and fully integrate 10 new Azure Local solution repositories into the AzureLocal GitHub organization and the azurelocal.cloud website.

Each new repo must be built out as a placeholder matching the full structure of existing solution repos (azurelocal-avd, azurelocal-sofs-fslogix, etc.) — not just an empty repo. The placeholder signals intent, establishes standards, and allows GitHub Pages and the site nav to be wired up immediately.

Reference: Brainstorming issue — #5

---

New Repos to Create

Repo	Category	Solution
azurelocal-sql-ha	Workload	Highly available SQL Server (FCI or AG) on Azure Local
azurelocal-aks	Workload	AKS on Azure Local — deployment, lifecycle, and workload patterns
azurelocal-custom-images	Workload	Custom VM image build pipelines (Packer, Azure Image Builder)
azurelocal-vmware-migration	Migration	VMware vSphere to Azure Local migration runbooks and tooling
azurelocal-hydration	Migration	Server hydration tooling using the upcoming Hydration tool
azurelocal-bcdr	Operations	Azure Backup, Azure Site Recovery, DR runbooks
azurelocal-monitoring	Operations	Azure Monitor, Prometheus/Grafana, log aggregation
azurelocal-governance	Operations	Azure Policy, security baselines, CIS benchmarks
azurelocal-cost	Operations	Chargeback/showback, rightsizing, cost reporting
azurelocal-iot	Platform	IoT Hub integration and edge workload patterns

---

Tasks

1. Create Repos with Placeholder Structure (x10)

Each repo must be created under the AzureLocal org and fully scaffolded as a placeholder. Use azurelocal-avd as the reference template. Every file should contain appropriate placeholder content (e.g. "Coming Soon", status badge, link back to azurelocal.cloud).

• Create GitHub repo under AzureLocal org (public)
• Scaffold the following structure, matching the reference repos:
  • README.md — title, description, status: placeholder/coming soon, link to azurelocal.cloud docs
  • CHANGELOG.md — empty (release-please format)
  • CONTRIBUTING.md — standard contribution guide
  • LICENSE — MIT
  • mkdocs.yml — MkDocs config matching other solution repos
  • release-please-config.json
  • .github/CODEOWNERS
  • .github/labels.yml
  • .github/pull_request_template.md
  • .github/workflows/ — CI lint, MkDocs deploy to gh-pages, release-please
  • config/variables.example.yml
  • config/schema/
  • docs/index.md — placeholder
  • docs/getting-started.md — placeholder
  • docs/contributing.md — placeholder
  • docs/roadmap.md — placeholder
  • src/ — empty with .gitkeep
  • scripts/ — empty with .gitkeep
  • tests/ — empty with .gitkeep
  • styles/ — copy Vale styles from existing repo
• Apply standard branch protection (require PR, no direct push to main)
• Apply standard labels (type/*, priority/*, status/*, solution/*)
• Configure release-please via release-please-config.json

2. GitHub Pages

• Enable GitHub Pages on each repo (MkDocs deploy via GitHub Actions to gh-pages branch)
• Confirm site is accessible at https://azurelocal.github.io/<repo-name>/
• Verify MkDocs build passes and site renders placeholder content correctly

3. Solutions Dropdown — Top Nav (docusaurus.config.js)

The current Solutions dropdown has 5 entries. Adding 10 = 15 total — needs restructuring.

• Restructure into grouped categories:
  • Workloads: AVD, SQL HA, AKS, Custom Images
  • Migration: VM Conversion, VMware Migration, Hydration
  • Operations: BCDR, Monitoring, Governance, Cost
  • Platform: SOFS for FSLogix, Load Testing, IoT, Toolkit
• Add all 10 new repos with correct https://azurelocal.github.io/<repo>/ URLs
• Test dropdown renders correctly on desktop and mobile

4. Footer (docusaurus.config.js)

The current footer has a single Solutions column — too long at 15 entries.

• Split footer Solutions into multiple grouped columns by category (matching nav groups above)
• Verify renders correctly at all breakpoints

5. Azure Services on Azure Local Docs (docs/azure-services/)

• Update existing pages to link to new repos:
  • aks-on-azure-local.md → link to azurelocal-aks
  • iot-operations-on-azure-local.md → link to azurelocal-iot
  • sql-managed-instance-on-azure-local.md → note relationship to azurelocal-sql-ha (MI vs FCI/AG — clarify distinction)
• Create new pages for gaps:
  • vmware-migration-on-azure-local.md
  • bcdr-on-azure-local.md
  • monitoring-on-azure-local.md
  • governance-on-azure-local.md
  • cost-management-on-azure-local.md
  • custom-images-on-azure-local.md
  • hydration-on-azure-local.md
• Update _category_.json and sidebar as needed

6. Solutions Index Page

• Update or create a /solutions index page on azurelocal.cloud listing all repos in a card/grid layout grouped by category

---

Acceptance Criteria

• All 10 repos exist under AzureLocal org with full placeholder structure
• All 10 have GitHub Pages active and accessible
• MkDocs builds and deploys without errors on all repos
• Solutions dropdown on azurelocal.cloud is grouped and includes all 15 solutions
• Footer is grouped by category and includes all 15 solutions
• docs/azure-services/ has pages covering all solution areas
• No broken links in nav, footer, or docs