A page builder needs boundaries.
A useful page builder gives editors meaningful choices. Start with the decisions they need to make, then design the blocks around them.
A blank page builder can look generous. Add a section, choose a width, pick a colour, adjust the spacing, repeat. But each extra choice asks the editor to do a little more design work before they can publish a sentence.
For Morrow Clay, I would rather an editor decide which workshop to feature than choose how many pixels should separate its heading from an image.
Name the job
“Featured workshop” is more helpful than “Two-column block.” The first describes a reason to add the section. The second describes its appearance and leaves the editor to invent its purpose.
A useful section has a small contract: a heading, a workshop entry, a short introduction, and a link. The template handles the arrangement. That makes the section recognisable across pages and gives the editor fewer ways to produce an awkward result.
Offer the choices that matter
Some variation is useful. A gallery might need a quiet grid or one large lead image. Those choices can be named and demonstrated. They do not require a full set of spacing and colour controls.
Statamic’s Replicator field supports sets of fields that can be added and arranged. The important design work is deciding which sets belong in the project. See the Replicator documentation.
Test the ordinary update
Before calling a builder finished, try changing the featured workshop, removing an image, and doubling the heading length. Then ask someone unfamiliar with the layout to make the same changes.
If a normal edit requires a long explanation, I look for a clearer field name or a smaller decision. A good boundary is something the editor experiences as confidence: this is the place to make the change, and the page will still hold together.