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. 

Benefits of using a headless CMS

There are many advantages of using a headless CMS for your next CMS project. The main advantages are:

  • It makes it possible to create better user experiences as you can take full advantage of the rapid innovation in the frontend market in the last few years. Since all the display logic is running in the browser, you're only transfering the content the frontend needs when it needs it.

  • It makes it easy to support any platform or device. 

  • Respond to new trends, markets and devices a lot faster

Webnodes advantages over other headless solutions

If we have convinced you of the benefits of a headless CMS, you still have to select the correct headless CMS solution. We think Webnodes offer a compelling package. Contact us if you need more information.

Battle-tested

Webnodes is a fully featured enterprise quality CMS used in thousands of web projects. This has created a very powerful API and featureset that the new "headless-only" solutions can't match.

Editing experience

Also, the editing experience on many of the "headless-only" solutions is often very basic. With Webnodes you get both a very powerful API and user interface combined with multiple headless API options. 

Superior content model and not page centric design.

When you're using a headless CMS, how you structure your content become even more important than before, because you're only providing the content through an API, without knowing how it's going to be used. Is it an app, a web app, a TV information system or an IoT device that is using the content? You don't know. This means that structuring the content in the format that makes sense for the developers using your headless API is crucial. If you simplyfy the natural content structure to a page centric model, you loose a lot of opportunities. Webnodes supports proper two-way relations between content, giving you a graph content model, and allows you to model the content how you would naturally structure it.

OData

There are several important benefits of using  an OData headless API over custom Rest APIs. The most important is that OData is an Oasis standard, Having a standardised API is a huge benefit: There is a huge number of tutorials for developers to learn from, and OData is supported in most programming languages. Additionally, many 3rd party software solutions supports importing content from OData APIs. For example a lot of BI solitions like Qlik, Tableau, PowerBI and others have built-in OData support.

Flexibility

One of our most important design goals is to provide flexibility on how you use our solution. We support non-headless, headless through a standardized API and headless through custom Rest API. We support both cloud or on-premise installations. We support