write-example-description

To write PatternFly example descriptions, draft prose under component example headings and demo sections that explains purpose and usage. Descriptions must follow PatternFly MCP content guidelines for tone, structure, and cross-linking to ensure accessibility and consistency across PatternFly.org.

PatternFly demo descriptions follow a structured format under ## Demos / ### Demo name headings. They align with PatternFly MCP content guidelines, ensuring clear prose that explains the demo's purpose and usage while maintaining consistent brand voice and accessibility considerations.

Yes, you can draft documentation for component examples using PatternFly brand voice guidelines. The descriptions conform to PatternFly documentation standards and MCP guidelines, providing cross-links and tone guidance to improve accessibility and consistency for readers learning component usage.

To ensure accessibility considerations in PatternFly documentation, apply MCP content guidelines during the description drafting process. This involves structuring prose for component examples and demos with consistent tone, cross-linking, and accessibility standards that conform to PatternFly documentation guidelines.

Yes, writing example descriptions requires cross-linking to other PatternFly components. The process applies MCP guidelines for cross-linking and tone guidance, ensuring descriptions across PatternFly.org improve discoverability, learning, and consistency while conforming to documentation standards.