Why we chose API-Based CMS System

Renat Zubairov know-how


In our last post we summarised what we need in our new content management system (CMS). After careful considerations and analysis we selected a new interesting CMS system. It is called prismic.io. And it’s cool not only because it’s name ends with .io (which is actually a top level domain for British Indian Ocean Territory) but also because it satisfy (almost) all of our important selection criteria.

API-Based CMS features

Feature 1 – No Pages, please

Check. prismic.io is not page but content fragment based. We are free to define the content fragment metadata/structure (called Document Masks) and then fill in the content. Content fragments are later on can be fetched via RESTfull API using special query language

Feature 2 – Collaboration and Version Control

Check. We liked a release planning features and attaching a piece of content to particular release

Feature 3 – Clean HTML

Check. Markdown editor would be even better but build-in editor is so far ok.

Feature 4 – Google SEO Friendly

Not out of the box. This feature need some work from our side – we just need to render the web-site on the server-side. We’ll update on how we integrated it into our express.js application.

Feature 5 – Availability, Scalability and Speed

Check. RESTfull API and correct release management makes proper caching and scaling a piece of cake. We don’t have concrete numbers on performance yet but there are all the necessary steps done by prismic.io to achieve a good performance and scale.

Apart from that we really liked the idea. API-based CMS gives us the full control and flexibility that we need without losing the ability to externalise content. Demo project is absolutely gorgeous and gives a great start to explore prismic.io features.

We are excited to try API-Based CMS prismic.io out. Their pricing is also quite good. We will keep posting on our experience with building a prismic.io-based web-site.

Please Note
We have changed our website CMS to WordPress. This is not to endorse or discourage others to use any specific CMS for their website. This move is completely subjective and to ensure an easy access for our editors to manage the content on our website.

About the Author

Renat Zubairov

Facebook Twitter

Renat Zubairov is CEO and co-founder of elastic.io. He is an experienced hacker, product owner and agile evangelist. Renat is a speaker on international conferences, user groups and active open source community member. During his career Renat was working with world best companies like Nokia, Nokia-Siemens Networks, TCS and DHL. Last 5 years he has been working in product start-ups in Application Integration, Data Integration and Business Process Management areas. Leading development of Application Integration (ESB, SOA) product.

You might want to check out also these posts