Using JAMStack with Agility CMS

We asked our President Joel Varty a few questions about why Agility CMS decided to go JAMstack.

Agility CMS
Agility CMS
Feb 4, 2020

Q: What's up with all the buzz around JAMStack!? Why did Agility CMS make a strategic decision to support JAMStack after being a .NET CMS for more than a decade?

Joel: I see three main reasons.

  1. Performance & Reliability

    JAMStack sites are statically generated, so they are incredibly fast. No web server needs to be scaled or maintained, and these static files can be delivered quickly over a global CDN - which means the response times are exceptionally quick. Further to that, JAMStack frameworks like Gatsby.js and Next.js are really good at bundling pages up into small chunks, so the actual files themselves are smaller and more responsive - everything just FEELS faster. 
  2. Security

    Since there's no webserver delivering your static files, and nothing is being computed in order to deliver your web pages, JAMStack sites are on a whole new level in terms of being secure. There simply isn't an entry point for a hacker to attack, such as exists on traditional web servers. Even better, things like distributed denial of service (DDOS) attacks are much less of a problem, since most CDN services such as Azure, AWS, Cloudflare and Stackpath also include things like a web app firewall (WAF), making it much easy to thwart these attacks. JAMStack sets you up for success.
  3. Developer preference

    A vast majority of the developer community is proficient with JavaScript. It's the most popular language by far and growing more so each year. We wanted to make sure Agility CMS empowered more developers, so we've fully embraced JAMStack in order to do that.

Q: How can using JAMStack change the lives of Agility CMS users? Is it a revolution? Or evolution?


JAMStack itself is revolutionary. It's exciting most of all because it's an easier and faster way of developing websites with fewer barriers to entry, and far fewer barriers to success. That being said, there are techniques that allow developers to adopt an evolutionary approach to getting going with JAMStack on an existing site. We're working customers and partners who have large, monolithic websites. They are using JAMStack to selectively improve the more important sections of these sites on a page by page basis. You don't have to rebuild your site from scratch if you don't want to.

Q: Can you give a specific example when you needed to bluntly tell your client  "OK, you need to start using JAMStack NOW to solve this particular pain you have, or else…"


Haha! Well, the good thing about the internet is that it's great for generating buzz, and JAMStack is buzzing right now. Our partners are either telling us they want to use JAMStack techniques, or they're asking us to provide them with guidance on how to best do that with Agility CMS. We've provided the JavaScript SDK and starter packages for the most popular tools, such as Gatsby.js, Next.js (which are both based on React.js), and Nuxt.js (based on Vue.js). Because of Agility's approach to Content Modelling and Page Management, developers can write more reusable code and give editors the power to maintain more control over the website.

If you are eager to learn more about JAMStack and Agility CMS check the video of our last webinar: NEVER BUILD YOUR WEBSITE FROM SCRATCH AGAIN: How To Migrate to JAMStack:   

Keep Reading  

If you want to learn more about JAMStack, make sure you read these articles:

If you want to learn more, check out our webinar about how Agility works as a JAMstack CMS.

Learning JAMstack? So, this eBook is for you!

eBook JAMstack for Beginners - Agility CMS and Ikius
Back to All Articles

Our Latest Posts