PDS proposals
← All proposals

Section Message

A copy of the PDS v2 Section Message (pds-section-message, same class names, props and behavior) with an agentic type (AI gradient border on a surface fill, the Agent Avatar as its leading icon (decided 2026-10-21; iconName picks its icon), the standard secondary Button as the CTA, a silver-muted Badge) and an avatarProps option for the avatar (halo, shape, size).

Extends a PDS componentOpen in Storybook

proposals/SectionMessage/context.md23 lines · View on GitHub

Section Message

Problem

The designer needs a local, editable copy of the PDS v2 Section Message to propose changes against. The published package ships it, but a proposal can only change local files.

Proposal

A copy of the PDS v2 Section Message (pds-section-message, same class names, props and behavior) with an agentic type (AI gradient border on a surface fill, the Agent Avatar as its leading icon (decided 2026-10-21; iconName picks its icon), the standard secondary Button as the CTA, a silver-muted Badge) and an avatarProps option for the avatar (halo, shape, size). Changes are recorded in decisions.md and custom.md. It builds on the v2 Section Message, so it is not net-new. Ready for dev 2026-10-20 (HANDOFF.md).

Source

PDS v2 reference checkout, src/components/notifications/SectionMessage/ at v2.0.0-beta.12.

Constraints

  • Keep the v2 API and class names so the port stays a copy.
  • Tokens only; the raw values in the source are listed in custom.md.

Open questions

  • Which treatment for the agentic message? See decisions.md.