documentation

To write MkDocs documentation for Blazor components, use a modular doc template enforcing consistent frontmatter with name and description fields, covering component docs, migration guides, and utility references within the /docs folder.

The required MkDocs frontmatter structure mandates at least a name and description field. This consistent frontmatter pattern ensures standardized documentation metadata across all component docs, migration guides, and utility feature references.

To create a migration guide for BlazorWebFormsComponents, apply the provided documentation templates within the /docs folder, linking to Microsoft references and live samples while following the enforced style guidelines and navigation structure.

Yes, this documentation skill supports utility feature references alongside component documentation. It provides modular templates and style guidelines for both utility features and component docs within the /docs directory, ensuring consistent structure.

The best way to configure MkDocs navigation for Blazor documentation is to follow the recommended navigation and MkDocs configuration guidance provided, which structures component docs, migration guides, and utility references with links to Microsoft references and live samples.

Yes, the skill provides practical, copy-paste-ready examples for documentation patterns and style guidelines. These templates cover components, migrations, and utility features, ensuring consistent frontmatter and modular structure within the /docs folder.