Overview

This site is a version of awesome-azd focused on public Azure Developer CLI templates.

What shows up here

• only public repositories
• only repositories under nathanmcnulty
• only repositories whose names start with azd-

That keeps every entry tied to a public azd project with a clear starting point.

Follow the solution's guide

Each entry identifies a reviewed deployment shape: standalone template, wrapper, or catalog. Copy commands only when that entry provides them. Staged workflows and unknown sources link to repository instructions instead of inventing a generic azd init / azd up path. Review caveats and prerequisites before running commands.

A source profile is documentation evidence, not a claim that deployment, tenant permissions, endpoint behavior, or cleanup have been validated in your environment.

Site layout

• the homepage is the entry point and featured view
• /templates is the full gallery, modeled after the way awesome-azd separates discovery into a dedicated route
• /guide documents how the catalog is generated and maintained, including one generated page per solution

How data gets into the site

The catalog combines three distinct inputs:

1. GitHub discovery finds public azd-* repositories automatically.
2. Local metadata overrides in catalog/overrides.json improve titles, summaries, tags, and featured ordering.
3. Reviewed source profiles in catalog/profiles.json bind deployment commands and optional features to a source revision and evidence hash. A mismatch produces neutral, unknown guidance without commands or unsupported feature promises.

Local commands

npm install
npm start

npm start refreshes the catalog before starting the development server. npm run build and npm run typecheck use the checked-in catalog without discovery. To update catalog data explicitly, run npm run generate:catalog, then build only after that refresh succeeds. A successful build validates the saved snapshot, not the current state of remote default branches.