heyweb or a headless CMS?
A headless CMS stores structured content and serves it to any front end. heyweb edits the content of one finished website, where it stands.
In shortA headless CMS such as Contentful, Sanity or Strapi stores content as structured entries and delivers it through an API to a front end you build and host separately. heyweb hosts the finished website itself and lets the client change the content directly in its pages.
Side by side
Both keep the client away from the code. They differ in how much has to be built first.
| Headless CMS | heyweb | |
|---|---|---|
| Before a client can edit | Model content types, connect the site to the API, set up builds | Upload the site |
| Where content lives | In the CMS, as structured entries | In the pages, as versions |
| Hosting | Separate, with a build step | Included |
| What the client uses | An admin panel with fields | A chat |
| One content source for web, app and more | Yes, that is the point | No |
| Roles, drafts, translations, workflows | Usually available | Not available |
Which one fits
A headless CMS fits when
- The same content feeds a website, an app or other channels
- An editorial team needs roles, drafts and approvals
- Content is large and strongly structured
- Developers maintain the front end over time
heyweb fits when
- There is one website and it is a few to a few dozen pages
- No developer will look after it after launch
- The client changes words and pictures now and then
- You do not want to model content for a small site
Why not both
For a small business website, a headless CMS means building an editing system that is larger than the site. heyweb skips the model and edits what is on the page, as described in a CMS for static sites.
When a project grows into several channels or a real editorial team, a headless CMS is the right tool, and your static site can read from it like any other front end.