Content Studio / Publishing & Moving Sites

Protecting Client Content

Preserve client-managed content during publishing, maintenance, and site moves.

Treat Runtime Data as Production Data

Client-managed Posts, Events, settings, credentials, media, and Smart Image assignments live in cyclops-cms-data. That folder is the authoritative record of the published site, not a rebuildable copy of the application.

Use Safe Maintenance Practices

Back up the current runtime before upgrades, moves, hosting changes, or manual server-file work. Never delete cyclops-cms-data casually, and never copy an older runtime over a newer client site.

Keep Testing Separate

Use a separate disposable site or copy for destructive tests. Do not test resets, migrations, cleanup, or manual file replacement on the client’s only live runtime. Content Studio has no supported merge process for combining changes from two runtime folders.

Respect Starter Content History

Starter Content seeds only during virgin initialization when explicitly selected. Deleted sample records stay deleted; re-registration and republishing must not restore them.

Verify After Publishing

After maintenance, check public content, sign in, verify Smart Images and media, and run System Health. If storage or configuration is uncertain, preserve the existing runtime and investigate before changing files.