Publishing safely

The person says: “Looks good, put it live.”

Promoting replaces what visitors are served. It is the one step that asks for the person’s yes, and it is the step most often declared done before it was.

The loop

1. Empress:site_status — what is staged, whether live moved since, and whether a change set rides on the stage.
2. Empress:site_preview — the stage (target: "stage") or the drafts (target: "draft") at three widths, if it was not rendered since the last change.
3. Empress:changeset_promote — when a change set is open; otherwise Empress:theme_promote. Ask the person first; then confirm: true. A client that supports it shows the person an approve or decline question instead.
4. Empress:site_preview — target: "live".
5. Empress:site_status — the new entry in the versions section, and whether it can be undone.

Judgment

• An Admin’s yes. If the person’s role cannot promote, the answer says the request waits in the console for an Admin, and names the page. Tell the person; do not retry.
• Group sites. Publishing to a group of sites is a person’s call from the console; the answer says so.
• Live moved since the stage. Stage again rather than forcing; force is for when the person has seen the difference.
• The cache. A page still showing the old version right after a promote is the edge cache for a few minutes, not a failed promote.