Understanding Pokko from a traditional CMS perspective

Pokko at its core is a CMS - a content management system. It is a system for managing content.

Content management

But what is content management?

Content is what sits behind most digital platforms. This blog post is made up of "content" - this text you are reading is the body of the blog post, there's a title up the top.

Someone had to define those features - a title, a place for body copy - somewhere.

In CMSes that's generally referred to as your "content model" - it defines what attributes your content has.

This site has many blog posts. Generally, CMSes have the ability to easily manage endless amounts of content such as blog posts.

Content management is the double-sided process of defining your content model as well as allowing for the creation of content based on those models.

Most platforms go further and offer things like media management, content governance, publishing workflows and so much more.

Traditional CMS comparison

"Traditional CMS" is a term given to the more heavyweight platforms that have been in use for a long time - Drupal, Umbraco, Sitecore, Kentico - to name a few.

Where platforms like Pokko (generally referred to as "Headless CMS") differ from these traditional platforms lies within a separation of concerns.

Pokko cares about the structure of your content, the security of your content and the workflow around publishing your content.

It does not care about where your content is used. Whether the content you're entering in Pokko is used on a website, a mobile app, a voice skills - Pokko doesn't care.

Traditional CMSes, on the other hand, care about the structure of your content as well as its presentation.

They tend to be quite heavily tied to web implementations, which means that your content can only serve one purpose.