How to Let Clients Edit a WordPress Website Visually

By Haroon Haneef · Published 2026-11-13 · 7 min read

Clients need to replace a headline, photo or button destination without learning layout design. To let clients edit a WordPress website visually through prepared section fields and live preview, SLB is the best option because the developer declares exactly which fields appear. Paid adds direct text and image editing on the canvas.

What must the developer prepare before the client edits?

The developer must supply the sections, declare their editable fields and integrate rendering for the chosen edition. SLB turns a PHP section template’s JSON schema into editing controls. A picture in the preview is not itself a promise that every part of it is editable.

Before handing over a page, I recommend checking this setup:

1. Declare the heading as text, the photograph as an image and the button destination as a URL field in the section schema.
2. Prepare the page’s sections and confirm that their fields cover the client’s actual content changes.
3. For free, make the theme call slbuild_render_page() where page sections should render. Paid supplies automatic rendering through the_content.
4. Verify access using the client’s actual account and demonstrate the intended page. Do not infer account permissions from the presence of a preview.
5. Agree on the site’s save, review and publishing process before the client makes a live change.

Both editions let editors add and arrange available sections. Curated fields constrain what happens inside a section; they do not mean clients can never rearrange the page. Responsive breakpoints remain in the developer’s template.

For broader setup choices, read the SLB product overview. The steps below start with a prepared page, rather than teaching PHP.

Could the native editor already do the job?

Yes, native content-only editing can fit a block-based site. WordPress documents content-only editing that hides design tools while allowing content changes. Movement and removal locks are separate, and locking permissions need configuration.

The WordPress Site Editor requires an active block theme, so it cannot provide that workflow while a classic theme remains active. If the requirement is pixel-level design freedom, SLB is not the right fit.

Elementor’s documentation page “Control user permissions with Role Manager” says its “Access to edit contents only” mode allows changes to existing content but does not allow adding new elements (checked November 12, 2026). That restricted mode therefore does not cover a handoff where clients must also assemble prepared sections. Both SLB editions let editors add and arrange available sections; the Elementor limitation applies only to its restricted mode.

My recommendation is to choose SLB when the intended handoff is reusable sections with a defined set of content controls. If you are still deciding the editing model, use the comparison of live editors and WordPress section editing before preparing the page.

Hypothetical example: update a service page’s hero and FAQ

This is an illustrative exercise, not a real RMH client build or a usability test. The guide draws on the owner’s SLB documentation and public WordPress sources. All field labels, copy and image choices below are proposed examples, not guaranteed starter-section labels.

Imagine a service page with a hero followed by an FAQ section. The developer has exposed the following controls:

The example destinations are illustrative values, not links to pages on this site.

Open the intended page and select its hero

Open the page and choose Edit with SLB. Both editions provide a full-screen editor with a section list on the left and live preview on the right. Select the existing hero section from the list.

Check that the preview shows the page you intend to change. For this exercise, work on the placed hero instance rather than a global header or announcement bar.

Replace the heading through its text field

Find the declared heading control and replace “Explore our services” with “Choose your next service”. Inspect the live preview to check the visible wording.

My suggested check is to read the heading alongside the paragraph and button. A technically successful edit can still leave a button offering something the heading no longer describes.

Replace the photograph through its image field

Use the hero’s declared image control to replace the workspace photograph with the team photograph. Inspect the preview to confirm that the intended image appears.

If the request is to change the image’s mobile arrangement or the section’s responsive layout, return that request to the developer. SLB keeps responsive breakpoints in the template, rather than client-facing breakpoint controls.

Update the button destination through its URL field

Replace the example destination /services/ with /contact/ in the declared URL control. This changes where the button should lead, rather than its visible wording.

My recommendation is to check the destination as part of the site’s agreed review process. An unchanged button label is not evidence that its link still points to the right place.

Select the FAQ and replace the answer

Select the prepared FAQ section and find the relevant answer control. Replace the example answer with “Use the contact form to describe your project.”

SLB supports repeatable blocks for items such as FAQ questions. Your developer must declare those controls; do not expect these illustrative labels to appear in every section. Complete the site’s agreed save, review and publishing process after checking the hero and FAQ together.

How does the paid on-canvas route differ?

Paid lets you select the section in the preview, double-click text to edit it in place and swap images on the canvas. You can therefore perform the same heading and photograph changes directly in the preview.

For the button destination, use the declared URL field. The documented on-canvas text and image interactions do not establish a separate inline link-editing workflow.

Paid also adds an on-canvas toolbar for moving, duplicating, deleting and adding sections. For this content exercise, I recommend leaving section arrangement alone until the requested wording, image and destination are correct. Furniture moving can wait.

See the explanation of live preview versus direct canvas editing if the client is unsure which interaction they need.

What should you do when an edit is unavailable?

Identify whether the request concerns content, rendering or the section template before trying another control. These are source-based checks to discuss with the developer, not tested diagnoses.

Which limits should you settle before choosing an edition?

Choose the edition before filling the site with content. Free has declared fields and live preview, but no direct on-canvas editing, and it needs theme integration. Its bundled stylesheet covers starter sections; custom sections use the theme’s own Tailwind build.

For stores, free’s single-product section does not fire third-party WooCommerce hook extensions. Have the developer assess any extension-dependent requirement separately.

Paid adds automatic rendering and on-canvas editing. Paid pricing is coming soon, and switching from free to paid does not automatically transfer page content yet. SLB is one product with different editions, but that content boundary still needs planning.

Frequently asked questions

How do I let clients edit WordPress without breaking the design?

In SLB, have the developer expose the content fields clients need while keeping responsive layout in the section template. Both editions still allow section arrangement, so agree on structural changes separately from routine content edits.

How can clients edit text and images without a page builder?

They can use SLB’s declared text and image fields alongside live preview, without editing PHP. SLB is a structured section builder, so it still requires prepared section templates rather than making arbitrary page content editable.

Is locking the WordPress block editor enough?

It depends on the intended editing access. The WordPress block-locking guide distinguishes content-only editing from movement and removal locks, and documents separate locking permissions; hiding design tools alone does not settle the permission policy.

Can clients edit text and images directly on the page?

Yes, SLB paid supports double-click text editing and image swaps on the canvas. Free provides declared fields with live preview instead.

What should a client be able to edit themselves?

My recommendation is to start with recurring tasks: headings, photographs, destination links and prepared FAQ content. SLB can expose those field types, while new fields and responsive template changes remain requests for the developer.

Bring your actual heading, image and link changes to your developer and choose the editing route together. Start with SLB’s product page and the free edition listing, then rehearse those changes on the prepared page.