A practical Ghost CMS API editorial workflow
Choose a content representation, test conversion, and preserve the editor’s changes from import to release.
Read the storyBring drafts into your CMS without losing editorial control.
Compare two destination-specific approaches rather than assuming every publishing API accepts the same content. The WordPress article concentrates on fields, media, taxonomy, and retries. The Ghost article concentrates on conversion and the handoff to the editor. Both use draft-first workflows and preserve a clear boundary between imported text and a public release.
Read the articles below, explore the guide library for focused topic introductions, or return to all Write API Lab articles to follow another thread.
Choose a content representation, test conversion, and preserve the editor’s changes from import to release.
Read the storyMap content, media, and taxonomy while protecting the human approval step in your WordPress integration.
Read the story