Articles

composable Article

Agentic CMS: Why Kontent.ai’s Vision for the Future of Content Management is Inspiring 

matt-garrepy

The Last Migration: Why Universities Keep Paying for Platforms That Don't Evolve

isabellaotero

<a target="_blank" rel="noopener noreferrer" href="https://cmscritic.com/critics/dan-drapeau">Dan Drapeau </a>is Managing Director at <a target="_blank" rel="noopener noreferrer" href="https://dxpcatalyst.com/">DXP Catalyst Consulting</a> and a CMS Critic contributor. <hr /> Composable architecture is now firmly part of mainstream enterprise conversations. Suite vendors have become more modular, and headless platforms have expanded their native capabilities, in several cases evolving into full DXPs through acquisition. AI capabilities, including emerging agentic workflows, are embedded across most major offerings. The competitive landscape has converged across architectural models.Evaluation approaches have not evolved at the same pace.Many organizations still assess DXPs through a single-track process that emphasizes feature breadth, demo cohesion, and tightly integrated product narratives. That structure naturally favors pre-composed suites and can disadvantage ecosystem-driven models before architectural tradeoffs are fully examined.This is not another debate about composable versus monolithic technology. It is a practical evaluation framework designed to ensure that platform capability and ecosystem architecture are assessed with equal rigor.By “pre-composed,” I refer to suite-style platforms that deliver a bundled set of tightly integrated products from a single vendor. While components may be licensed independently, the underlying architecture assumes close internal coupling across core capabilities.Evaluating composable and pre-composed approaches fairly requires structural changes to how selection and architectural review are conducted.<h3 id="why-a-single-evaluation-track-creates-structural-bias">Why a Single Evaluation Track Creates Structural Bias</h3>Traditional evaluations follow a single-track model: RFP issuance, vendor demos, stakeholder scorecards, and aggregate scoring. Functional breadth and demo cohesion often dominate.That structure works when all vendors provide tightly integrated suites. It becomes problematic when some vendors operate as orchestration layers or depend on ecosystem components for search, DAM, CMP, or CDP.In those scenarios, the evaluation model itself shapes the outcome. Vendors showcasing native breadth in a single interface frequently score higher than vendors demonstrating integration patterns, even when the latter may offer stronger long-term flexibility.Separating platform capability from ecosystem architecture mitigates this bias.<h3 id="the-two-track-evaluation-model">The Two-Track Evaluation Model</h3>A more balanced approach separates platform evaluation from ecosystem architecture by running two structured tracks in parallel: <h4 id="track-1.-core-platform-evaluation">Track 1. Core Platform Evaluation</h4>The first track evaluates the DXP as a product:<ul><li>Functional capability across CMS, personalization, experimentation, and adjacent experience services</li><li>Operational and governance maturity</li><li>Architectural alignment with existing systems</li><li>Non-functional readiness – including performance, security, and compliance</li><li>Licensing structure and cost trajectory</li><li>Vendor profile and strategic direction</li></ul>This clarifies what adopting the platform as the core DXP means over a multi-year horizon. <h4 id="track-2.-ecosystem-and-composability-evaluation">Track 2. Ecosystem and Composability Evaluation</h4>The second track evaluates the broader architecture independently of the platform.Rather than asking whether a DXP bundles search, CMP, or CDP as native products, this track examines how those capabilities function within the proposed architecture and whether the DXP can realistically serve as the coordination layer for a broader ecosystem. It evaluates:<ul><li>Data and analytics architecture, including warehouse alignment and experimentation visibility</li><li>Sequencing strategy across ecosystem capabilities such as CDP, personalization, and search</li><li>Search strategy, including conversational and LLM-driven experiences</li><li>AI capabilities, automation patterns, and governance controls</li><li>DAM and content asset strategy</li><li>Hosting and front-end flexibility</li><li>Integration maturity and connector quality</li></ul>The objective is to assess not only what the platform includes today, but whether it enables durable evolution over time. Best-of-breed services should integrate without architectural strain, and new capabilities should be introduced without creating lock-in, rework, or hidden dependencies.CDP strategy illustrates why this separation matters. Evaluation should focus on where customer data is modeled and how activation occurs within the architecture. In warehouse-centric environments, introducing a suite-coupled CDP can shift the system of record and create unnecessary duplication. Understanding whether activation depends on the DXP’s native data layer or can remain decoupled reveals how tightly the ecosystem is structured. Similar substitution questions apply across search, DAM, and AI.<h3 id="operationalizing-the-two-track-model">Operationalizing the Two-Track Model</h3>Separating ecosystem architecture from platform scoring ensures both models are assessed on equal footing.In practice, this model typically unfolds over 5-7 weeks. Vendors prepare and deliver platform demonstrations while ecosystem discovery and architectural modeling occur in parallel. Weighting across both tracks should be defined before demos begin and documented explicitly, since bias can re-enter through weighting decisions even when intent is neutral.<h3 id="the-complexity-of-running-parallel-tracks">The Complexity of Running Parallel Tracks</h3>Parallel tracks introduce rigor and practical complications.Differences in native coverage complicate comparison. If CMP, search, or CDP are weighted heavily but not natively provided by all vendors, those capabilities should move into the ecosystem track rather than penalizing the platform score. Foundational capabilities such as CMS remain in the platform track, while optional or externally delivered services belong in ecosystem evaluation.Vendors may bring partners into demos to illustrate integration. That can be appropriate, but evaluation should focus on architectural feasibility, operational ownership, and governance responsibility rather than demo choreography.When multiple DXP vendors recommend the same ecosystem component, such as a shared search or data platform, that element should be evaluated independently so that differences in governance, scalability, and integration maturity remain visible.Without disciplined separation, weighting decisions can distort outcomes even when intent is neutral.<h3 id="synthesizing-the-results">Synthesizing the Results</h3>Synthesis is not about averaging scores.Track 1 produces weighted scoring across functional, operational, architectural, and non-functional criteria. Track 2 evaluates whether the platform can realistically serve as the hub of a broader ecosystem.For composable-oriented platforms, this means assessing how cleanly external products plug in for search, CDP, DAM, or CMP, and what governance or integration overhead that introduces. For pre-composed suites, it means pressure-testing substitution claims. If a component can be replaced, what constraints exist in practice? Does personalization depend on a native CDP? Does experimentation assume native analytics?Review both outputs side by side and reconcile tensions. A platform may score highly in functional breadth yet limit ecosystem flexibility. A composable option may offer architectural openness while introducing additional governance responsibility.Leadership must articulate what the organization is optimizing for: time-to-value, long-term flexibility, operational simplicity, or ecosystem optionality. Without clarity, decisions default to demo cohesion.Sequencing also becomes part of synthesis. Organizations may defer CDP activation or advanced orchestration. The selected architecture should support phased rollout without creating integration debt or future re-platforming risk.Shortlisting 2 vendors from an initial field of 4-5 keeps reconciliation manageable while preserving competitive tension. The final phase shifts toward structured stress testing under realistic growth and governance scenarios.<h3 id="from-validation-to-stress-testing">From Validation to Stress Testing</h3>Finalist discussions should test structural durability.Evaluate governance scalability as experimentation and personalization expand across properties. Test how the architecture performs in a multi-site or multi-brand environment with shared components and localized control. Examine data portability if strategic direction shifts. Assess how AI-generated content is governed, reviewed, and audited. Confirm that advanced capabilities can be deferred without requiring architectural rework or creating hidden dependencies.This stage focuses less on feature confirmation and more on alignment with long-term operating models.<h3 id="the-critical-checklist-for-dxp-evaluation">The Critical Checklist for DXP Evaluation</h3>A disciplined evaluation model should answer:<ol><li>Have you separated platform evaluation from ecosystem design?</li><li>Is weighting across both tracks defined before demos begin?</li><li>Does the architecture align with your current operational maturity and support the governance structure you will require as scale increases?</li><li>Does the vendor’s roadmap and acquisition pattern preserve your architectural autonomy over time?</li><li>Can phaseable capabilities such as CDP be introduced deliberately, and does the architecture support evolving personalization and flexibility across vendor solutions?</li><li>Have non-functional realities and full ecosystem costs been modeled early?</li></ol>Composable and pre-composed DXPs represent architectural strategies along a spectrum. A structured two-track evaluation approach ensures that whichever model is selected, it is chosen for structural alignment and long-term outcomes rather than surface cohesion. <hr /><h3 id="upcoming-events">Upcoming Events</h3> <img style="width:34.15%" src="https://cmscritic.com/ms-content/uploads/2026/01/logo_jday_hor.png" /><h4 id="joomladay-usa-2026"><a target="_blank" rel="noopener noreferrer" href="https://www.jdayusa.com/">JoomlaDay USA 2026</a></h4>April 29 - May 2, 2026 – Delray Beach, FloridaBe part of the Joomla community in one of the most iconic cities in the world! JoomlaDay USA 2026 is coming to Delray Beach, and you can join us for a dynamic event packed with insights, workshops, and networking opportunities. Learn from top Joomla experts and developers offering valuable insights and real-world solutions. Participate in interactive workshops and sessions and enhance your skills in Joomla management, development, design, and more. And connect with fellow Joomla enthusiasts, developers, and professionals from across the world.<a target="_blank" rel="noopener noreferrer" href="https://www.jdayusa.com/"> Book your seats today.</a> <img style="width:30.06%" src="https://cmscritic.com/ms-content/uploads/2026/01/cms-summit-26-logo.jpg" alt="" /><h4 id="cms-summit-26"><a target="_blank" rel="noopener noreferrer" href="https://www.boye-co.com/conferences/cmssummit26">CMS Summit 26</a></h4>May 12-13, 2026 – Frankfurt, GermanyThe best conferences create space for honest, experience-based conversations. Not sales pitches. Not hype. Just thoughtful exchanges between people who spend their days designing, building, running, and evolving digital experiences. CMS Summit brings together people who share real stories from their work and platforms and who are interested in learning from each other on how to make things better. Over two days in Frankfurt, you can expect practitioner-led talks grounded in experience, conversations about trade-offs, constraints, and decisions, and time to compare notes with peers facing similar challenges. Space is limited for this exclusive event, <a target="_blank" rel="noopener noreferrer" href="https://www.boye-co.com/conferences/cmssummit26/tickets">so book your seats today.</a> <img style="width:30.13%" src="https://cmscritic.com/ms-content/uploads/2025/12/image-1765546475634.png" /><h4 id="umbraco-codegarden-2026"><a target="_blank" rel="noopener noreferrer" href="https://codegarden.umbraco.com/">Umbraco Codegarden 2026</a></h4>June 10–11, 2026 – Copenhagen, DKJoin us in Copenhagen (or online) for the biggest Umbraco conference in the world – two full days of learning, genuine conversations, and the kind of inspiration that brings business leaders, developers, and digital creators together. Codegarden 2026 is packed with both business and tech content, from deep-dive workshops and advanced sessions to real-world case studies and strategy talks. You’ll leave with ideas, strategies, and knowledge you can put into practice immediately. <a target="_blank" rel="noopener noreferrer" href="https://codegarden.umbraco.com/">Book your tickets today.</a> <img style="width:36.69%" src="https://cmscritic.com/ms-content/uploads/2026/01/open-source-cms-26.jpg" /><h4 id="open-source-cms-26"><a target="_blank" rel="noopener noreferrer" href="https://www.boye-co.com/conferences/opensourcecms26">Open Source CMS 26</a></h4>October 20–21, 2026 – Utrecht, NetherlandsJoin us for the first annual edition of our prestigious international conference dedicated to making open source CMS better. This event is already being called the “missing gathering place” for the open source CMS community – an international conference with confirmed participants from Europe and North America. Be part of a friendly mix of digital leaders from notable open source CMS projects, agencies, even a few industry analysts who get together to learn, network, and talk about what really matters when it comes to creating better open source CMS projects right now and for the foreseeable future. <a target="_blank" rel="noopener noreferrer" href="https://www.boye-co.com/conferences/opensourcecms26/tickets">Book your tickets today.</a>

