Headless CMS

Webnodes is designed to work as a content API in a headless situation

Headless before it was coined

With the introduction of our OData endpoints in 2011, Webnodes fully supported what has become known as headless CMS architecture. It means that you edit and manage the content in the CMS, and expose the content in a content API. Any frontend (website, app, IoT device etc) can fetch the content it needs when it needs it.

We have always been a firm believer in the concepts behind headless. Webnodes can be seen as a content API with a powerful content editing interface. We've never had any proprietary template solutions unlike many of our competitors. The reason is that we think such solutions will always lag behind the latest frontend technologies.