Knowledge and discovery primitives

This page loads only /v1/css/starthds-core.css, /v1/css/starthds-knowledge.css, /v1/js/starthds-core.js, and /v1/js/starthds-knowledge.js. Search, command, suggestions, tabs, filters, chips, tags, result cards, metrics, content headers, reading layouts, response cards, selected markers, reactions, comments, and community Q&A surfaces are generic StartHDS primitives. Applications own the search logic and product data.

Discovery primitives

Search, command, filters, and cards for generic content discovery.

StartHDS provides presentation and progressive interaction primitives only. Host applications own search data, routes, ranking, and persistence.

Read content
  • Reusable article patternsGuide · 8 minOpen
  • Trusted reference setCollection · updated today
Readable 2 filters applied
NeutralReference
SelectedPortable
GuideUpdated today

Design a content card contract

A product-neutral result card can show title, excerpt, metadata, media, tags, actions, and selected markers without owning search behavior.

TrustedReading
TrustedOpen

Compact result

A dense reusable result surface.

Community knowledge

Comments, community cards, and Q&A surfaces.

These primitives style discussion-like content without owning identity, moderation, ranking, votes, or persistence.

  • Asked by a readerReference

    How should a product adapt this content surface?

    Compose generic classes and keep product-specific data outside StartHDS.

  • Answered by a contributorSelected answer

    Use product adapters around portable primitives.

    StartHDS only supplies the accessible presentation shell and progressive state toggles.

Comment author2 min ago

Comment cards stay product-neutral and readable.

Reply author

Reply cards can nest under comments without app-specific logic.

Community card

Use for groups, spaces, or cohorts.

Member card

Use for people or contributors.

Profile card

Use for compact identity summaries.

Knowledge-style reading contentPlain HTML

Readable content with metadata and actions

Use reading primitives for articles, help entries, reference pages, and response explainers.

GenericAccessible

Content section

Sections keep a comfortable measure using --hds-reading-measure and compose with tags, meta lists, and reaction controls.

Reference metadata

Type
Article
State
Reviewed

Compact section

A tighter content section variant.

Callout section

Products can add domain copy here while preserving StartHDS generic structure.