Composable vs. Pre-Composed DXPs in 2026: A Two-Track Evaluation Framework for Modern DXP Selection

dan-drapeau

AI ROI? A-OK: MACH Alliance Report Says Enterprises with Composable Foundations are Netting Returns

Flying the Agentic Skies: easyJet’s Paul Curtis on Taking Off with Agents and Soaring with MACH

Orchestrate and Create: Umbraco Compose Streamlines Integration of New Technologies and Agentic AI

Griddo DXP Powers University Websites and Digital Experiences with a PhD in Performance

Power your CMS on AWS

Manage your websites & apps in the most trusted cloud.

#ffffff

Step into the AI ‘Time MACHine’: Jason Cottrell of MACH Alliance on what’s ahead in 2026

What is a CMS in 2026? Mark Demeny on AI, Content Supply Chains, and the Future of Content Management

Combatting Composable Regret in 2026

filip-larsen

The Headless Holodeck: Joel Varty of Agility CMS on Warp-Speed Demos, AI, and the Next Generation of CMS

Welcome to the 'Agent Ecosystem': MACH Alliance unites tech leaders to build the future of enterprise AI

There’s a little-known psychological condition called footballis doldrumus that affects millions of people each year.
This peculiar phenomenon strikes around mid-July – the “dog days,” as we say – causing North American football fans to incessantly pine for the pigskin. The hotter the summer, the more intense the craving. And this has been a hot one.
Symptoms include (but are not limited to): listing the season opener as a holiday on your Outlook calendar, leaving messages on refrigerator wipe boards that read “6 weeks left ‘til kickoff,” and waking up from a deep sleep and shouting first and ten for no apparent reason.
It’s a sinister malady that Joel Varty is undoubtedly familiar with, given his own experience on the field. When we met in New York City this past May, he told me about his son’s goal of playing football at the collegiate level, and perhaps one day in the NFL. I learned later that Joel played during college, and has a passion for coaching. 
As a victim myself of footballis doldrumus, talking with Joel was a bit like a support group on multiple levels. I resisted any mention of Tom Brady for fear of getting too off-topic (or sounding like an insipid fanboy), and we focused instead on the real-world challenges impacting the content management game.
In his role as Chief Technology Officer at <a href="https://www.cmscritic.com/agility-cms-introduces-simplified-pricing-tiers-for-headless-content-management/">Agility</a> – <a href="https://www.cmscritic.com/top-free-headless-cms-platforms/">a headless CMS</a> – Joel is facing a deep bench of competitors with similar strengths on the field. As many platform features become commoditized, executing the right plays to differentiate is essential to win.
When I learned that Agility was releasing new updates to its UI, I caught up with Joel to learn more about his company’s strategy and get his perspective on the marketplace. We talked about how composable is changing the game, why trust is critical to customer experience, and how he’s quarterbacking his own way to victory.
<h2>Coaching the long game in CMS </h2>
Like most content management veterans, Joel’s path to product was circuitous. While playing football at the <a href="https://www.uoguelph.ca/" target="_blank">University of Guelph</a> in Ontario, he parlayed a love of prose into programming and graduated with honors in English and Computer Science.
It’s not an uncommon story in the development world. Some of the best coders I’ve ever worked with started analyzing James Joyce before JavaScript.
Guelph is also where Agility’s CEO, <a href="https://www.linkedin.com/in/jonvoigt/">Jon Voigt</a>, attended – and the two have been teaming up ever since. They both endured the rise and fall of the dot.com era, and that lead to a stint of website consulting gigs that encompassed the buildout of their own CMS.
“[I think] everyone has said, ‘hey, I can build my own CMS’ at some point,” he recalls with laughter. “We started ours around 2005 and kept doing it because we really like working together. But by 2017, we decided we didn’t want to build websites anymore – we just wanted to build a CMS, and we think headless CMS is the way to go.”
Joel also said that one of the catalysts for this shift in priorities was the maturity of the Agility CMS itself. Not only was it stable and trusted at a foundational level, but it now had enough customers running on it to make financial sense. As a totally bootstrapped company with solid profitability, they were able to sell off some of their existing contracts in 2018 and go all-in on the CMS.
<hr />
<h4>“I think where Agility shines isn't in a specific vertical market. It's with folks who have complex, unique needs – and you have to approach those in a special way. We love to teach our partners how to do that.”</h4>
<hr />
“It was really hard to let go,” Joel admitted. “Giving [our business] to partners was a double-edged sword, but it was great to stop competing with our partners. We were always the first party vendor building stuff, so we didn't feel it was fair to have a product we have an upper hand with.”
I asked Joel how they made the transition successful, particularly around client care. I’ve heard this projects-to-products story many times, but the failures often come from a lack of top-down leadership and cultural investment – like a self-inflicted form of pass interference. 
“We actually looked at our core values as a company, and really focused on teaching,” he said, “so we took the lessons we’ve learned and started teaching our partners how to do things. I think where Agility shines isn't in a specific vertical market. It's with folks who have complex, unique needs – and you have to approach those in a special way. We love to teach our partners how to do that.”
Teach... or coach? Either way, Joel and his team have made the knowledge transfer a big part of the Agility experience. This includes clear documentation, tutorials, transparent practices, and regular communication with their community of users. 
<h2>Outplaying sameness with service </h2>
At a recent event, I was discussing the headless CMS category with several attendees, and the subject of commoditization came up (as it frequently does). One of the pedaled analogies was that DXPs are akin to “apples and oranges” based on their feature sets, while headless CMSes are more like red apples versus green.
I asked Joel about this swelling box of apples and how he views the commoditization challenge.
“It’s interesting because there's almost more of a move to be enough of the same so that you're recognizable across vendors – like things have to be ‘same enough,’” he observed. “If you're too different, that's not actually a good thing, because it's hard to compare in a DX or composable space. So we strive to be ‘same enough’ while being unique.”
Commoditization is a real threat, but Agility is rising above the challenge by investing in its customer experience. This is embodied by its “White Glove Service,” which assures each client receives human interaction – which Joel admits is a challenge for most vendors as it inhibits scalability. But when the average lifetime of an Agility customer is eight to ten years, there’s value in this hands-on approach.
This felt like a key differentiator to me, so I asked if it was a key selling point for Agility.
“We haven't been using it enough,” Joel said. “We need to listen more to that part of our customers’ reactions. Our product was built based on customer feedback, and that's how we decide what we're going to do. It's 100% customer driven. We spent a lot of time and effort tracking what people say and want regarding features. And that's how we decide what we build into the product.”
To that end, Agility continues to provide transparency around its roadmap, engaging with its users via <a href="https://roadmap.agilitycms.com/tabs/3-launched" target="_blank">roadmap.agilitycms.com</a> around ideation. Joel said developers are very vocal within their community, but Agility strives to ensure that marketers and business decision-makers have a voice. That’s important, given the critical role of content operations within most enterprises.
“Our ideal customer needs to understand the value of content,” he explained. “Sometimes it's the developer, an information management role, a head of marketing, a CTO – maybe even the CEO of a smaller company. But if they can get the value of that content… then that’s going to be a good fit for Agility.”
<h2>Tackling the composable hype-cycle with trust</h2>
As a headless CMS, I asked Joel what he thought about the growth of composable and the advent of <a href="https://www.cmscritic.com/wrestling-with-category-confusion-in-the-dxc-slackdown/">DXC (digital experience composition)</a> and other categories emerging in the space. On the one hand, DXC vendors like <a href="https://www.cmscritic.com/uniform-raises-28m-in-series-a-funding-round-for-composable-dxp/">Uniform</a> are solving the visualization challenges for headless CMSes. But are these TLAs (or “three-lettered acronyms” for the unindoctrinated) helping or hindering our understanding of the composable space?
“My opinion is those acronyms are holding us back as much as they bring us forward,” he said. “They give us something to talk about, but you always have to go beyond that. There's always some explaining that has to happen when you're talking to someone who actually wants to use this in their business. I think it comes down to having more trust between people.”
That trust is hard-earned, as Joel explained. <a href="https://www.cineplex.com/" target="_blank">Cineplex</a>, one of Agility’s customers since 2007, has relied not just on its CMS, but on the expertise of a team that understands their business imperatives. Over the years, trust in Agility has guided the cinema giant’s digital transformation, from site rebuilds to infrastructure changes. This ingredient of trust has shaped Joel’s perspective on composable, which is as much about the business considerations as the technology posture.
“I think the idea of enterprise software should mean long-term ROI, not just fast ROI,” he said. “How can you take a piece out and put it back in, or fix something that you don't like? That, to me, is like the best of composable.”
I probed further about the importance of composable standards and the rise of the <a href="https://www.cmscritic.com/the-future-is-composable-a-conversation-with-new-mach-alliance-president-casper-rasmussen/">MACH Alliance</a> over the last few years. The organization has advocated for best-of-breed technologies that meet the rigid standards of MACH (Microservices, API-first, Cloud-native SaaS, Headless). Are relationships with vendors in DXC, e-Commerce, search, and other categories becoming an important growth channel for headless CMS?
“Yes, and the long-term goal is to have a combination of technology and relationships accelerated, where it's like a pre-built stack or grid that everyone knows works,” he said. “So CMS is going to be hosted here, and it will have this for search, this personalization, and this for commerce. We know how it all works together – and everyone trusts it.”
Joel admitted that we might be three or four years away from any broad market buy-in, suggesting that it’s still a hard sell given the institutional culture of some IT departments. This is why the efforts of thought leaders within the MACH Alliance community have been key to advancing the growth of composable.
“They won’t get it until they trust it,” Joel punctuated.
<h2>Agility’s new UI delivers more than a fresh uniform</h2>
I heard Agility’s plans for its new user interface some time ago, well before its scheduled GA. While modernizing a UI is an accepted part of any software lifecycle, it offers as many opportunities as challenges. Most people loathe change – so any modification can be met with temperamental responses. That’s why this UI "refresh" is as much about empathy and sentiment as it is about systems and processes.
I wanted to hear how Agility approached this undertaking, and what stood out for Joel.
“Interestingly enough, we started this new UI project about 18 months ago,” he revealed. “The last time we redid our UI was in 2015, and Jon [our CEO] and I knew that you always do it once and then refresh it after everyone's already had a chance to see it. We started base testing with cohorts of new or existing users, and we actually brought design in-house – which, for a smaller company, was a big deal. We also have this amazing person who A/B tested different things and conducted interviews to determine what makes [users] feel better. And we focused as much on that as we could and tried to be very consistent about how we handled content.”
As Joel detailed the process, it was clear his team didn’t cut things out or remove extraneous elements just to satisfy the simplification goal. To his point, CMS users claim to want all the features – even if they won’t be using them.
“There's a real balance there,” he continued. “But overall, we wanted things to be faster and easier across the board and ultimately make people feel better.”
I had a chance to peruse the new UI while comparing it to the classic version (which will continue to be available to users). Right off the bat, the visual design system is cleaner and more streamlined, offering a modern lightweight experience that feels more like an app. The main navigation panel provides more contrast, aimed at reducing eye strain during prolonged use. The authoring tools are still intuitive and familiar, a staple of Agility's previous UI. 
<img src="https://cmscritic.com/ms-content/uploads/2023/07/agility-new-ui-2023-1024x692.jpg" alt="New Agility software UI" />
You can read about the full scope of features <a href="https://www.cmscritic.com/agility-unveils-refreshed-design-system-in-ui-delivering-enhanced-user-experience-and-accessibility/">in our previous post</a>, but a few stand out, including new filters that offer augmented search. Users will find the new org selector handy, and there’s a slick heartbeat indicator coming that will provide greater visibility around specific events and tasks. Also noteworthy are the drag-and-drop model editor and the table column reordering, both designed to simplify and accelerate tasks.
You can check out the UI for yourself by creating an Agility account at <a href="http://www.agilitycms.com">www.agilitycms.com</a>. While Joel and his team are still fine-tuning some details, scope creep has pushed the original launch date into late July – a frustrating reality of software launches.
“But I think it will be worth it,” he said. “Our company anniversary is July 19, so I'm kind of thinking maybe that's a good day.”
<h2>Keeping the game fun – even with AI on the field</h2>
I’ve already waxed extensively about Joel’s affinity for football. But that affection is grounded by a deep gratitude for his family and their shared pastimes. Much like his dual pursuits of literature and computer science, he blends a love for athletics and a passion for art and scholarship in his life outside Agility.
“I am super blessed with two really, really cool kids,” he said glowingly. “My son plays football, and I've been a dedicated ‘dad coach’ for that. But my daughter is super into theater, and I love directing, being on stage, or getting involved from a community standpoint. It's got nothing to do with technology – it's just having fun.”
As we rounded out our time together, the subject of AI meandered into the conversation. What does Joel think about the advent of this technology and its impact on content? He has, after all, helped shape the CMS space over the last two decades. What does the world look like now that ChatGPT is a growing fixture in the creative process?
“I look at it like this: ChatGPT needs us,” he said. “It copies ideas. Nothing comes out of thin air, and someone has to come up with the ideas.”
Kind of like a quarterback audibling on the field. Sometimes, human instinct takes over – no matter how rehearsed the play might be. And while AI may prove its worth as a key automation tool, it’s heartening to hear from a content veteran that people are still core to the process.
As a headless CMS in a densely-packed market, Agility is executing in all the right ways. And with so many seasons under its belt, the platform and its people have proven resilient in the face of change. That speaks volumes about its vision and go-to-market strategy, which gives it a strong position in the new composable game. 
I still reserve the mantle of GOAT for Tom Brady, but Joel definitely has my vote for the “CMS Hall of Fame.”

