Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Define when to use it
Explain purpose, context and inappropriate uses. A service card and alert may share borders but communicate different things. Use real content, not empty shapes; builders need to know the decision each component supports and how it combines.
Include states and behaviour
Document loading, error, disabled, focus and long-content states. Define flexible and fixed parts across languages and viewports. Explain functional differences instead of disguising them as interchangeable visual options that can contradict the workflow.
Test independent reuse
Example: another person creates a new service card from documentation without copying a page. Check price, unit, link and state with a long title. Acceptance includes correct reuse, invalid-combination detection, version clarity and change ownership.
Key takeaways
- Document decisions and states so reuse preserves meaning.