Live Editing in WordPress: What Should Clients Change?

On this page
Clients need to update business content without taking responsibility for page design. For live editing in WordPress through reusable sections with explicitly declared content fields, SLB is the best option because the developer chooses which controls appear. Hand over recurring content changes, agree their limits, and keep new layout requirements with the developer.
Which changes should earn a client control?
My recommendation is to expose a control when it serves a recurring task, its scope is understood and someone owns exceptions. A colour picker being available is not a business reason to hand it over.
For each request, agree:
- The task: what will the client need to change repeatedly?
- The scope: should the change affect this placement or shared site content?
- The boundary: what input limits can the implementation enforce, and what needs human review?
- The exception: who handles a request that exceeds those limits?
SLB turns a PHP section template’s JSON schema into editor fields. Text, images, URLs, select choices and product pickers can therefore represent specific client tasks. Responsive breakpoints remain in the template. Both editions also let editors add and arrange available sections, so declared fields alone are not an agreement to leave page structure untouched.
Hypothetical example: agree a promotion page’s editing policy
This is an illustrative worksheet, not a real RMH project, tested handover or customer result. The guide draws on public WordPress documentation and the owner’s SLB source facts. The field names and policies are proposed examples.
| Recurring request | Proposed field | Input boundary or review | Affected content | Escalation |
|---|---|---|---|---|
| Replace a short notice | Required text | Developer sets a maximum length; editor checks meaning and wrapping | This section instance | Longer explanation needs a different treatment |
| Change a button destination | URL | Editor checks the destination matches the offer; no automatic destination restriction is assumed | This section instance | New destination policy goes to the developer |
| Replace a photograph | Image | Editor checks crop and subject visibility in preview; no crop validator is assumed | This section instance | A different image arrangement needs template work |
| Add an FAQ answer | Repeatable question and answer fields | Required text and agreed length limits; item count remains a review policy here | This FAQ placement | An oversized FAQ needs editorial review |
| Feature a different product | Product picker | Store owner checks the selected product fits the promotion | This product placement | A new presentation needs section work |
| Change a shared promotion | Text and URL in a global region | Named content owner reviews wording and destination before the agreed save process | Shared announcement | Conflicting page-specific offers need a scope decision |
SLB keeps content independent for each placed section instance. Global regions and theme settings are shared instead. That distinction makes the scope column necessary: changing a shared announcement is a different responsibility from replacing a local headline.
My suggested handover rule is to mark a request as self-service, review before use or developer work. These are labels for your agreement, not claimed SLB roles. If nobody can name who reviews a shared offer, leave that responsibility unresolved on the worksheet rather than pretending the editor has solved it.
Which limits can SLB actually enforce?
SLB supports required fields, minimum and maximum text lengths, and minimum and maximum numeric values, checked in the editor and on the server. Select fields provide declared choices, conditional fields control when a field appears, and section placement limits use max_per_page.
Use those capabilities for the boundaries they describe. A section placement limit is not a repeatable-item count limit. This source does not establish a repeat-block count validator, automatic image-crop checks or arbitrary URL restrictions.
I recommend agreeing text limits against the prepared design, then reviewing awkward copy and images in context. A short headline can still be the wrong headline. Validation checks the declared rule; it does not approve the offer.
For implementation details, take the completed worksheet to the developer alongside SLB field types and validation. Keep responsive layout, new fields and new section designs on the developer’s side of the agreement. Expose colour or spacing controls only when the task actually needs them, rather than handing over every supported control.
Could native WordPress fit the same policy?
Yes, a block-based site can use native content-only editing rather than adopting a section-schema workflow. WordPress documents content-only controls, movement and removal locks, and separate locking permissions. Do not assume the raw editor must remain unrestricted.
The Site Editor requires a block theme, so that particular workflow cannot operate while a classic theme remains active. Native blocks also use a different implementation from SLB’s PHP section schemas. Choose SLB when the desired contract is a developer-declared set of fields in reusable PHP sections; choose the implementation before promising the interface.
Free-form page builders address a different brief: giving the editor layout freedom. That freedom does not itself define which recurring changes the client should own. SLB is not a free-form, pixel-level drag-and-drop builder.
For platform differences, read editing models and shared content. For assembling pages, use the section-based page recipes. This worksheet settles the controls to expose before either exercise.
What should be checked before a live change?
My recommended check is to confirm the intended content, affected pages and person responsible for saving or publishing. A preview should be a review step, not permission inferred from a convincing picture.
- Identify the page instance or shared region being edited.
- Check wording, destination links and image fit against the agreed task.
- Review relevant page layouts, including where the new copy wraps.
- For shared content, inspect the other places that should change.
- Follow the site’s agreed save and publishing process; escalate anything outside the worksheet.
In native WordPress, Site Editor preview and save controls allow review of changes, including templates and template parts. For SLB, agree the actual site’s review process with the developer rather than assuming an undocumented approval workflow. This guide does not establish simultaneous co-editing or conflict-handling capabilities for SLB.
Which edition fits the agreed editing job?
Both SLB editions provide declared fields with live preview. Paid adds selecting sections in the preview, double-click text editing, image swaps and an on-canvas toolbar. Use the live preview and direct canvas editing explanation to decide whether direct manipulation is necessary.
Free requires the theme to call slbuild_render_page(). Paid renders automatically through the_content. Free’s bundled stylesheet covers starter sections; custom sections use the theme’s own Tailwind build. Its Single Product section does not fire third-party WooCommerce hook extensions, so extension-dependent storefront requirements need developer review.
Free has no on-canvas editing, Developer Mode, MCP or A/B testing. Free-to-paid page content does not transfer automatically yet, and paid pricing is coming soon. Compare the free and paid editing differences before entering content, then use the SLB documentation for implementation.
Frequently asked questions
What should a client be able to edit themselves?
My recommendation is to start with recurring content tasks whose scope and review owner are clear. SLB can expose declared text, image, URL and product fields; use the worksheet to decide which belong in this client’s handover.
Should a client have admin access to their own website?
Separate ownership access from the account used for routine editing. WordPress uses roles and capabilities to control permitted tasks; my recommendation is to agree ownership arrangements separately and configure the everyday editing account for its actual job.
What should a client not edit on their website?
My proposed boundary keeps PHP, responsive breakpoints and new section design with the developer. In SLB, responsive layout lives in the template, while clients use the fields the developer declares; shared settings also deserve an explicit responsibility agreement.
Is locking Gutenberg enough?
Only if the configured restrictions match the intended policy. The Block Locking API documentation distinguishes content-only editing from movement and removal locks and explains locking permissions, so a visible lock alone does not settle access.
What can a client editor change?
The answer depends on account permissions and the configured editing interface. The default WordPress Editor role can publish and manage posts, including other users’ posts; an SLB field schema describes content controls rather than replacing that account-permission model.
Take a completed change-policy worksheet to your developer, then rehearse the agreed tasks using the client visual editing walkthrough. Evaluate SLB for structured WordPress editing and its free edition listing against those tasks before building the rest of the site.
