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.
Knowledge example
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.
Suggestions
No application search logic runs in StartHDS.
- Reusable article patternsOpen
- Trusted reference set
Compact result
A dense reusable result surface.
Generic response card
Response cards hold generated, editorial, support, or reference-style content while the host application owns data and state.
This summary is generic and portable.
Compact successful response
24Results
3Filters
0App dependencies
Community knowledge
Comments, community cards, and Q&A surfaces.
These primitives style discussion-like content without owning identity, moderation, ranking, votes, or persistence.
How should a product adapt this content surface?
Compose generic classes and keep product-specific data outside StartHDS.
Use product adapters around portable primitives.
StartHDS only supplies the accessible presentation shell and progressive state toggles.
Community card
Use for groups, spaces, or cohorts.
Member card
Use for people or contributors.
Profile card
Use for compact identity summaries.
Readable content with metadata and actions
Use reading primitives for articles, help entries, reference pages, and response explainers.
Content section
Sections keep a comfortable measure using --hds-reading-measure and compose with tags, meta lists, and reaction controls.
Reference metadata
Compact section
A tighter content section variant.
Callout section
Products can add domain copy here while preserving StartHDS generic structure.
CComment author2 min ago
Comment cards stay product-neutral and readable.