Playing to Win in the Headless CMS Game: Interview with Joel Varty, CTO at Agility CMS

<hr /> Hey, it’s Friday, folks! Queue the confetti!!!If you don’t already have a skip in your step, I highly recommend adding some music to your current situation. And if you happen to stumble upon a terrestrial ‘80s rock station or Spotify playlist, maybe you’ll <a target="_blank" rel="noopener noreferrer" href="https://en.wikipedia.org/wiki/Working_for_the_Weekend">get lucky and score some Loverboy.</a>As those Canadian crooners have maintained for almost a quarter of a century, everybody’s working for the weekend…Of course, “working stiff” anthems aside, Murphy’s Law is also a song on repeat, particularly in the digital world. We’ve all heard the macabre pipe organ play when a “503: Service Unavailable” message appears on screen where a website homepage should.Why on Friday? And why does stuff invariably hit the fan at 4 PM, just as Happy Hour starts calling your name?That’s the central premise of a fictional yet highly relatable blog series from <a target="_blank" rel="noopener noreferrer" href="https://www.linkedin.com/in/joelvarty/">Joel Varty,</a> CTO at <a target="_blank" rel="noopener noreferrer" href="https://cmscritic.com/products/agility">Agility CMS.</a> It’s called “The Incremental Approach,” and across four snappy installments, it weaves a sordid tale of haywire and hope – and how a leaked press release turned a Friday afternoon into a ring of fire (hats off to the OG loverboy, Johnny Cash).I won’t give too much away, but this engaging series reminded me of the many lessons we learn along the way, and how there’s no replacement for real-world experience. For those of us responsible for the uptime of high-availability website workloads, “game day” testing our infrastructure for unexpected traffic spikes, outages, and other scenarios is essential. But there are always things we can’t see or prepare for – even with the best runbooks and failovers in place. For those situations, we need human assets. Seasoned leadership. Teams that are ready to think on their feet and bring unconventional ideas to the table.As Loverboy might say, the trusted people who have a piece of your heart. If your Friday is dragging, inject it with a little fun! This story has everything you want: drama, intrigue, <a target="_blank" rel="noopener noreferrer" href="https://cmscritic.com/products/nextjs">Next.js.</a> All the trappings of a world gone mad, and how a headless CMS – and its intrepid team – saves the day.Tapping his signature humor, Joel traverses his own playlist of hits, from how a CDN can turn a sad song into a happy one, how running code at the edge can rock the room, and how incremental steps can rewrite the lyrics and take a whole new tune to the top of the charts. You can read the series here:<ul><li><a target="_blank" rel="noopener noreferrer" href="https://agilitycms.com/blog/the-incremental-approach-go-to-market-in-less-than-half-the-time-part-1">Agility CMS: “The Incremental Approach” – Part 1 </a></li><li><a target="_blank" rel="noopener noreferrer" href="https://agilitycms.com/blog/the-incremental-approach-go-to-market-in-less-than-half-the-time-part-2">Agility CMS: “The Incremental Approach” – Part 2 </a></li><li><a target="_blank" rel="noopener noreferrer" href="https://agilitycms.com/blog/the-incremental-approach-go-to-market-in-less-than-half-the-time-part-3">Agility CMS: “The Incremental Approach” – Part 3 </a></li><li><a target="_blank" rel="noopener noreferrer" href="https://agilitycms.com/blog/the-incremental-approach-go-to-market-in-less-than-half-the-time-part-4">Agility CMS: “The Incremental Approach” – Part 4</a></li></ul> <hr /><h4 style="text-align:center" id="looking-for-guidance-on-agility-cms?-talk-to-an-expert.">Looking for guidance on Agility CMS? <a target="_blank" rel="noopener noreferrer" href="https://cmscritic.com/contact">Talk to an expert.</a></h4><hr /> <h3 id="upcoming-events">Upcoming Events</h3> <img style="width:31.83%" src="https://cmscritic.com/ms-content/uploads/2025/01/cms-connect-2025-logo.png" alt="" /><h4 id="cms-connect-25"><a target="_blank" rel="noopener noreferrer" href="https://www.boye-co.com/conferences/cmsconnect25">CMS Connect 25</a></h4>August 5-6, 2025 – Montreal, CanadaWe are delighted to present the second annual summer edition of our signature global conference dedicated to the content management community! CMS Connect will be held again in beautiful Montreal, Canada, and feature a unique blend of masterclasses, insightful talks, interactive discussions, impactful learning sessions, and authentic networking opportunities. Join vendors, agencies, and customers from across our industry as we engage and collaborate around the future of content management – and hear from the top thought leaders at the only vendor-neutral, in-person conference exclusively focused on CMS. Space is limited for this event, <a target="_blank" rel="noopener noreferrer" href="https://www.boye-co.com/conferences/cmsconnect25">so book your seats today.</a>

Hey Loverboy, Don’t be Heartbroken: Agility CMS Offers Levity and Lessons in ‘The Incremental Approach’ 

CMS Summit 26

Find out at Open Source CMS 26, October 20-21 in Utrecht, Netherlands

What's ahead for Open Source CMS?

Explore a wide range of informative articles on composable, insights, and industry updates. Stay informed and ahead of the curve with our diverse collection of news and posts covering the latest trends and developments in the industry

News

Power your CMS on AWS

What's ahead for Open Source CMS?