Content Studio / Publishing & Moving Sites

Application Code vs Runtime Data

Distinguish published application files from persistent Content Studio runtime data.

Application: cyclops-cms

cyclops-cms contains the protected Content Studio application supplied by the installed package: administration code, shared PHP, JavaScript and CSS, public readers, initialization logic, packaged Starter Content, and support assets. A newer Content Studio release may replace these application files.

Runtime: cyclops-cms-data

cyclops-cms-data is the site-specific authoritative store. It contains Posts, Events, uploaded media, settings, templates, Smart Image assignments, credentials, initialization state, and other runtime configuration created for that published site.

The Ownership Boundary

Application code is replaceable and should not be used as the client’s editable content store. Runtime data belongs to the site and must survive package updates, re-registration, republishing, and moves. Do not casually replace it with an older copy.

Starter Content Is Seed Data

Packaged Starter Content lives with the application as a source package. When selected during first initialization, missing sample records and media are copied into runtime once. From then on, the runtime copies are ordinary editable content and remain authoritative; publishing does not reseed deleted items.

Practical Rule

When updating the application, preserve cyclops-cms-data. When backing up or moving client content, include the entire current cyclops-cms-data folder as one matching set.