How to Choose the Right CMS for Your Website
The podcast emphasizes that there is no universally 'best' CMS; instead, the right choice should hinge on critical questions regarding a project's specific requirements. Seven essential questions are outlined to guide CMS selection, addressing aspects such as website management, frequency of updates, and custom functionality.
Summary
In the episode, the hosts discuss the complexities surrounding the selection of a Content Management System (CMS) for a website. They argue that the question of which CMS is 'best' is misguided; rather, the focus should be on what questions need to be asked to identify the right CMS for a particular use case. The hosts introduce a framework of seven key questions to assist in determining the appropriate CMS for different projects, highlighting that every CMS comes with its compromises and is suitable for specific situations.
The discussion includes considerations for who will update the website, how often updates will occur, and the type of site being created. The hosts note the significance of knowing the budget and the longevity expected from the CMS. Custom functionality and who will maintain the website also play critical roles in the decision-making process. Furthermore, they explore how the expected lifespan of a website can drastically alter the choice of CMS, particularly for businesses with rapidly changing needs versus those with long-standing content. The episode encapsulates the nuanced considerations involved in CMS selection, emphasizing problem-solving over platform loyalty.
About this episode
How do you choose the right CMS for a website? Matt and Mike share the framework they use to evaluate content management systems by considering factors like project type, editor experience, budget, maintenance, customization, and long-term goals. They also discuss where WordPress, Webflow, Shopify, and headless CMSs fit - and why asking the right questions is more important than picking a favorite platform.
Key Insights
- The speaker emphasizes that asking the right questions is more crucial than determining the best CMS.
- Every CMS is a compromise and no platform universally solves all problems.
- Understanding who will update the website is essential, as different users will interact with the CMS in varied ways.
- The frequency of updates needed for the website significantly influences the choice of CMS.
- The type of website—be it a brochure, blog, or e-commerce site—greatly affects which CMS should be utilized.
- Budget considerations play a vital role in the decision-making process, impacting everything from hosting to plugins.
- A website designed to last long should allow for easy updates to address evolving business needs.
- Custom functionality requirements can dictate the choice of CMS, as some systems handle unique functionality better than others.
- The speaker recounts a critical experience of a website needing rapid updates that led to reconsidering their CMS choice.
- The speaker discusses the challenge of integrating third-party services with a CMS and the implications for site management.
- Longevity expectations for a website can lead to different CMS recommendations based on the anticipated frequency of updates.
- The discussion outlines the importance of maintaining the website post-launch to prevent operational issues.
Topics
Transcript
People often ask what is the best CMS, but actually that's the wrong question. The better question is what questions should you ask before choosing a CMS? Because if you ask the right questions, the right CMS oftentimes will choose itself. So today we're going to be walking through the framework that we use before recommending something like a WordPress or Webflow, Shopify, a headless CMS, or maybe no CMS at all, or even a different CMS, because there's lots of CMSs out there. So if this sounds interesting to you and you want to support the show, you can go and check us out on that Patreon, leave a review or rating on your podcast app, join us in…
Full transcript available for MurmurCast members
Sign Up to AccessMore from HTML All The Things - Web Development, AI, and Developer Careers
Do You Actually Own Your Digital Games?
A Brazilian Xbox player won a court case against Microsoft after his account was hacked and permanently suspended, resulting in loss of his entire digital game library and OneDrive files. The hosts discuss this as a potential win for digital ownership rights and explore broader concerns about account security, digital preservation, and the nature of licensing versus ownership in digital storefronts.
AI Coding Makes Development Easier - So Why Are We Burning Out?
Hosts discuss how AI coding tools, while making development easier, are paradoxically causing burnout by eliminating the struggle-and-satisfaction cycle that previously sustained developer motivation. They explore the psychological toll of AI-assisted work where accomplishment feels hollow and recommend finding personal projects and adjusting workflows to maintain job satisfaction.
Kimi K3 Brings Frontier AI Into the Open
Kimi K3, a new 3 trillion parameter open-source AI model, represents a major advancement in frontier AI that rivals closed-source models like GPT-5.6 and Claude Opus. While offering exciting possibilities for corporations to run powerful AI locally without subscription costs, it poses significant safety risks by allowing malicious actors and state entities to deploy unrestricted AI systems without safety guardrails.
JavaScript Isn't Always the Answer: Native Browser Features Every Developer Should Know
This episode discusses how modern browsers have evolved to handle features that previously required JavaScript or Flash, such as form validation, accordions, dialogs, popovers, and responsive images. The hosts argue for using native browser APIs and semantic HTML instead of over-engineering with JavaScript, which reduces code complexity, improves performance, and enhances accessibility.
Growing Your App: From MVP to MLP
The episode discusses the distinction between MVP (Minimum Viable Product) and MLP (Minimal Lovable Product), using a golf score-tracking app as a case study. The hosts argue that building too many features due to AI-enabled development can complicate products unnecessarily, and emphasize the importance of user feedback, gut instinct, and resilience when determining what features actually make a product worth using.