azd template artifacts

Reference docs and copyable assets for authoring Azure Developer CLI (azd) templates and preparing them for collection submission.

This repository is not a deployable template. It is a guidance and standards package for template authors and maintainers.

Start here

• Guidance entry point — navigation plus the shared meaning of MUST, SHOULD, and MAY
• Template README — copyable README.md authors can adapt for their own template repositories
• Definition of done — measurable completion checklist
• Development process — default GitHub flow for building and reviewing template changes
• Operational guidelines — ownership, maintenance, and governance guidance
• Recommended practices — cross-cutting security, portability, testing, and operations guidance
• Template configuration — azure.yaml, hooks, services, pipelines, and dev containers
• Troubleshooting — durable diagnostics for azd, Azure, identity, and CI/CD failures
• Structure samples — example repository layouts by language
• Publishing guidelines — how to validate and submit to the public Awesome AZD collection

Requirement layers

• Core azd requirements: an azure.yaml file plus the infrastructure and application assets needed for the template scenario.
• Awesome AZD collection requirements: documentation, metadata, and submission steps needed to list a template in the public collection.
• Optional repository enhancements: dev containers, GitHub Codespaces, CI/CD pipelines, and other maintainability improvements.

Use the normative language defined in docs/readme.md when reading the guidance in this repository.