Going live, backups, updates

Before publishing, back up. After publishing, check. If something is wrong, roll back.

Quality checklist before launch

Every page reviewed on Mobile, Tablet and Desktop in the editor.
Header and footer links work, and Theme Settings colours and fonts are set.
No placeholder text ("lorem ipsum") left anywhere.
Every image has a sensible size and is described.
Forms, cart and checkout tested with a real test order (shops).
If using Claude: the audit shows zero blockers and you reviewed the preview link on a phone.
Developer Mode switched off again (or locked off in wp-config.php).
A fresh backup exists.

Backups

SLB does not make backups. Use your host's backup tool or a backup plugin and take one:

Before installing or updating SLB.
Before activating a different theme.
Before publishing a draft theme.

A backup must include both the database (your page content and settings) and the files (themes, plugins, uploads).

Warning. Deleting the SLB plugin removes its settings, global regions and custom CSS. Back up first.

Publishing

Page edits in the editor: Publish Changes.
A draft theme built with Claude: SLB Editor > Developer Mode > Preview / Publish > Publish Draft Theme. Give the release a name you will recognise, such as "June relaunch".

Rollback

If a published theme has a problem:

Open SLB Editor > Developer Mode.
Click Rollback to Previous Theme.
Check the live site.

Rollback switches the site back to the theme that was live before. It restores theme files, not content changes you made to pages afterwards. For page edits use Discard before publishing, or a backup after.

Updating SLB

Take a backup.
Obtain the new zip. It has a new version number in its name (for example slb-full-0.3.11.zip).
In Plugins > Add New Plugin > Upload Plugin upload the zip. WordPress offers to replace the current version. Confirm.
Open SLB Editor and check one page. Then run the audit if you use Claude.

Never overwrite files by hand. Do not copy files over the plugin through FTP. Always use a zip with a new version number so WordPress and SLB know what changed. The updated plugin folder may include a newer mcp folder; copy it to your computer and run npm install again.

Starter sections in your theme are not overwritten by a plugin update, so nothing you customised in your theme is lost.