Skip to main content

Page Builder Roadmap

This is a living roadmap for the Page Builder's layout system. It's here so you can see what's coming and why. Backward compatibility is a hard rule — see Your existing pages — so nothing here breaks what you've already built.

Status legend

🟢 Shipped  ·  🟡 In progress  ·  ⚪ Planned  ·  🔵 Exploring

The direction: one simple layout model

The layout system is moving from the classic Section → Row → Column (Bootstrap) grid to one primitive — the Div — a container you set to Flex, Grid, or Block. That's the whole model. It maps directly to real, modern HTML/CSS, and it means there's one way to lay out a page instead of two.

Section → a full-width band (a <section>) ← start here
Grid → columns inside it ← "I want columns"
Flexbox → a row or a stack inside it ← "I want things in a row"
↳ your content

That structure is exactly how a developer writes it by hand — <section><div class="grid">…</div></section> — so the builder now teaches good structure instead of hiding it behind a grid framework. If you're new to this, the Bootstrap columns → CSS Grid & Flexbox guide explains Flex vs Grid vs Block from scratch.

What you'll see in the palette

The Layout tab leads with the modern primitives; the classic Bootstrap elements move into a Classic group (still fully supported):

TileCreatesFor
Sectiona modern Div, tagged <section>, with contained contentthe root band of a page — where you start
Grida Div set to display: gridcolumns (a card grid, an even split, a hero)
Flexboxa Div set to display: flexa one-dimensional row or stack that can wrap
Classic ▸Section (Bootstrap) · Row · Columnexisting pages & anyone who prefers the old grid

A beginner's instinct — "click Section, it's the main content area" — now lands on the modern primitive, not the legacy one. No one has to understand "flex" or "grid" to start a page; they discover Grid the moment they want columns.

Columns without the math (but the fractions stay)

Modern builders dropped the palette of fixed column structures. Instead of picking "1/3 + 1/3 + 1/3" up front, you set a Grid and say how many columns — children fill the tracks. But the fractions you know aren't going anywhere:

  • They live on as Width presets on a cell — 1/2, 1/3, 1/4, 2/3, 5/6… are all still one click.
  • Under the hood a 1/3 cell becomes grid-column: span 4, a 2/3 cell becomes span 8 — modern CSS Grid instead of a Bootstrap col-* class.
  • An uneven split like 1/3 + 2/3 is a Grid with grid-template-columns: 1fr 2fr, or two cells at span 4 and span 8.
  • Auto columns fill the remaining space (the grid equivalent of flex: 1).

So the feel is the same — familiar fractions — while the output is clean, responsive CSS Grid.

What's coming

PhaseWhatStatus
Content Width on the DivA container option so a full-width section Div centres its content to a max-width (no accidental full-bleed).🟡 In progress
Converter → flex/gridThe Site Converter rebuilds a source's content rows as flex/grid Div rows instead of Bootstrap columns.🟡 In progress
Div = default wrapperDropping an element on an empty canvas wraps it in a Div (tagged section at the root, div when nested) — not Section → Column.⚪ Planned
Modern paletteSection (modern Div) / Grid / Flexbox lead the Layout tab; Bootstrap moves to Classic.⚪ Planned
Columns as GridDrop cells into a Grid Div; fractions become grid spans (1/3span 4).⚪ Planned
Convert to GridAn opt-in action to modernise an existing Bootstrap row into a Grid Div — using the same translation the converter uses.⚪ Planned
Live Editor parityEvery new behaviour works identically in the backend builder and the front-end Live Page Editor.⚪ Planned

Your existing pages

This is an evolution, not a rip-out:

  • Every existing Section / Row / Column page keeps rendering and editing — the Bootstrap shortcodes are not removed, only demoted to the Classic palette group.
  • The two models coexist. New pages lead with the Div; old pages stay classic until you choose otherwise.
  • A "Convert to Grid" action (planned) modernises a classic row on demand — opt-in, per row, never automatic. It reuses the Site Converter's existing col → grid span translation.
  • Nothing forces a big-bang rewrite. Migrate a page when it suits you, or leave it.

Principles

  • Straightforward for newcomers — one obvious way to lay out a page; no dual systems in your face.
  • Nothing breaks — backward compatibility is non-negotiable.
  • Clean output — semantic HTML and vanilla CSS (grid spans, not a wall of utility classes).
  • Teaches good structure — the builder mirrors how a developer hand-writes a modern layout.
This roadmap will move

Scope and order can change as the work lands and as feedback comes in.