Draft or live: how an article lands in each CMS

Publishing now saves the article in WordPress as a draft. Munshi says “Saved in WordPress as a draft. Review and publish it from your WordPress dashboard.” The article's status in Munshi reads Landed as a draft in WordPress.

Scheduling sends the article to WordPress with its date and time, and WordPress puts it live at that slot by itself. The body arrives as WordPress blocks, so you can edit it as normal. Its images are copied into your media library.

These three always hold the article as a draft, whether you publish now or schedule. Scheduling decides when Munshi sends the draft, not when it goes live. At the slot, the article is sent again, still as a draft. It goes live when you publish it in the platform.

• Ghost: “Saved in Ghost as a draft. Review and publish it from your Ghost dashboard.”
• Webflow: “Saved in Webflow as a draft item. Publish it from your Webflow CMS.” The article goes into the collection's rich text field.
• Framer: the article is saved as a draft item in your Framer CMS collection. You review and publish it from Framer.

Publishing now writes the live document. Munshi says: “Published to Sanity.”

Scheduling saves a draft document instead, so Studio shows it coming. Munshi says: “Staged in Sanity as a draft until the scheduled slot.” At the slot, Munshi publishes it and clears the staged draft.

The document is of type post, with a title, body, slug and excerpt.

The cover you chose for the article goes with it to four platforms. If you chose no cover, Munshi uses the first image in the article.

• WordPress: the featured image, uploaded to your media library.
• Ghost: the feature image, uploaded to Ghost.
• Sanity: the main image, uploaded to your assets.
• Webflow: written into every Image field in the collection, with its alt text.
• Framer: not written. Add the image in Framer when you publish.