EMDASH AND ZEPHYR

One Immutable Version The Code and Content ship together

EmDash holds the content. Zephyr creates immutable releases of that content and the code used at that time.

One build holds the words and the site. one production tag → → EMDASH The words The page stays in EmDash A save can start a capture The save is still a draft draft ZEPHYR The site build 1289 content, renderer, and shell its own URL, stays deployed deployed THE TAG Production points at build 1289 words and site together rollback moves this tag the release Illustrative. Each build keeps its URL. A person moves the tag. Recovery still depends on detection.

The content and the site. One tag.

content and site, one build

  • this version
  • production tag

One version moves. The words come with it.

14:02 → build 1290This version is the public site.Content and code together
14:06 → build 1289Production returns to the last good version.Words and site together
Illustrative. Recovery still depends on how fast you see the problem.
One buildcontains the content and the site.
One URLto review before anyone releases.
One tagrolls both back.

THE SPLIT

A CMS and a pipeline are two releases.

Content here. Code there.

  1. The CMS writes the live site.
  2. The pipeline ships a different artifact.
  3. Content rollback and code rollback are two jobs.
  4. Brand, legal, and platform look at different versions.
two systems, two versionsReconcile the two

EmDash on Zephyr

  1. A save can become a sealed site build.
  2. That build has its own URL.
  3. A person releases one version.
  4. Rollback returns the words and the site together.
one build, one tagMove one tag
Three teams. One production tag. one URL CONTENT Editors change EmDash They review a URL EmDash save PLATFORM Platform releases Zephyr A role moves the tag one URL per build ENTERPRISE The company shares it Brand, legal, engineering one production tag PRODUCTION build 1289 the words and the site Illustrative. Rollback returns this version. Recovery still depends on detection.

ONE ENTERPRISE SITE

Three teams. One production tag.

CONTENT

Editors change EmDash

The content stays in the CMS. The team reviews a URL for that version.

EmDash save

PLATFORM

Platform releases Zephyr

Every build stays deployed. A role decides which version is public.

one URL per build

ENTERPRISE

The company shares the version

Brand, legal, and engineering open the same URL. Rollback returns that version.

one production tag

HOW THEY MEET

Edit in EmDash. Release on Zephyr.

  1. 01Save the content
    EmDash  save the page
    content stays in the CMS
    the save can start a capture

    EmDash commits the page. The save can start a capture. The save is still a draft.

  2. 02Deploy the build
    Zephyr  sealed site build
    content + renderer + shell
    → build-1289.zephyrcloud.app

    Zephyr seals the content, the renderer, and the shell. That build keeps its URL.

  3. 03Roll back to a working page
    production  build 1289
    words and site together
    rollback  returns both

    Move the production tag back to a working release. It already contains the code and content from that version, even if the CMS has changed or the original code is gone.

BETTER TOGETHER

Each product does one half of the release.

  • emdash

    the content

    The CMS keeps the draft

    Editors and agents change pages in EmDash. A save is the content. It is not yet the public site.

  • zephyr

    the version

    The build gets its own URL

    This site captures that save into one sealed site. Zephyr deploys the build. Official plugins are coming soon.

  • one tag

    the release

    Production is one pointer

    A person points production at that build. Rollback selects an older retained version. The words and the site move together.

  • EMDASH · 1.5

    Start from the content you have

    A WordPress export can become files on your machine. That is the way in. The release is still one Zephyr version.

  • ZEPHYR CLOUD · HOW THEY MEET

    One version. The words and the site.

    The capture, the sealed build, and the tag. What the pair does today, and what is still best-effort.

BOOK A DEMO

Bring both teams. Leave with one version.

30 minutes with an engineer. Content and platform look at the same URL.

  • A content save that becomes a build URL
  • One production tag for the site
  • A rollback that returns both

Loading the form…

Rather pick a time yourself? Book a call →

Email Zephyr Cloud