Blazor Widget Alignment

1. The shape already fits — it just needs the right names

The draft is a dynamic-widget system: a flat WidgetDto (with a string Type) is fed by IWidgetApiService and rendered by a single Widget.razor that switches on WidgetType. That is compatible with this architecture once reframed:

• WidgetDto is the raw API representation. Mapping each one to the right scaffold ViewModel is exactly the RawRepresentationFactory<T> + domain-control pattern (D11).
• DynamicWidgets.razor / Widget.razor become the feed renderer over scaffold components + domain controls — not one mega-switch.
• The Blazor WidgetType names just need to reconcile to our universal taxonomy.

2. WidgetType → component / domain-control map

From Components/WidgetType.cs + the render cases in Components/Widget.razor:

3. WidgetDto → RawRepresentationFactory

ApiModels/WidgetDto.cs is a flat catch-all (a string Type + every possible field: Title/Blurb/Cta/Icon/ThreeUpButtons/Slider*). Under D11 that DTO is the raw representation; a factory keyed on Type projects it onto the right typed scaffold ViewModel:

// WidgetDto (raw) -> scaffold ViewModel, dispatched by Type
public sealed class WidgetFactory : RawRepresentationFactory<ComponentViewModel>
{
    public ComponentViewModel Create(WidgetDto w) => w.Type switch
    {
        "PilotCard"         => pilotCardFactory.Create(...),                 // CardViewModel
        "SingleButtonLarge" => documentHeroFactory.Create(w),               // CardHeroViewModel (content card)
        "SingleButton1" or "SingleButton2" or "EmergencyButton"
                            => buttonFactory.Create(w),                      // ButtonViewModel
        "ThreeUpButton"     => buttonGroupFactory.Create(w.ThreeUpButtons), // ButtonGroupViewModel
        "SliderImages" or "SliderNoImages" or "SliderNoImagesEyebrows"
                            => feedCarouselFactory.Create(w.SliderItems),    // CarouselViewModel
        _ => throw new NotSupportedException(w.Type),
    };
}

Field reconciliation for the reclassified card: SingleButtonLarge → CardHeroViewModel with Title → Title, Blurb → Description, Icon → Image. Keyed services (.NET 8+) can resolve the per-type factory by key instead of the switch.

4. Gaps & reconciliation for the alignment task

• Reclassify SingleButtonLarge → content card (Hero/Document); rename off the "button" label. (the headline item)
• Rename to the universal taxonomy: SingleButton1/2 → Button (Icon variant) · ThreeUpButton → Button Group · Slider* → Carousel variants · EmergencyButton → Button (Emergency Hotline).
• Split the god-DTO: map WidgetDto → typed scaffold VMs via the factory above (keep the factory a pure mapper — no IServiceProvider; the async gather stays in the API service).
• Reframe the host: DynamicWidgets/Widget render scaffold components / domain controls, not a mega-switch of inline markup.
• Namespace/naming: ALPADocs.Components / ALPADocs.ApiModels vs our universal component names.
• Not yet in the draft (present in the Home design): CardSmall / Resource Tile (the card-sm nav rows), the section-title headers, and the non-Home components (Menu Text, List).

5. Branch files in scope