Ghost is the writing tool, not the website

Technology

Ghost has one of the better writing experiences in publishing software. It also has the content model of a publication: posts, tags, authors. A marketing site is not that, and no amount of configuration turns one into the other.

So on CrewAI we let it be the first thing and not the second. Editorial writes in Ghost, and every published post lands as a draft in Contentful, where marketing owns metadata, page composition, and schedule.

Monogram logo

The pipeline

How Ghost sits next to a headless CMS

  1. Its content model is a publication

    Posts, tags, authors, and one template per post. A marketing site is assembled from reusable sections with their own metadata and composition rules, and Ghost has no opinion about any of that. CrewAI's site is composed that way, so Ghost was never going to render it.

  2. Nothing on the site renders from Ghost

    By the time a reader asks for a page, the article is already sitting in Contentful. Ghost is a source we read on publish, not a dependency in the request path, so its uptime and its theme layer are not part of the site's availability story.

  3. Published in Ghost is not live

    That is the cost, and it is worth naming before rollout rather than after. A writer hits publish and no reader sees anything; the piece has been handed to marketing instead. We took the trade deliberately, but every person writing has to know it is the trade.

Project

Where Ghost feeds the site

Writing

On content models and migrations