The auto-layout engine
The engine picks the right layout for the content you add.
There are twenty-one distinct layouts. Each one is the correct answer to a specific combination of three signals: what the parent looks like, how many children it has, and what those children look like.
The engine reads those three signals for every section and selects the right layout without being asked. No template picker, no layout dropdown, no manual override needed.
This is not a smart default that usually works. It is a deterministic mapping. Every possible combination of signals has exactly one correct layout, and the engine applies it. Write your content. The presentation is already decided.
Twenty-one layouts, one per content shape
Three lead modalities. Four count buckets. Three group modalities. Each combination maps to one layout, designed specifically for that content shape. Not a closest match. Not a sensible approximation. The layout built for exactly what you wrote.
Three lead modalities. Four count buckets. Three group modalities. Each combination maps to one layout, designed specifically for that content shape. Not a closest match. Not a sensible approximation. The layout built for exactly what you wrote.
Lead item modality
Photograph, icon, or text. Determines the visual register of the section's opening.
Supporting item count
One, two, three, or many. Determines the grid structure.
Group modality
Photograph, icon, or text, resolved across the supporting items as a set.
How the engine resolves a layout
Four signals in. One layout out. Always the same answer.
The engine evaluates three signals in sequence: the parent's modality, the number of children, and the children's modality. Those three inputs resolve to a single template path. The decision is deterministic, consistent, and instantaneous. The same content will always produce the same layout.
Manual overrides
The engine is right most times. Two fields fix the rest.
The automatic resolution is correct in the vast majority of cases. When it isn't, two fields let you correct it precisely. One controls how the section renders on its own page. The other controls how it renders when listed alongside similar sections. Everything else stays automatic.
Page-level override
Controls the layout for this section on its own dedicated page. Use when the automatic choice is wrong for this specific case.
Catalog-level override
Controls the layout when this section appears in a listing alongside others. Use to enforce visual consistency across a catalog.
