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.
The content and the site. One tag.
content and site, one build
- this version
- production tag
One version moves. The words come with it.
THE SPLIT
A CMS and a pipeline are two releases.
Content here. Code there.
- The CMS writes the live site.
- The pipeline ships a different artifact.
- Content rollback and code rollback are two jobs.
- Brand, legal, and platform look at different versions.
two systems, two versionsReconcile the twoEmDash on Zephyr
- A save can become a sealed site build.
- That build has its own URL.
- A person releases one version.
- Rollback returns the words and the site together.
one build, one tagMove one tagONE ENTERPRISE SITE
Three teams. One production tag.
HOW THEY MEET
Edit in EmDash. Release on Zephyr.
- 01Save the content
EmDash save the page content stays in the CMS the save can start a captureEmDash commits the page. The save can start a capture. The save is still a draft.
- 02Deploy the build
Zephyr sealed site build content + renderer + shell → build-1289.zephyrcloud.appZephyr seals the content, the renderer, and the shell. That build keeps its URL.
- 03Roll back to a working page
production build 1289 words and site together rollback returns bothMove 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 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 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
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