Card

Overview

Card is a hairline-bordered ContentControl surface, no shadow, matching the web contract’s div-based parts. It is compositional: nest NaviusCardHeader, NaviusCardContent, and NaviusCardFooter directly inside the root’s Content, or use the root alone for a plain panel. NaviusCardTitle and NaviusCardDescription are typically nested inside NaviusCardHeader. Each subpart is a padded ContentControl with a fixed padding rhythm so header, content, and footer blocks align.

Usage

xmlns:card="clr-namespace:Navius.Wpf.Ui.Card;assembly=Navius.Wpf.Ui"

<card:NaviusCard MaxWidth="360">
    <StackPanel>
        <card:NaviusCardHeader>
            <StackPanel>
                <card:NaviusCardTitle Content="Deployment" />
                <card:NaviusCardDescription Content="navius-docs, production" />
            </StackPanel>
        </card:NaviusCardHeader>
        <card:NaviusCardContent>
            <TextBlock Text="Last deployed 12 minutes ago." TextWrapping="Wrap" />
        </card:NaviusCardContent>
        <card:NaviusCardFooter>
            <TextBlock Text="Live" />
        </card:NaviusCardFooter>
    </StackPanel>
</card:NaviusCard>

Properties

Property	Type	Default	From	Description
`Content`	`object`	`-`	`ContentControl` (`NaviusCard`)	The card body; nest `NaviusCardHeader`/`NaviusCardContent`/`NaviusCardFooter` directly, or use alone for a plain panel.
`Content`	`object`	`-`	`ContentControl` (`NaviusCardHeader`)	Top padding block (16,16,16,8); typically holds `NaviusCardTitle`/`NaviusCardDescription`.
`Content`	`object`	`-`	`ContentControl` (`NaviusCardTitle`)	The card’s title, styled with weight/size hierarchy, no distinct color.
`Content`	`object`	`-`	`ContentControl` (`NaviusCardDescription`)	The card’s supplementary text, muted foreground.
`Content`	`object`	`-`	`ContentControl` (`NaviusCardContent`)	The body block (16,8,16,16 padding), aligned with header/footer.
`Content`	`object`	`-`	`ContentControl` (`NaviusCardFooter`)	The bottom block (16,0,16,16 padding), typically a row of actions.

UIA mechanism

None of the six Card types overrides OnCreateAutomationPeer, and ContentControl’s base implementation does not create one either, so none has an automation peer of its own; assistive technology sees only each part’s template (borders and content presenters) and any interactive content nested inside. The unit suite exercises template application and part composition (Card_TemplateApplies_AndPartsCompose in tests/Navius.Wpf.Tests/UiDisplayItemsTests.cs), not an automation surface. The M6 audit found this family clean: token-only surfaces, no template parts, no animations, no bindings at risk.