CMS & Publishing

Open source CMS and publishing tools fall into three groups: headless CMS platforms for structured content, dedicated publishing platforms for blogs and newsletters, and wiki or documentation tools for internal and public knowledge bases. Strapi, Payload, and Directus are headless CMS options: content is modeled through an admin panel (collections, fields, relations) and delivered to any frontend through a REST or GraphQL API, decoupling the content editor from the website's framework. Directus differs by wrapping an existing SQL database rather than owning the schema, which suits teams that already have a database and want a CMS layer added on top without a migration. Payload is TypeScript-first and runs as a Node application with a code-first schema, appealing to teams that want the content model defined and version-controlled alongside application code rather than only through an admin UI.

Ghost is a purpose-built blogging and newsletter platform rather than a general headless CMS. It ships with its own themes, a built-in subscriber and membership system, and email newsletter delivery, aimed at publishers and writers who want a finished product instead of a set of building blocks. Wiki.js and Docmost cover internal knowledge bases and documentation. Wiki.js is a traditional wiki with page history, access control, and multiple markup formats (Markdown, HTML, AsciiDoc). Docmost is closer to a Notion or Confluence alternative, with real-time collaborative editing, nested pages, and comments, aimed at teams documenting internal processes together rather than publishing to the public.

What to look for depends on the use case. For a marketing site or app that needs content editable by non-developers but rendered by a custom frontend, a headless CMS (Strapi, Payload, Directus) is the right fit, and the deciding factor is usually whether the team wants a code-first schema (Payload) or an existing database wrapped in an API (Directus). For a blog or newsletter, Ghost includes subscriber and membership management that a headless CMS would require building from scratch. For internal documentation, the choice comes down to whether real-time multiplayer editing (Docmost) matters more than mature access control and page versioning (Wiki.js). All of these can be self-hosted with Docker and a Postgres or MySQL database, which keeps content and subscriber data under the team's own control.