Headless CMS

Content belongs to you. Not to your website template.

The price list is on the website. And in the app. And on the screen in the branch. And in the newsletter. And in the PDF field sales send out.

When a price changes, a small expedition through five systems begins. Usually one of them is forgotten.

A headless CMS turns that relationship around. The content lives in one place, independent of how it is displayed. Every channel fetches it from there. Change it once, and it changes everywhere.

You decide what your content looks like

In Caymland M4 you create your content types yourself. No development request, no database change, no waiting.

A content type is a description: an "event" has a title, a date, a place, an image, a description and a link to a speaker. You define that in the interface, and from the next click editors can enter events.

Available field types include:

For formatted text you choose per field what to work with: plain text, Markdown or a comfortable editor. Your editorial team gets the tool that suits them, not the one the system dictates.

Multilingual without the pain

Languages are enabled per content type. A document then exists in several language versions that belong together and are nevertheless edited and approved individually.

That matters more than it sounds: the German version can go live while the French one is still being proofread. A language switcher shows your editors at once which languages already exist and which are missing.

Draft and approval

Every piece of content has a draft state and a published state. Only what is approved is served outwards.

So your editors can work on the next version in peace while the current one is live. And because approval happens per language, an unfinished translation blocks nothing.

A media library that tidies up

Images and files sit in a central library instead of scattered across folders.

• Replace instead of re-upload: swap an image and it changes everywhere it is used.
• Usage evidence: before deleting, you see everywhere a file is embedded. No more broken pages.
• Rename and organise, without references breaking.

Deliver wherever you want

Approved content is available through an open interface. Your website fetches it, your app fetches it, the screen in the branch fetches it, the partner portal fetches it.

• Public or protected, decided per content type. Public content is freely retrievable, protected content only with an access token.
• Filter, sort, page right at retrieval, so the other end does not have to load everything.
• Caching for fast delivery even under heavy traffic.
• Outbound notifications when a piece of content changes, so connected systems can react at once.

Your website can be built in any technology. The CMS is not interested in which.

The advantage only we have

An ordinary headless CMS knows content. Ours sits in the middle of your CRM.

Concretely that means: a content field can refer directly to a contact field. Your categories are the same ones marketing uses. And delivered content can be tied to what you know about the person looking at it.

That turns "managing content" into something else: content that fits the person currently reading it.

What this looks like day to day

The tourism board. Events, businesses and offers are maintained once and appear on the main website, the partner sites, in the app and in the weekly newsletter. In four languages.

Retail. Product descriptions and promotions come from one source into the online shop, the in-store screen and the printed insert.

The association. The editorial team works on the next edition as a draft, approves it on the appointed day, and every channel follows. No deploy, no appointment with IT.