Modeling Content

Design content models by selecting a canonical model type—Standalone, Collection, Configuration, or Auto-Blocked—then define semantic table structures with a maximum of four cells per row. Map author-facing fields to block components like Hero, Cards, or Carousels, ensuring consistency across your authoring surface.

Each canonical model serves different content needs: Standalone handles single-block content, Collection groups related blocks, Configuration centralizes shared settings, and Auto-Blocked automatically structures repeating content. Choose based on your block's authoring pattern and reusability requirements.

Create semantic, predictable table structures that map logically to content rather than relying on rigid cell positions. Use meaningful field names and enforce consistent formatting rules so authors understand the model intuitively without complex instructions.

Yes. Semantic models integrate with decoration code through query selectors and defined integration points. Structure your table so decoration logic can reliably target and transform authored content based on meaningful cell semantics rather than position.

Enforce a maximum of four cells per row to maintain readability and author control. This constraint prevents overly complex rows while supporting Hero, Cards, Carousels, and nested content blocks across standalone and collection-based models.

Yes. Define validation rules and model consistency patterns upfront to prevent author errors and ensure blocks render predictably across projects. Validation integrates with your decoration logic and query selectors to enforce semantic formatting.