DEV Community

Cover image for Why You as a Developer Should be Using a CMS
Joel Varty for Agility CMS

Posted on • Updated on • Originally published at

Why You as a Developer Should be Using a CMS

By: Gabriella Pirrone

Gabriella Pirrone

A content management system (CMS) can take away the overall stress of managing your website. It can also give developers the flexibility to build and focus on creating solutions to complex problems so they can spend more of their time coding. But, why else would a developer want to use a CMS?

I reached out to James Vidler, the VP of Product and Operations here at Agility CMS. James’ extensive background in software development led me to our conversation about the overall importance of a CMS for developers, its benefits, the knowledge needed to implement a CMS, and its most common languages and frameworks. Read the interview below.

Why is a Content Management System Important?

By choosing a CMS, companies can easily build websites for themselves and their customers. These systems can streamline web design and content publishing, ensuring that both your site and workflow are in sync. For my first question, I asked James what the overall importance of a CMS was for a developer from his perspective. 

“A properly implemented content management system allows non-technical editors to modify and create content without requiring a developer’s assistance. Let’s imagine you’ve built a website for a customer without a CMS. You’ve spent countless, painstaking hours obsessing over the design and content of the site with your customer. Then, you launch the website.  

In today’s web, content is often fluid and in a constant state of flux. The amount of content on websites is also growing exponentially. Before you know it, your customer starts to request new pages and alterations to existing ones. How do you handle these? Without a CMS, this responsibility falls on you.  

You might find yourself going on and on in email chains with your customers just to get some basic content updated. This is a huge time-suck, not only for you but for your customers as well. Wouldn’t you prefer to move on to building new websites, and continue to learn and grow your development skills rather than fiddle with HTML updates all day?” 

Top Benefits of a Content Management System for Developers

There is a strong notion that a CMS only benefits the editor. As you're reading this article, I believe that you’d agree that it also benefits the developer as well. I asked James to share his opinion on this often-discussed topic.

“Many believe that a CMS only benefits editors, but I strongly disagree. I think a CMS is an invaluable tool for a developer. You’ll be more productive, write better code, and have happier customers. Once you have a site with a CMS, it can be managed without your involvement, this frees you up to work on the next big thing. Ideally, when you are building a site using a CMS, you are effectively creating Lego pieces that editors then use to piece together their pages. This also forces developers to think about how to support different use cases and placements of functionality and content. So, you’ll spend more time developing your skills and building efficient, re-usable code.   

A successful implementation will delight your customers. The next time they ask you to update content, you’ll be able to show them how they can manage this on their own and how this in-turn empowers the editor to be able to do more. They’ll love that they have control, and love they’ll love you for enabling this.” 

Let your Developers Build How they Want & When they Want  


The popularity of aheadless CMS is rising and many are moving away from a traditional CMS. Let's face it, it's time to say goodbye to planning around outdated capabilities. Waiting on IT just to make simple content updates, risking serious security breaches, and shying away from multichannel optimization. In my next question, James touches on why CMSs have been a polarizing topic in the developer community.

“Not everyone has had great experiences with CMSs. There are various reasons for this, one is that traditional CMSs dictate how you build your website and place constraints and limitations around the tools and technology you use to build it. Developers like to be in control of their tech stack and try new things. Being told what to do and how to do it doesn’t leave a lot of room for creativity. Another problem with traditional CMSs is that they get old, need to be maintained, upgraded, managed and they don’t tend to scale well. Frankly put, they can be a headache that gets in the way. Luckily, we are heading into a new era of CMSs, the era of the “headless CMS”.  

A headless CMS is just like a regular CMS, except it does not place any assumptions on how the content will be used in the presentation layer. This means that developers are free to build their website or app exactly how they want, using whatever tech stack they wish. Content is consumed via an Open API and can easily be accessed regardless of programming language or framework. On top of this, many headless CMSs offer hosted, managed CMS instances, with high-availability APIs that are designed to scale to meet high traffic demands. It’s a bright future for CMS, not only do the editors have all the features they’ve come to know and love but now many of the development pain points have also been addressed.”

