How to review, approve and send a CMS draft

Read preflight, approve a version, create the CMS draft.

About 2 minutes per draft · Illustrative UI

Animated walkthrough: Review, approve, send a CMS draft

BlogFactory · example product “Plantwise”Illustrative UI

Review Queue

  • How often to water houseplantsVersion 3 · In review
Open

Opened version 3 with its change summary.

Step 1 of 5

Open the draft in the Review Queue

Open the version waiting in the Review Queue. Each row names the version, so you always approve something specific.

Review Queue · Preflight

Run preflight
  • Revision is currentOK
  • SEO checksOK
  • Destination connectedOK
  • Cover imageWarning

Step 2 of 5

Read the preflight

The preflight checks the revision, SEO state and destination. Failures in those three block delivery. Warnings such as a missing cover image are shown and do not block.

Review Queue · Approval

Version 3 · updated just now

Approve this version

Approved: version 3.

Step 3 of 5

Approve this exact version

Approve version 3. If anyone edits the draft afterwards, the version changes and the approval no longer matches it.

Review Queue · Delivery

ToGhost · Plantwise blog
Create CMS draft

Draft created in Ghost. The edit link comes back with the result.

Step 4 of 5

Choose a destination and create the CMS draft

Pick the connected destination and create the CMS draft. Repeating the same version and destination reuses the existing draft instead of creating a second one.

Your CMS · Drafts

  • How often to water houseplantsDraft
Open in your CMS

BlogFactory has no live-publish action.

Step 5 of 5

Publishing stays with you

The post waits in your CMS as a draft. BlogFactory stops here. Whether and when it goes live is decided in the CMS, by a person.

Illustrative UI: a composite of the real screens with an invented example product. It is not a recording, and no real account or data is shown.

What you need

  • ConnectionA connected CMSDelivery of an approved draft to WordPress, Ghost, Wix or Framer
More: who sets each one, and what stops without it
You needWho sets itWithout it
A connected CMSYou, in Control → IntegrationsNothing is sent. The draft stays in BlogFactory and the review steps still work.

Drafts only. BlogFactory only creates CMS drafts. It never publishes live on its own.

What it will not do

Boundary · BlogFactory only creates CMS drafts. It never publishes live on its own.
  • Publish live, schedule a live post or delete content.
  • Force a write over a newer version. A conflict writes nothing; you reread and retry.
  • Send a draft to a destination you have not connected and tested.

Try the steps on your own site.

Every step above is in both editions. You approve each draft, and nothing publishes itself.