Documentation and Samples in Blazor Demo not Copilot Friendly

[jstynder]

🙋 Feature Request

When copilot scaffolds code for FluentUI, it has definitive/authoritive page to consult. Copilot Friendly Documentation would be beneficial.

🤔 Expected Behavior

Easy plain html for copilot to scan and then use in scaffolding.

😯 Current Behavior

It hulicinates, and seems to be getting incorrect properties and Values for Components.

💁 Possible Solution

Html scannable pages .

🔦 Context

When using copilot scaffolds incorrect use of components.

💻 Examples

this is one it consistently gets wrong

@if (!string.IsNullOrEmpty(_status))
{
    <div style="margin-top:8px">
        <FluentMessageBar>@_status</FluentMessageBar>
    </div>
}

[vnbaaij]

See also #4368.

As long as there is as much info as there is for the Fluent UI React components, it will almost certainly be using that in it's responses. No real good way to prevent that, I'm afraid.

About the html scanable pages, our docs site is just plain html.

Having a MCP server will lead to much better quality results.

I'll move this to the discussion area so others can chime in about what we can do to make things work better with AI systems like Copilot.