SG-Builder publish loop — visual edits, predictable shipping

May 12, 2026. SG-Builder ships a tightened publish loop. Builder templates are now native. Staging-aware preview shows you what visitors will see before you click Publish. Per-page rollback gives you a one-click undo.

What changed

Before: edit a page in SG-Builder, save, publish, hope it looks right on the public site. If something rendered wrong, you fixed it in another save-publish cycle. Builder templates lived in a separate tool that synced unreliably with the live editor.

After: templates are part of SG-Builder itself. Edits save against a per-page revision history. The preview pane shows the staging-state render with the same code path the public site uses. Publish lifts the staging version into live. If the live result is wrong, one click rolls that page back without touching the rest of the site.

What's in this release

Templates native to SG-Builder

Page templates (header, footer, sidebar, archive layouts) now live inside the SG-Builder editor:

• Edit a template the same way you edit a page — drag, drop, configure, save.
• Templates apply per page — set a different header for landing pages versus product pages.
• Template revisions — every template save is versioned. Roll back if a template change breaks pages that use it.
• Template testing — preview a template change against a sample page before applying it site-wide.

The earlier "Builder Templates" external tool is sunsetted. Existing templates migrated automatically on May 12.

Tightened publish loop

Editing a page now follows a clear save → preview → publish flow:

1. Save writes to the page's staging revision. The live site is untouched.
2. Preview opens the staging render in a new tab. Same renderer the public site uses — what you see is what visitors will see.
3. Publish lifts the staging revision to live. Public visitors see the new version on next page load.

You can save many times before publishing. Each save is a revision. The publish button only fires the latest staging version live.

Per-page rollback

Every page has a revision history:

• Open the page in SG-Builder
• Click the Revisions dropdown
• Pick a prior revision to view it
• Click Restore to bring that revision back as the current staging draft
• Click Publish to push it live

Page-level rollback is independent of site-level backups (the April 29 Highlight). Site backups restore everything to a moment. Page rollback restores one page to a prior revision. Use the right tool for the right blast radius.

Layer manager updates

The Layer Manager (the structural tree of every block on the page) now supports:

• Multi-select — pick several blocks, move or delete them together
• Search — type a block class or component name to jump to it in the tree
• Bulk operations — copy a section, paste into another page, copy again
• Lock controls — mark a block "locked" so accidental clicks don't move it

For complex pages with 50+ blocks, the Layer Manager improvements measurably reduce edit time.

Exit and return flow

If you close SG-Builder mid-edit, your work is preserved as a draft. Returning to the page reopens the editor at the exact state — same selection, same scroll position, same panel layout. No "are you sure you want to leave" modal. No lost work.

Why this matters

The visual editor is where most SGEN customers spend most of their admin time. Every friction point in the publish loop multiplies across daily editing sessions. The May 12 release attacks the friction directly — fewer save-publish surprise loops, fewer "I broke something, what now" moments, fewer manual workarounds for missing template behavior.

For agencies and operators editing many sites, the time savings compound. A 2-second-per-save improvement across 200 saves per week is 7 minutes saved weekly per editor.

Common patterns

• Daily content editor workflow. Open page → edit blocks → Save (often) → Preview when sections look done → Publish when satisfied. The preview-before-publish step catches most surprises before they hit visitors.
• Template change rollout. Update a template, preview against three representative pages, then apply site-wide. If the preview shows a problem on one page type, fix the template before publishing.
• Mistake recovery. Editor accidentally deletes a section. Open Revisions, pick the version from before the delete, click Restore. Five seconds, no support ticket.
• Multi-editor collaboration. Two editors take turns on a page. Each save is a separate revision, attributed to the editor who made it. The revision history shows who changed what and when.

What's not in this release

• Real-time co-editing. Two editors can both have the page open but can't both edit at once (the second editor gets a read-only view + a "draft owned by Alice" indicator). True real-time collaboration is in LATER.
• Component-level revisions. Today revisions are per-page. "Roll back this section" is not yet supported.
• Visual diff between revisions. The Revisions list shows timestamps and authors. A visual side-by-side diff is in NEXT.

Behind the work

The April 6 changelog entry (provisioning automation + builder updates + platform safety) is the foundation. The April 10 entry (deployment safety + environment consistency) is what makes the staging-aware preview reliable — without consistent environments, "preview matches live" wouldn't be true.

Next steps

• Read the Reference at Reference → SG-Builder for the full editor reference.
• Try the Revisions panel on any page in SG-Builder — useful even if you don't think you'll need it. Knowing it exists changes how you edit.
• Migrate any custom template workflows to native SG-Builder templates. The legacy Builder Templates tool is being phased out at end of Q3.