Contentful is a content hub, pioneering the concept of headless content management. It's a powerful 100% SaaS solution for pure content management that I have recently become fairly familiar with.
While my experience comes out of the Episerver Web Content Management world, I'm increasingly fascinated by the simplicity of separating pure content management in a service such as Contentful for un-intrusive content use in multiple channels, while still keeping for example advanced web experience delivery in a system like Episerver.
Getting started with Contentful UI Extensions - part 2
In this post, I'll show how to make a field editor that will let you have any kind of syntax highlighted code in a long text field, as well as taking a look at command line interface (CLI) and Github distribution.
Getting started with Contentful UI Extensions - Part 1
Contentful has a handful of extension points, where you in a fairly straightforward and simple manner can extend the editorial experience with minimal development effort. In this post-series I'll show some examples of this.
The Curious Case of Content Modelling
Having the right content model (the structure of your content types) is very important in order to end up with good, usable (and reusable) content. I believe that is something that most content management aficionados can agree on. But what is a good content model? And who should be modelling your content? In this blog post I will try to discuss a few opinions on this topic.
Distributed Content: Delivering an Episerver Web Experience with Contentful Content
The move in the market towards headless could also be seen as a tendency towards a deeper decoupling between content and experience delivery. Inspired by a few discussions, I've tried my hands on an uncommon combination: Contentful providing content delivered through an Episerver web experience layer.