Coding is Hard, Understanding Someone else’s Code is Harder.

It’s said that there are many skills needed to develop and build a successful website. This primarily depends on the type of CMS architecture you’re using. We recommended a headless CMS architecture because it only contains 2 core components: A back end to manage and store content and an API to deliver that content anywhere.Below, James describes the knowledge and skills required to learn CMS web development.

“A problem with traditional CMSs is that they tend to have a steeper learning curve. Not only do you need to understand the backend of the CMS you also need to know how to work in their supported programming language, framework, and sometimes even specific themes. Coding is hard, understanding someone else’s code is harder. On the flipside, headless CMSs are just an API. This means all you need to know is HTML/CSS/JavaScript and how to make an API call to fetch content. With technologies such as JAMstack and static site generators, you don’t even need to know a server-side programming language anymore. If you can build a website in HTML/CSS/JavaScript, then you can build a website with a CMS.”

Common Languages and Frameworks used by CMS Developers

If you’re wondering what programming language to use for creating your CMS, the answer may not be so simple. It also depends if you’re using a traditional CMS or a headless CMS, in this case we both agreed that a headless CMS was the best way to go. I knew James had a passionate take on this, so I asked him to elaborate on the most popular languages and frameworks used by CMS developers? 

“Traditional CMSs are often coupled with specific server-side programming languages such as PHP, .NET or Java (to name a few). While these programming languages are still popular, useful and relevant, they aren’t required anymore in order to integrate a website with a CMS. In the last few years, JavaScript is taking a much larger role in overall web development (with or without a CMS). Things that used to be done by traditional server-side languages are now being done in JavaScript.  

For example, you can execute JavaScript on the server using Node.js. You can run JavaScript in a build-process of a static site generator to pull content from an API, render HTML pages, and then deploy those static HTML pages. This is referred to as a JAMstack (JavaScript-API-Markup) architecture. On the frontend, modern frameworks such as ReactJS, VueJS, and Angular continue to be on the rise. One of my personal favorites (and exploding in popularity) frameworks is GatsbyJS, a progressive web-app framework built on-top of ReactJS that includes static site generation and uses GraphQL to store and access content from any data source. In fact, we just released a source-plugin for GatsbyJS + Agility CMS the other week.” 

Ending Notes

If you want to learn more about CMS development 💻 and you live in the Toronto area, join us on Oct 17th for our first annual 🚀 fastr_conf. Learn how a 🤖 headless CMS can bring all the benefits an editor has become accustomed to, while allowing you, as a developer to build re-usable components in your 🥞 tech stack, 🤯 your way. Register ASAP 🔥, only a few seats left, use promo code "first50" 💲

Top comments (10)

highcenburg profile image
Vicente G. Reyes • Edited
A problem with traditional CMSs is that they tend to have a steeper learning curve.

I agree!! I never enjoyed developing websites using wordpress.


I never enjoy developing websites using any PaaS.

joelvarty profile image
Joel Varty

Have you tried using a Headless CMS?

I'd be happy to hear your feedback.

highcenburg profile image
Vicente G. Reyes

Hi, I've used DEV & Stackbit's CMS for my personal blog and I just had a small confusion on how to properly input content but all in all I had a great experience using it unlike Wordpress, Wix, Webflow and others which I can't remember.

pedropcruz profile image
Pedro Cruz • Edited

Hello @joelvarty and thanks for your awesome post! Really liked It!

But i have a question for you: i am a developer and want to share with the world my thoughts about this world, developers have free license for using Agility CMS?

Many thanks

joelvarty profile image
Joel Varty

You bet! Sign up for a free account on

nallen805 profile image

Very helpful and informative. Thanks for the info!

joelvarty profile image
Joel Varty

Glad you found it helpful!

steelwolf180 profile image
Max Ong Zong Bao

This is really a nice comparison between traditional vs headless cms

joelvarty profile image
Joel Varty

Thanks - our team worked hard to make sure it captured the developer's point of view.