Articles

Contributor Article

Reflections on CMS Kickoff 25 from ‘The AEM Guy’

tom-cranstoun

<hr /> In today’s competitive business environment, delivering dynamic experiences across multiple digital channels is becoming increasingly important. In the past, a traditional monolithic CMS was the go-to solution for managing website content in bulk, offering a comprehensive approach with integrated frontend and backend functionalities.However, as the importance of web channels for media distribution grew, developers within larger enterprises recognized the limitations of monolithic solutions in managing complex, structured content or delivering unique frontend capabilities. This led to the rise of custom, internal CMS solutions. Performance and extensive customization were possible but at huge engineering costs and time pressure to plan, develop, and uphold these systems.Since 2007, the rise in smart devices has welcomed a new era of content consumption across diverse channels. The move significantly burdened both monolithic CMS technology and content teams.The need for a multi-channel content strategy and a modern tech stack made the limitations of traditional CMS more apparent. Even today,<a target="_blank" href="https://hygraph.com/resources/future-of-content"> 8 in 10 tech leaders</a> think their current CMS holds them back with inefficient developer or editorial experiences.<h3 id="elevating-tech-teams-with-cms-modernization">Elevating tech teams with CMS modernization</h3>The heavy burden developers face with maintaining custom CMS platforms not only leads to burnout – <a target="_blank" href="https://blog.jetbrains.com/team/2023/11/20/the-state-of-developer-ecosystem-2023/">experienced by nearly 73% of developers</a> at some point in their careers – but also acts as a significant restriction. Consequently, organizations are increasingly looking to modernize their CMS to alleviate these pressures.An in-house CMS requires ongoing maintenance, like keeping an orchestra in tune and ensuring all musicians play harmoniously. It’s also less scalable as it’s often built by a small group of people, so they are the only ones who can access and make changes to the system. Subsequently, it’s hard to manage as the project scales, and the small group of developers who built the solution will be stuck maintaining the code base. Modern headless CMS platforms can greatly enhance the capabilities and efficiency of tech teams, freeing them from the constraints of maintenance around custom platforms and empowering them to focus on driving innovation. There are many other benefits to consider, too: <h4 id="1.-increased-developer-velocity">1. Increased developer velocity</h4>Accumulated technical debt from maintaining custom middleware can reduce developer velocity, slow release cycles, and hinder an organization's ability to maintain a continuous release schedule. <h4 id="2.-improved-app-performance">2. Improved app performance</h4>Performance is a key indicator of your project's success. It's also closely connected to your business since you lose revenue when your performance is poor. A CMS failure can be detected by business metrics such as lost revenues, which are influenced by poor performance indicators such as slow page load speed and low core web vitals. <h4 id="3.-stay-current-with-the-latest-tech">3. Stay current with the latest tech</h4>The technology landscape is ever-evolving. Naturally, some of the latest technologies work better than outdated ones. The advantage of a headless CMS is that you can choose any technology you like and easily switch the front end without changing your CMS. <h4 id="4.-future-proof-technology-strategy">4. Future-proof technology strategy</h4>A tech leader should choose IT vendors that can adapt quickly to an unknown future. A headless architecture with content federation puts data in one place so teams can scale the digital experience. Developers get all the flexibility of headless without having to build, host, secure, and ensure the performance of custom middleware.   <h4 id="5.-talent-acquisition">5. Talent acquisition</h4>Legacy systems are hard to understand, making developers less productive and less attractive when recruiting new team members. It’s much easier to handle things in-house if everything needed to work with the CMS can be easily found in any tech stack. <h4 id="6.-heightened-security">6. Heightened security</h4>Unlike a traditional CMS, a modern headless CMS decouples the backend content repository layer from the frontend presentation layer. This separation allows for greater security because the content management layer is isolated and can be protected independently.<h3 id="why-headless-is-the-way-forward">Why headless is the way forward</h3>Adopting a headless CMS with content federation can offer flexibility, scalability, and streamlined content distribution across multiple channels. Furthermore, by separating the frontend and backend, this approach lays the foundation for organizations to meet their technical and content requirements swiftly, allowing technology teams to develop with any technology for any platform.At a time when content is king, your CMS needs to be a gateway to digital transformation rather than a barrier. <hr /><h3 id="upcoming-conferences">Upcoming conferences</h3> <img style="width:29.67%" src="https://cmscritic.com/ms-content/uploads/2024/01/cms-connect-2024-logo.png" alt="CMS Connect 24 logo" /><h4 id="cms-connect-24---sold-out"><a target="_blank" href="https://www.boye-co.com/conferences/cmsconnect24">CMS Connect 24</a> - SOLD OUT</h4>August 6-7, 2024 – Montreal, CanadaWe are delighted to present our first annual summer edition of our prestigious international conference dedicated to the global content management community. Join us this August in Montreal, Canada, for a vendor-neutral conference focused on CMS. Tired of impersonal and overwhelming gatherings? Picture this event as a unique blend of masterclasses, insightful talks, interactive discussions, impactful learning sessions, and authentic networking opportunities. <img style="width:29.58%" src="https://cmscritic.com/ms-content/uploads/2024/01/cms-kickoff-2025-logo.png" /><h4 id="cms-kickoff-25"><a target="_blank" href="https://www.boye-co.com/conferences/cmskickoff25/tickets">CMS Kickoff 25</a></h4>January 14-15, 2025 – Tampa Bay Area, FloridaJoin us next January in the Tampa Bay area of Florida for the third annual CMS Kickoff – the industry's premier global event. Similar to a traditional kickoff, we reflect on recent trends and share stories from the frontlines. Additionally, we will delve into the current happenings and shed light on the future. Prepare for an unparalleled in-person CMS conference experience that will equip you to move things forward. This is an exclusive event – space is limited, so secure your tickets today.

 Roadmap to Digital Experience Success: Six Ways to Future-Proof Your CMS While Elevating Your Tech Teams

