Components

Stable public classes use the hds- prefix. Optional ds-container, ds-button, and ds-card aliases are documented aliases only.

Generic control and status utilities

Core includes product-neutral control bars, status messages, skip links, active navigation states, and safe code wrapping for downstream app chrome without owning app data.

Saved

hds-control-barhds-control-bar__innerhds-control-bar__grouphds-control-bar__buttonhds-status-messagehds-skip-linkhds-active

Interactions, flows, and form feedback

Disclosure, sheet, menu, flow, choice card, upload, and save-status primitives are generic HTML/CSS contracts enhanced through data-hds-* attributes. See the interactions example.

hds-disclosurehds-sheethds-menuhds-flowhds-choice-cardhds-uploadhds-save-status

App and mobile layout primitives

Generic app shells, sidebars, mobile pages, appbars, icon buttons, sticky action bars, and bottom tab bars are documented on /docs/app and showcased at /examples/app-mobile.

hds-app-shellhds-app-mainhds-app-sidebarhds-app-asidehds-mobile-pagehds-appbarhds-sticky-action-barhds-mobile-tabbar

Dashboard bundle primitives

Product-neutral dashboard shells, stat cards, metric rows, user summaries, records/value tables, activity feeds, progress/status panels, toolbar/actions, and state surfaces are documented on /docs/dashboard and showcased at /examples/dashboard. Load /v1/css/starthds-dashboard.css after /v1/css/starthds-core.css; keep these classes out of the app/mobile bundle.

hds-dashboard-shellhds-dashboard-toolbarhds-dashboard-sectionhds-dashboard-gridhds-stat-cardhds-dashboard-usershds-dashboard-tablehds-dashboard-activity-feedhds-dashboard-status-summaryhds-dashboard-empty

Data bundle primitives

Generic data presentation primitives live in the dashboard CSS bundle and are documented on /docs/data with a copyable standalone showcase at /examples/data. Use core first, app CSS only when composing the edit sheet pattern, then dashboard/data CSS.

hds-data-toolbarhds-data-filter-barhds-data-tablehds-data-cell-actionshds-data-cardhds-data-listhds-data-recordhds-data-field-listhds-data-edit-sheethds-data-edit-sheet__statushds-data-edit-sheet__fieldshds-data-edit-sheet__footerhds-data-paginationhds-data-bulk-action-barhds-data-emptyhds-data-loadinghds-data-errorhds-sheet

Operations, trust, admin, and media detail primitives

Task cards, notifications, trust badges, notices, admin lists/tables, moderation items, bulk actions, attachments, and lightbox media remain generic hds-* contracts.

hds-task-listhds-notification-listhds-trust-badgehds-noticehds-tablehds-admin-listhds-moderation-itemhds-attachment-listhds-lightbox

Discovery and knowledge primitives

Search, command, suggestion, tabs, filter, chip, tag, result-card, reading, response-card, and reaction primitives are documented on /docs/knowledge and showcased at /examples/knowledge.

hds-searchhds-commandhds-tabshds-filter-barhds-result-cardhds-readinghds-response-cardhds-reaction-bar

Marketing components

Landing heroes, proof strips, benefit and feature grids, testimonials, pricing cards, FAQs, and CTA panels are documented on /docs/marketing and showcased at /examples/marketing. Markdown landing directives can render these same primitives from /examples/markdown-landing.

hds-landing-herohds-pricing-cardhds-faq-itemhds-cta-band

Media components

Video cards, course progress, lesson lists, article cards, galleries, breadcrumbs, and pagination are documented on /docs/media and showcased at /examples/media.

hds-media-cardhds-video-framehds-course-cardhds-gallery-itemhds-pagination

Social and community components

Social proof, reviews, comments, avatars, profiles, community cards, share bars, and social links are documented on /docs/social and showcased at /examples/social.

hds-social-proofhds-review-cardhds-comment-threadhds-community-cardhds-profile-cardhds-share-bar

Conversion and funnel components

Lead magnets, opt-in forms, webinars, events, countdowns, urgency notes, steps, timelines, comparisons, guarantees, and risk reversal are documented on /docs/conversion and showcased at /examples/conversion.

hds-lead-magnet-cardhds-optin-formhds-countdownhds-process-timelinehds-comparison-tablehds-comparison-cardhds-guarantee-cardhds-risk-reversal
Card

Token-backed surface

Use hds-card, hds-panel, hds-badge, and action classes.

Alert: feedback components inherit token colors.

Form contract

Operations and media primitives

Tasks, notifications, trust badges, notices, admin review, and attachments.

These primitives are generic StartHDS surfaces. Host applications own queues, permissions, files, and moderation state.

Info notice: Use notices for neutral updates, success, warning, danger, and trust messaging.
Success notice with semantic status tokens.
Warning notice for cautionary copy.
Danger notice for destructive or failed states.
Trust notice for verification or safety guidance.
VerifiedStaffExpertTrusted3
  1. Review urgent item

    Urgent task cards highlight priority without encoding product-specific queues.

    Priority · Due today

  2. Publish checklist

    Complete task cards can remain visible in histories or audit flows.

    Complete · 2 min ago

  • Unread notificationA generic unread state using notification tokens.
  • Read notificationRead items use the same calm surface.
ItemStatusOwner
Policy cardTrustedTeam
Attachment reviewStaffOps
  • Admin list item

    Use for generic operational records, permissions, or configuration rows.

  • Moderation item

    A warning-backed review surface for any product domain.

    Review
2 selected
  • PDFAttachment item2.4 MB · generic metadata
  • Image previewMedia detail surface
Lightbox media and captions are styling primitives only; applications own opening, routing, and asset data.