What problem does it solve?
Create clear, predictable content models that make it easy for authors to compose page content and for developers to reliably render blocks. Poorly designed models lead to author confusion, inconsistent data, and fragile decoration code; this skill removes that friction by prescribing semantic, reusable structures.
Core Features & Use Cases
- Canonical patterns: Guides selection between Standalone, Collection, Configuration, and Auto-Blocked models to fit the block's purpose.
- Validation & best practices: Checklists and anti-patterns to enforce semantic formatting, a maximum of four cells per row, and predictable author inputs.
- Advanced scenarios: Solutions for nested blocks, per-item configuration, list handling, and form strategies with examples and trade-offs.
- Use Case: Design a card grid for a product listing using the Collection model so each row becomes a card with image and content, or convert three consecutive sections into an auto-blocked tabs component for simpler authoring.
Quick Start
Design a content model for a hero block with image, heading, body text, and CTA following the canonical models and the four-cells-per-row guideline.