michael-lukaszczyk

In any industry, buzzwords abound! 
In the Digital Experience (DX) landscape, it is no different – and you will hear a handful of terms that seemingly set the standard for the ecosystem.
However, you might not know what they all mean and how they are different from one another. That could pose a major problem, particularly as a technology, marketing, and/or business leader in the enterprise who is expected to be at one with the trends and best practices while leading their organization to digital glory.
I recently sat down for an hour during a<a href="https://www.youtube.com/live/tDAVv1VwHgU?feature=share"> DX Café interview with Andrew Kumar,</a> VP of Customer Solutions at <a href="https://www.cmscritic.com/uniform-adds-new-visual-editing-and-integration-features-to-enhance-dxcp/">Uniform</a>, and we talked about four of the oft-heard concepts around the DX industry “watercooler.”
Uniform is an interesting company to start with as a frame of reference for much of this headless and composable DXP and product industry. As Kumar noted in the discussion, Uniform is “a rapidly evolving product set, but it is very much this visual workspace for digital teams.” 
One of our first orders of business was to define four specific terms within DX architecture: Monolithic, Headless, MACH, and Composable.
<h2>Monolithic: "All your software embedded into one application"</h2>
Kumar discussed the transition from monolithic systems to more modular, composable systems in enterprise technology. Traditionally, monolithic systems encapsulated all software functions in one application, which led to challenges due to the complexity of enterprises. Companies often had to adapt their processes to the monolithic system or spend significant resources to adapt them to their business.
Kumar suggests that enterprises' complexities arise due to their constant need to meet customer demands, leading to diverse offerings. When enterprises attempt to fit monolithic systems into their complex business operations, they often encounter difficulties.
In response to these challenges, monolithic platforms decompose into modular structures to support these complex business needs.
“I am starting to shy away from the term monolithic,” said Kumar. “And I'm shying away from that because the historical monolithic platforms are decomposing themselves.”
However, Kumar mentions that businesses often underestimate their complexity until they have analyzed their operations. Only when the complexities are fully understood can technology be molded around the business rather than vice versa.
He uses the term "all in one" rather than monolithic, as the platforms are becoming more modular and adaptable to fit the needs of the business. However, these all-in-one systems often do not integrate well with external modules, akin to battery packs that only fit one brand of tools.
While all-in-one solutions can be beneficial due to their convenience, speed to market, and easier vendor management, they often do not excel in any particular area, only offering adequate solutions for various functions. This can be a drawback for businesses requiring a specific solution or the best feature. Despite these shortcomings, it can prove valuable if the out-of-the-box solution fits an enterprise's needs.
Kumar concludes that the move away from monolithic systems is largely based on the level of complexity and customization that a business requires. The more complex and custom a business needs, the more likely a monolithic system is to be an impediment.
<h2>Headless: "Kind of a hot keyword"</h2>
Kumar talked about the concept of "<a href="https://www.cmscritic.com/top-free-headless-cms-platforms/">headless</a>" systems, which are becoming popular in the tech industry. Headless systems offer more flexibility than traditional "all-in-one" systems, as they separate the content from how it's presented to the customer. This decoupling allows for easier content distribution across various channels.
In an all-in-one system, content creation and presentation are intertwined. For instance, a Content Management System (CMS) creates webpages and websites. However, presenting the same content on a mobile app or other platforms like email channels, digital displays, or VR headsets requires significant effort to untether the content from its original presentation.
“An all-in-one CMS builds webpages and websites,” said Kumar. “(but) then if you try to build a mobile app with the all-in-one, you have to untether. You have to undergo a lot of effort to create flexibility. If you try to put that content into an email channel, or a digital display or a VR, like an Apple VR headset, it's a lot of work. It's feasible, but it's a lot of work.”
Conversely, headless systems don't know or dictate where the content will end up. The content is consumed through an API and can appear on a website, an app, or other platforms. This gives tremendous flexibility and allows reusing content across various touchpoints and channels.
The challenge with headless systems is that they do not inherently provide a way to preview how the content will appear in different consuming applications. Over the past six to seven years, Kumar has been developing tools to enable such previews.
The appropriateness of headless systems depends on the industry and the nature of customer interactions. Headless systems make sense in industries like telecom, where most customer interactions are through mobile devices or chatbots. Some organizations start by using headless for a single website before expanding to multiple websites, thereby beginning to take advantage of the system's flexibility. However, it's a different paradigm with a lean, out-of-the-box solution.
<h2>MACH: "Very high bar for standards of quality"</h2>
Kumar noted that the MACH in the <a href="https://www.cmscritic.com/the-future-is-composable-a-conversation-with-new-mach-alliance-president-casper-rasmussen/">MACH Alliance</a> stands for Microservices, API-first, Cloud-native, and Headless. The MACH Alliance sets high standards for vendors in the tech industry, and not every vendor meets these standards. 
Like Kumar's company Uniform, those who receive approval can assure prospective buyers that their platform has been audited and meets specific technical standards. This approval can help support both the buyers' previous and future investments.
Kumar acknowledges criticism that the MACH Alliance is not inclusive but argues that maintaining high standards is necessary to push the industry forward. The high bar for entry ensures that the MACH Alliance seal retains its value and is not awarded to companies that do not meet its stringent criteria. Therefore, he views the exclusivity of the Alliance as a potential strength rather than a weakness, ensuring that only vendors that meet the highest standards are admitted.
<h2>Composable: "The way it's being defined is learning the lessons from the previous three terms"</h2>
Kumar lastly broke down the concept of "composable" systems, stating that this is the latest term in the tech industry. He sees it as a natural evolution from monolithic to all-in-one to headless systems and now to composable systems.
Traditional monolithic systems are now decomposing into composable systems. They're breaking down into smaller, more manageable modules that can be reconfigured per business needs.
“Headless tools are generally composable by default,” asserted Kumar. “Because they're unique, like ring-fenced capabilities that can be plugged and played as necessary.”
The MACH Alliance's standards, Kumar explains, push the needle on what it means to be truly composable. Having APIs on top of any software does not make it headless or composable. He highlights the importance of having clean, well-defined microservices to manage the platform's infrastructure. He also emphasizes the necessity of being "API first," where APIs get published concurrently with features.
Moreover, he addresses the importance of the Cloud in the MACH model. While one might have a headless system hosted locally, it would not meet the requirements of being self-serve, auto-updating, and cloud-native. In a cloud environment, the vendor takes care of security patches, reducing the maintenance burden on users.
Finally, he highlights the value of being composable for complex business enterprises. Adapting technology to business needs is vital in a rapidly changing business environment. While "composable" hasn't gained much search volume or intent yet, he anticipates it may become the next hot keyword in the industry.
Education is paramount in the ever-shifting DX industry. We hope you have gained a better understanding of some of the key principles that are frequently raised in conversations. 
<hr />
<a href="https://www.cmscritic.com/critics/matthew-mcqueeny/">Matt McQueeny</a> is part of the leadership team at <a href="https://konabos.com/" target="_blank">Konabos</a> and a CMS Critic contributor.

Exploring DX Architecture

mattmcqueeny

Explore a wide range of informative articles on Contributor, 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

Reflections on CMS Kickoff 25 from ‘The AEM Guy’

Roadmap to Digital Experience Success: Six Ways to Future-Proof Your CMS While Elevating Your Tech Teams

Exploring DX Architecture