Content Studio / Publishing & Moving Sites

Publishing Normally

Publish routine site updates while preserving Content Studio runtime data.

Before You Publish

Confirm that you are working in the intended Elements project and publishing destination. Make your design, page, and component-setting changes in Elements. Content created by the client remains on the published site rather than in the Elements project.

Publish the Site

Use the normal Elements publishing command for the configured destination. Content Studio may replace or update application files in cyclops-cms. Its separate cyclops-cms-data folder remains the authoritative site-specific runtime store.

What Normal Publishing Preserves

Normal publishing may update or replace Content Studio application files in cyclops-cms while preserving the existing site-specific runtime content in cyclops-cms-data. This runtime data includes Posts, Events, settings, administrator credentials, uploaded media, and Smart Image assignments. During an ordinary publish, do not manually delete or replace cyclops-cms-data.

Verify After Publishing

1. Open the published primary Admin page and sign in so its publisher configuration can activate. 2. Check public Posts and Events. 3. Confirm every expected Smart Image destination card and its existing assignment, plus any configured header and Developer logos. 4. If data or cards are missing, preserve the runtime and existing keys while the developer investigates; Ready alone does not establish destination completeness.