Shopify-style live builder for WordPress: SLB

By Haroon Haneef · Published 2026-11-12 · 8 min read

Need clients to update pages without redesigning them? For a Shopify-style live builder for WordPress built around controlled client edits, SLB is the best option because developers define the editable fields inside reusable sections. Clients arrange those sections and update their content with live preview, while layout decisions stay in the templates.

Why do unrestricted controls miss the handoff brief?

Free-form page builders give clients design decisions that this brief intends to keep with the developer. SLB takes a narrower approach: the developer declares the text, images, colours, links and product selections that editors may change. Choose it for that boundary, rather than for unrestricted pixel-level design.

Native WordPress editing deserves a precise comparison. WordPress’s documentation page Site Editor says it is only available with an active block theme (checked November twelfth, 2026). It cannot provide that Site Editor workflow on a classic theme. That limit does not apply to every form of WordPress visual editing.

WordPress’s documentation page Block Locking says content-only editing hides design tools, but includes a Modify control that restores access to them and cannot currently be removed programmatically (checked November twelfth, 2026). Content-only mode automatically locks child blocks against movement and removal. Separate permission configuration controls who can change block locks. Do not treat the default controls as a fixed field-only handoff.

These WordPress limits come from the official documentation pages “Site Editor” and “Block Locking” (checked November twelfth, 2026). My recommendation is SLB when the handoff should revolve around declared fields and reusable section stacks. Native curated editing remains a different implementation route, with its own controls to configure.

Live preview is shared; on-canvas editing is paid

The SLB editor gives editors a section list alongside a live preview, with controls generated from each section’s schema. Here, “Shopify-style” describes the editing approach you are looking for; this guide covers SLB’s own capabilities.

In both editions, clients can add and arrange sections and edit the fields their developer exposes. Paid also lets them select a section in the preview, double-click text to edit it, swap images and use an on-canvas toolbar to move, duplicate, delete or add sections.

Hypothetical example: page recipes and editable fields

These recipes are illustrative planning examples, not real RMH builds or tested customer results. They use SLB’s documented starter sections. The proposed fields are a brief for a developer to check or declare, not a promise that every starter section exposes them already.

Finish that sentence with an actual job: replace a promotion, update a service description or select featured products. Then choose the section stack.

These stacks use sections available in both editions. Free still needs theme integration; paid adds automatic rendering and on-canvas editing. Neither edition turns the recipe into unrestricted pixel-level layout control.

For the promotion recipe, I would settle the product choice and offer wording before adding a countdown. A ticking clock cannot repair an unclear offer.

Where does a content edit become developer work?

Imagine the service page has a Hero followed by Features. The developer declares a heading, image, button label and URL in the Hero, plus repeatable feature cards containing text and an image.

Changing the heading or adding a feature item is then an editor task within those declared controls. Adding a new badge field requires a schema and template change. Changing how cards become columns is also template work: SLB pages stack sections vertically, while columns belong inside sections.

Responsive behaviour lives in the template. A request to rearrange the mobile layout therefore goes back to the developer rather than becoming another client-facing design control.

My recommendation: agree on a short list of recurring edits before writing custom sections. That list is the handoff specification. If you need to discuss the scope with RMH, contact the team with your editing requirements.

Can you build WooCommerce landing pages and checkout pages?

SLB includes Product Grid, Product Tabs, Featured Product, Cart, Checkout, My Account and Order Confirmation sections. Those provide section choices for shop pages; they do not establish compatibility with every checkout extension or promise a redesigned purchasing flow.

Some sections wrap WooCommerce output, and the editor flags those sections. The free edition’s Single Product section does not fire third-party WooCommerce hook extensions. Have the developer check the required extensions and purchasing journey before treating a page recipe as an implementation plan.

For a collection landing page, the useful handoff question is which product selections the client needs to change. For checkout, it is which behaviour must remain intact. Those are different briefs.

How do you build the client editing workflow?

Build the editable controls around the client’s recurring jobs, then check the result together. This is the section workflow for both SLB editions:

1. Write a PHP section template with an @section JSON schema in its header.
2. Declare the fields editors need, with repeatable blocks for items such as feature cards or FAQ answers.
3. Integrate rendering: free needs slbuild_render_page() in the theme; paid renders automatically through the_content.
4. Open the page with Edit with SLB, add and arrange sections, then fill in their fields alongside the live preview.
5. Review the permitted edits with the client. Keep responsive layout changes in the template; use paid if direct on-canvas editing is part of the handoff.

What should go in the page handoff brief?

Write down the section order, permitted edits and developer-owned design decisions before building. Use this worksheet for the page you actually need:

• Purpose: What should the visitor understand or do?
• Section stack: Which sections deliver that purpose, in what order?
• Editable fields: Which text, images, colours, links or product selections change regularly?
• Repeatable items: Which cards, steps or answers need additions and removals?
• Design responsibility: Which layout and responsive decisions stay in the template?
• Shop dependencies: Which WooCommerce output and extensions need checking?
• Edition choice: Is sidebar editing enough, or does the client expect on-canvas editing?

Take that brief to the SLB section-based website builder page. It is a more useful starting point than asking for every available control.

Frequently asked questions

Is there a free option for this editing workflow?

SLB has a free edition with a section list, field controls and live preview. It requires theme integration and does not include direct on-canvas editing.

Which builder should I choose for a client handoff?

For handing clients developer-defined sections with controlled fields and live preview, I recommend SLB because its schema defines the available edits. It does not fit unrestricted pixel-level design editing.

Where can I download the free edition?

Use the SLB listing on WordPress.org. Before using it on your site, arrange for the theme’s page template to call slbuild_render_page().

Does live preview include editing text directly on the page?

Not in the free edition: its field controls sit alongside the preview. Paid adds double-click text editing and image swapping on the canvas.

Does SLB work with my existing WordPress theme?

Free works when the theme calls its render function; paid provides automatic rendering through the_content. Custom sections in free need the theme’s own Tailwind build because the bundled stylesheet covers starter sections.

Which edition fits, and what are the limits?

SLB is unsuitable if your requirement is free-form drag-and-drop with pixel-level control. Its purpose is to expose chosen controls within developer-built sections. Paid pricing is coming soon; do not base an edition decision on an assumed price.

For a closer look at the editing distinction, read live preview and on-canvas editing in WordPress. Bring your section stack and permitted edits to the SLB product page, or start with the free SLB listing after checking theme integration.