{"id":1802,"date":"2026-10-29T13:14:35","date_gmt":"2026-10-29T12:14:35","guid":{"rendered":"https:\/\/cms.fauves.agency\/?p=1802"},"modified":"2026-10-29T14:01:48","modified_gmt":"2026-10-29T13:01:48","slug":"how-to-choose-a-cms","status":"publish","type":"post","link":"https:\/\/cms.fauves.agency\/en\/index.php\/2026\/10\/29\/how-to-choose-a-cms\/","title":{"rendered":"How to choose a CMS without making your website heavier"},"content":{"rendered":"<p>To choose a CMS without making your website heavier, start with the way your team actually works.<\/p>\n<p>Choosing a CMS is often treated as a technical decision. It is not only that.<\/p>\n<p>A content management system affects who can update the website, how content is structured, what can be maintained internally and how much technical complexity the organisation takes on over time.<\/p>\n<p>That is why the right question is not \u201cWhich CMS is best?\u201d It is \u201cWhich CMS fits the way this organisation needs to work?\u201d<\/p>\n<h2>Choose a CMS by starting with the people who will use it<\/h2>\n<p>Before comparing platforms, look at the editorial reality. Who will publish content? How often will they do it? Are they comfortable working with structured fields, or do they need a very simple interface? Does the team need to create new types of content, or mainly update existing pages?<\/p>\n<p>A CMS should make these tasks clearer, not introduce a new technical responsibility for the people who use it.<\/p>\n<p>For many organisations, <a href=\"\/en\/blog\/wordpress-astro-build-better-websites\/\">WordPress remains a sensible choice<\/a> because it is familiar and flexible. It can support pages, articles, projects, services and custom content models without requiring the whole team to learn a new environment.<\/p>\n<h2>Do not confuse content freedom with layout freedom<\/h2>\n<p>There is a difference between being able to update content and being able to redesign a page.<\/p>\n<p>Most clients need to change titles, text, images, links and structured information. They may also need to add an article, a case study or a team member. These are editorial tasks.<\/p>\n<p>Giving every editor <a href=\"\/en\/blog\/when-wordpress-becomes-a-bottleneck\/\">unrestricted layout control<\/a> can look empowering, but it can also make a website harder to keep consistent. The visual system slowly shifts. Components are used in unintended ways. Important pages lose the structure that made them easy to read.<\/p>\n<p>A good CMS setup gives people the freedom they need while protecting the parts that should remain coherent.<\/p>\n<h2>Define the content model before selecting plugins<\/h2>\n<p>Many websites become complex because the content model is never made explicit. A new need appears, a plugin is installed, then another exception is added later.<\/p>\n<p>It is usually better to begin with the recurring content types. What does the organisation need to manage repeatedly? Services, projects, people, articles, events, locations, resources or testimonials?<\/p>\n<p>Once this is clear, those things can be represented as structured content. That makes editing easier and gives the frontend reliable information to work with.<\/p>\n<h2>Consider the public website separately<\/h2>\n<p>A CMS is the place where content is managed. It does not have to dictate how every public page is delivered.<\/p>\n<p>In a <a href=\"\/en\/blog\/separate-cms-from-public-website\/\">headless setup<\/a>, WordPress can remain the editorial backend while a dedicated frontend such as Astro handles the website itself. This is useful when performance, visual precision, multilingual delivery or long-term frontend control are important.<\/p>\n<p>It allows us to preserve a familiar CMS without forcing the public website to carry the full technical weight of the backend, theme and page-builder layer.<\/p>\n<h2>Ask practical questions before making a decision<\/h2>\n<ul>\n<li>Who needs to edit the website and what do they need to change?<\/li>\n<li>Which content should be structured rather than created as one-off pages?<\/li>\n<li>Which integrations are essential and which are only nice to have?<\/li>\n<li>Does the website need to support several languages?<\/li>\n<li>Which parts need to be dynamic in real time?<\/li>\n<li>How will the system remain understandable after launch?<\/li>\n<\/ul>\n<p>These questions lead to better decisions than choosing a platform because it is familiar, fashionable or recommended in a generic comparison article.<\/p>\n<h2>The CMS should serve the website, not burden it<\/h2>\n<p>The goal is not to use the newest tool or build the most technical stack. The goal is to give the organisation a dependable editorial system and a website that remains clear, fast and maintainable.<\/p>\n<p>For many projects, that means keeping WordPress for content management and using a separate frontend for the public experience. For others, a simpler setup may be enough.<\/p>\n<p>What matters is that the technology supports the work. It should help the team manage content, help visitors understand the organisation and give the website room to evolve without becoming unnecessarily heavy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The best CMS is not the most fashionable one. It is the one that fits your content, your team and the website you need to maintain.<\/p>\n","protected":false},"author":1,"featured_media":1837,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[105],"tags":[],"class_list":["post-1802","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-experience"],"acf":{"related_posts":"","selected_cta_key":""},"rank_math_meta":{"rank_math_seo_score":"67","rank_math_title":"Choose a CMS without making your website heavier","rank_math_description":"Choose a CMS without making your website heavier: balance content autonomy, clarity and performance.","rank_math_focus_keyword":"choose a CMS"},"selected_cta":[],"wpml_current_locale":"en_US","wpml_translations":{"fr_FR":{"locale":"fr_FR","id":1814,"slug":"comment-choisir-un-cms-sans-alourdir-votre-site-web","post_title":"Comment choisir un CMS sans alourdir votre site web","href":"https:\/\/cms.fauves.agency\/index.php\/2026\/10\/29\/comment-choisir-un-cms-sans-alourdir-votre-site-web\/"}},"_links":{"self":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1802?lang=en"}],"collection":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts?lang=en"}],"about":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/types\/post?lang=en"}],"author":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/users\/1?lang=en"}],"replies":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/comments?lang=en&post=1802"}],"version-history":[{"count":4,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1802\/revisions?lang=en"}],"predecessor-version":[{"id":1923,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/posts\/1802\/revisions\/1923?lang=en"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/media\/1837?lang=en"}],"wp:attachment":[{"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/media?lang=en&parent=1802"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/categories?lang=en&post=1802"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms.fauves.agency\/index.php\/wp-json\/wp\/v2\/tags?lang=en&post=1802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}