Component docs with tabs, accordions, and code blocks
The accidental prototype tried to render custom docs-tabs and docs-accordion blocks. We do not need a special renderer for that. The useful product answer is simpler: component docs should put examples, code, and optional detail in a clear scan path. Useful patterns: 1. Use tabs for equivalent variants: frameworks, platforms, examples, or states. 2. Use accordions for optional depth: props, accessibility, migration notes, and edge cases. 3. Keep code blocks close to the claim they prove. 4. Do n
Show component docs with tabs, accordions, and code blocks
The accidental prototype tried to render custom docs-tabs and docs-accordion blocks. We do not need a special renderer for that. The useful product answer is simpler: component docs should put examples, code, and optional detail in a clear scan path.
Useful patterns:
- Use tabs for equivalent variants: frameworks, platforms, examples, or states.
- Use accordions for optional depth: props, accessibility, migration notes, and edge cases.
- Keep code blocks close to the claim they prove.
- Do not hide the primary setup path behind a disclosure control.