How jekcms approaches preview: a WYSIWYG editor that shows the result as you type, one-click theme-accurate preview of the real page, tokenized share links for drafts, and autosave backed by full revisions.
The Problem with Save-and-Preview
The traditional CMS workflow is: edit content, save, open a new tab, refresh, check the result, go back, edit more, save again, refresh again. For a 1,000-word post with a few rounds of editing, that is a dozen context switches — each one breaking focus for no good reason.
The Editor Is the Preview
jekcms attacks this with a WYSIWYG editor: headings, lists, blockquotes, and images render in the editor the way they will render on the page. Images can be resized, aligned, and captioned inline, and the result you see while typing is the result readers get. For the large majority of edits there is simply no preview round-trip anymore.
Theme-Accurate Preview
When you do want to see the post inside your real theme — typography, sidebars, related-content blocks and all — one click in the editor sidebar opens the actual page rendered by your live theme. No mock preview environment that drifts from reality; it is the same template pipeline that serves visitors.
Anonymous Preview Links
Drafts sometimes need eyes that do not have an admin account — a client, an editor, the subject of an interview. The editor generates a tokenized preview link on demand: send the URL, the recipient sees the draft, and they never touch a login screen. The link is bound to its token, not to a session.
Autosave and Full Revisions
While you work, drafts autosave in the background, so a crashed browser or a closed tab costs you seconds, not paragraphs. Independently of autosave, every content change is snapshotted as a revision with its source recorded — manual edit, API, queue, or n8n — and any revision can be restored, including a full-snapshot restore that brings back the complete state of the post.
