Cloning a site

The person says: “Clone the downtown site so we can try the new layout without touching it.”

A clone is a new site in this workspace (it counts toward the plan’s sites): the source’s content, media, menus and settings are copied into it from what is live, never drafts. It runs in the background.

The loop

1. Empress:whoami — the source site’s slug, and the plan’s room for another site.
2. Empress:site_status — the source: drafts and an open change set are not copied; say so.
3. Empress:site_call — tool: "empress.site_clone", optional args: { title, slug } for the copy; confirm: true once the person agreed. The answer starts a run.
4. Empress:work_status — the copy’s task, until it is done; it names the new site.
5. Empress:site_status — the new site, once it is active.
6. Empress:changeset_create — on the new site, for what makes it different.
7. Empress:site_call — tool: "content_update" for those differences (args: the item’s collection and id, the changed fields in data), with changeset; preview and promote as in staging-a-change.

Judgment

• A clone starts identical. Change the name, address and contact details before anything on it is shared.
• A staging sibling is not a second venue. For a new location with its own theme choices, see creating-a-site.