We offer two options for storing content:

The Default Git-Based CMS

The first one, which is the default is on our plans, is using the same Git repository of your project to store the content. This is also known as a Git-based CMS.

At first glance, this might look like no CMS at all. However, consider that:

  1. Git is essentially a fully versioned data repository. Coupled with common managed solutions (such as GitHub, but not limited to it) you get first-class availability, security and governance.
  2. Git supports flexible branching strategies that could be as simple or powerful as desired. Developers can use their own branches, while content creators could all work on a single preview branch or have separate environments for longer-term projects (the latter is coming soon to our product).
  3. Less moving parts. This makes it a good choice to start with, and often to grow with.

Connecting to a Headless CMS

In our premium plans we fully support connecting to Contentful as an external API-based CMS. This support includes:

  1. Automatic inference of the content model from Contentful - no need to declare it twice.
  2. Fetching data & assets from CMS and caching it for a smooth workflow.
  3. Bi-directional content sync: any editing made in our UI immediately appears in Contentful, and vice versa - edit anything in Contentful and you'd see it in our visual editor in a few seconds.
  4. Publishing integration. When you publish in through our visual editor, it will publish the selected documents in Contentful.

With this option you get all the workflow and management capabilities of the CMS, and all content is available through the CMS API for cross-platform use. In our experience, this is a good option for larger organizations.

Where is the CMS Configured?

For both CMS options, our themes provide an appropriate project configuration and utilize Sourcebit to abstract away most details of how to read content from its source and transform it into URLs.

For a deep dive on themes, see How Themes Work.

If you're interested in using an external CMS, talk to us!.

Next up: What a Website Needs