To choose a CMS, start from the content to publish, the functions expected and the people who will keep the site alive: Webflow serves brand sites and marketing pages; WordPress handles catalogues, online booking and large editorial volumes, provided someone takes on technical maintenance and governance; WooCommerce comes on top when the site sells or takes bookings. A platform that publishes articles and a shop that manages availability do not call for the same trade-offs.
Choose the solution your team will be able to publish with, run and evolve, with responsibilities set from the start.
Which CMS to choose for your project?
Choose Webflow for a showcase site driven by communications, WordPress for extensive editorial publishing; look at WooCommerce as soon as the site sells or takes bookings.
| Criterion and option | What to examine | Proof to ask for | Warning sign |
|---|---|---|---|
| Autonomy: Webflow | CMS collections, reusable components and marketing pages to publish without a developer | A page published by your team, with your content | Every change, even to text, depends on the provider |
| Content: WordPress | Editorial organisation, chosen plugins and maintenance load | A demo run with your content and your approval roles | No one identified for technical updates |
| Commerce: WooCommerce | Catalogue, orders, payment and availability management | A sales or booking journey run end to end | Day-to-day order management missing from the proposed scope |
Compare tasks completed, not feature lists. The demo uses your content, on the operations your team will actually carry out.
No solution wins in the abstract: it all depends on the project and the resources that will keep it alive.
What a CMS does: the main families
A CMS organises content and its publication on a site: you enter information in an admin interface, then that content feeds pages designed to display it.
Separating content from its presentation is decided at the design stage. A news item has a title, a body and an image; how it is displayed depends on the page template. When these fields have clear names, the editorial team knows what it is editing without rebuilding the page.
The traditional model brings editorial management and site building together in a single environment. WordPress represents it here. Its plugins cover a wide range of functions; you still have to decide who maintains the whole and who has the final say when someone wants to add one.
The visual builder with a built-in CMS combines page composition with structured content. Webflow relies on classes for the design system and on collections for content, hosting included. You then have to tell apart the changes that are publishing from those that touch the design of the site.
The headless model separates content management from the interface that presents it. For your decision, look above all at how the roles are split: who prepares the content, who develops its display, who maintains the link between the two? The project has to provide someone for each.
Choose the family according to where the content is going. Preparing marketing pages and evolving an application do not raise the same needs. Headless development is justified when the separation meets a real use; choosing it for a hypothetical future adds technical complexity with no defined use.
Ask to see where your team will write, where it will preview and who will step in when a page template has to change.
The criteria that really make the difference
What separates CMS options is editorial autonomy, the split of technical responsibilities and the ability to evolve the design, far more than the length of their feature list.
Start with everyday tasks: replace a visual, publish a news item, correct a piece of information or prepare a campaign page. For each one, note who handles it and how far that person can go alone. Knowing how to edit text does not mean knowing how to create a new page structure.
To judge design freedom, start from your journeys; interfaces are signed off after research, wireframes, mock-ups, prototyping and testing. Have them designed by the team that will build them: layout choices then meet production constraints before delivery. Web design work has to take the chosen CMS into account.
For integrations, describe the information that comes into the site and the information that goes out. An announced connection is not enough: ask which operation it covers, who handles errors and who maintains it.
Security counts from the selection stage. In its guide to the secure implementation of a CMS, ANSSI, the French national cybersecurity agency, recommends assessing the available offers against security criteria and keeping plugins and themes to the strict minimum, choosing ones that are actively maintained.
Comparing solutions without ranking them
WordPress, Webflow and WooCommerce do not meet the same needs: compare them on how the site will work after delivery and on the responsibilities your team is willing to take on.
WordPress is free and open source. Its extensibility suits sites that combine editorial publishing with features added through plugins. That flexibility is paid for in governance: each plugin, its upkeep and each technical change need an owner. A team with no one for this work should build support into its choice.
Webflow brings together visual building, a CMS and hosting. The studio chooses it when the client team has to publish on its own after delivery. The decision comes down to how content models and components fit with the people who publish, more than to how the site looks.
For a marketing site of this kind, ask for the delivery to include named collections, reusable components and documentation. Editorial autonomy is checked with the client team; the name of the platform does not guarantee it.
WooCommerce enters the comparison when the site has to sell or manage bookings. Assess the catalogue and the checkout flow with the people who will run the service. An e-commerce platform is judged on those operations; how easy it is to build a home page says nothing about day-to-day management.
A headless architecture calls for a different review: content management and the developed interface each need a scope and an owner. Without a specific use that requires it, the choice is hard to defend.
The head-to-head between the two publishing tools has its own article, our detailed comparison of Webflow and WordPress. Here, the choice starts from the type of site, how it is run and how much time the team has.
Which CMS for which type of project?
A brand site puts composition and publishing first, a shop commercial management, a media outlet editorial organisation and a SaaS product consistency between interfaces and features.
For a showcase site, Webflow fits projects that need a design system and marketing pages fed by an editorial team. List the expected content and functions all the same: as soon as the site has to handle more than presentation and publishing, those needs enter the study.
For e-commerce, describe the catalogue, the order process, payment and availability. Three routes are worth comparing: WordPress with WooCommerce, a dedicated e-commerce platform and a custom-built platform. It all depends on the operations to cover, because selling a product and booking a service are not managed the same way.
When content is at the heart of the project, WordPress deserves study, technical maintenance and governance included. If the editorial activity supports a marketing site, look instead at the quality of the content model and the ease of publishing.
A SaaS or a platform calls for separating the marketing site from the product: the CMS that presents the offer does not decide the application’s architecture. Components, journeys and identity should nonetheless stay consistent from one interface to the next.
A SaaS marketing site changes at the pace of launches, the product at the pace of releases. A CMS that lets marketing publish without waiting for a product deployment avoids tying the two calendars together; check this before choosing one solution for both.
The team and the content lifecycle
A communications team needs to organise how pages are created and approved; a SaaS founding team also has to split changes between marketing, design and product development.
In a group, a page can go from its author to an approver before publication. Describe that circuit with the people who live it, then judge the CMS on the rights required, how content is prepared and whether it can tell an editorial correction from a structural change.
In a founding team, the same person may write a page and then change a feature of the product. Keep content requests and development requests apart all the same, or one kind ends up handled as the other.
For a multilingual organisation, take a real piece of content and describe its journey: writing, translation, approval, then updates. Ask what happens when the source text changes, and have it shown for the planned languages: a general promise proves nothing.
With several user roles, list the permitted actions and the visible information for each one. Managing an order does not require being able to change the site’s design; that separation is settled with the operations and security teams.
On Astore, the purchasing platform the studio built for the Accor group’s procurement entity, catalogue needs vary with the type of hotel. For a project of this kind, examine the catalogue content and the operations given to each role, without copying another platform’s organisation onto yours.
The ANSSI guide mentioned above recommends multi-factor authentication for the site’s functional administrators. It also asks you to check that the CMS is compatible with its recommendations on the lifecycle of authentication factors, limiting login attempts and keeping error messages harmless. Go through these points with the person who manages access.
That leaves the documentation: it names the content models and reusable components, so that a team taking over the site knows where to work and when to call in a developer.
Assessing the total cost over time
The cost of a CMS covers design, production and running: compare these items separately before choosing a subscription or a launch quote.
Design covers journeys, interfaces and content models. Its scope depends on the number of genuinely different pages, the components to create and the functions to integrate. Have the deliverables listed: mock-ups, development, documentation, editorial support.
Running costs are everything that keeps costing money after delivery. With Webflow, hosting is included, but the work of evolving the site is not. For WordPress, go through hosting, plugins and technical maintenance with the provider: free software tells you nothing about the cost of the project.
A migration needs its own scope: which content will be carried over, which models will be rebuilt and which parts of the functionality will change? Do not compare a new build with no content migration against a redesign that has to preserve an existing site.
Functions weigh on the budget too. A shop, a booking system or an interface for several roles adds operations to design, test and maintain. The quote should name them rather than fold them into a general development line.
For the same project, mad.studio can scope different levels of deliverables depending on budget and ambition. Ask what changes from one scope to the next: components delivered, functions included, documentation, support. A price difference should match an identifiable difference in work.
Estimate the cost of maintaining a website separately from the launch. Also have the handling of change requests spelled out: a fix, a new page and a new feature do not involve the same work.
Planning for growth and keeping an exit door
Plan how the site will evolve from known needs (new content, languages, integrations, product features) and check the handover conditions along the way.
Ask what happens when the site takes on a new family of content. Does the model already exist, do you need to create a component or change the structure? The answer tells you whether the change is a matter of publishing or a new project.
For portability, start from what you would need to change provider or platform: the content recovery format, the files handed over, the access transferred, the elements to rebuild. A data export does not settle a handover on its own.
List the dependencies as well (plugins, hosting, specific developments, upkeep skills) and, for each one, its current owner and the conditions for transferring it to another team.
If new markets are on the horizon, check the languages and the editorial organisation they will require; have the scenario demonstrated rather than taking a capability on trust.
If the project already involves a change of platform, the migration from WordPress to Webflow is a separate study. Before choosing the CMS, establish what you want to keep and what you accept to rebuild.
The verdict, profile by profile
The method above is there to settle the choice; here are the default directions it leads to, to be tested against your own constraints.
- Brand site and campaign pages, self-sufficient marketing team: a visual builder with a built-in CMS, Webflow first.
- Media, high-volume blog, several authors and an approval circuit: a traditional CMS with an established editorial base, WordPress for example, with its author, editor and administrator roles.
- Online sales at the heart of the project: a dedicated e-commerce platform, not a general-purpose CMS that you keep extending.
- Content shared between a site, an app and another channel: a headless CMS, with a separately developed front end.
- Corporate site that changes twice a year: the simplest CMS the team can open without training.
- Regulatory constraints or mandatory hosting: start from the hosting constraint, it rules out part of the solutions straight away.
The questions to ask before choosing a solution
Copy these questions into your selection brief or your exchange with the provider, and ask for a demo for every answer that affects your daily operations.
- Which content and pages will our team be able to create or edit alone after delivery, and which work will remain reserved for development?
- How will the CMS handle our review circuit before publication, and how many administrator accounts will be opened, in whose name?
- Who will design the interfaces and who will put them into production? How will the components be documented for future pages or views?
- Which integrations are included, what information will they exchange and who will be responsible for errors or changes in how they work?
- Which items fall under the subscription, hosting, plugins, maintenance or additional support?
- Which content, files and access will we be able to recover if we change provider or CMS, and which elements will have to be rebuilt?
- How will adding a language, a content model or a feature be handled, and how will these changes be priced?
- What documentation and support are planned so that the people who publish can take the site over without depending on the provider’s memory?
Which CMS to choose for a blog?
For a blog, study WordPress when editorial publishing takes centre stage; look at Webflow when the articles are part of a showcase or marketing site already organised around CMS collections.
Start with the article model: what information each post contains, which of it the author fills in, which the design displays on its own. A title, an author, a category or a visual should each serve a purpose; a template including them is no reason to keep them.
If your team publishes news, long-form features and interviews, bring an example of each to the demo. Watch how the CMS handles their differences and note what requires technical work.
Editorial work does not stop once an article is created. Ask how you find content that needs correcting, how you prepare a publication and how you rework a text that has already been approved: the interface should fit the writers’ real work.
For an existing blog, review the content migration before choosing the future model. Older articles, their categories and their media may need separate handling. Work on the site structure then helps decide how readers will find the posts and how the sections will be organised.
Before deciding, have that content published by its future author, using only the planned documentation. Judge the CMS on that work rather than on a page the provider prepared in advance.
The answers below start from the type of site, the tasks given to your team and the resources available to maintain the solution.