Website and CMS

Content management systems provide the infrastructure for creating, editing, storing, and publishing website content. CMS platforms enable non-technical users to maintain websites without writing code, while providing developers with frameworks for building custom functionality. The platform selection affects content workflow, site performance, security posture, hosting requirements, and long-term maintenance costs.

This page covers systems designed primarily for public-facing organisational websites: informational sites, blogs, news publications, and marketing pages. The scope includes traditional coupled CMS (where content management and presentation are integrated), headless CMS (API-first content repositories), and visual site builders with CMS capabilities. E-commerce platforms, learning management systems, and internal knowledge bases are covered in separate benchmark pages. Programme management systems with public reporting features (such as donor portals) are addressed under Programme and Humanitarian Systems.

Requirements taxonomy

This taxonomy defines evaluation criteria for website and CMS tools. Requirements are organised by functional area and weighted by typical priority for mission-driven organisations. Adjust weights based on your specific operational context.

Functional requirements

Core capabilities that define what the CMS must do.

Content authoring and editing

Content organisation and structure

Multi-language and localisation

Workflow and collaboration

Design and theming

SEO and metadata

Technical requirements

Infrastructure, architecture, and deployment considerations.

Deployment and hosting

Scalability and performance

API and headless capabilities

Security requirements

Security controls and data protection capabilities.

Authentication and access control

Data protection

Security certifications and compliance

Operational requirements

Day-to-day administration and management considerations.

Administration and configuration

Monitoring and observability

Support and maintenance

Data management requirements

Data handling, portability, and lifecycle management.

Data import and migration

Data export and portability

Commercial and contractual requirements

Licensing, pricing, and vendor relationship considerations.

Pricing and licensing

Vendor assessment

Accessibility requirements

Compliance with accessibility standards.

Assessment methodology

Tools are assessed against each requirement using the following scale:

Additional notation:

• $ indicates feature requires paid tier or add-on
• E indicates feature available in enterprise tier only
• P indicates feature requires plugin or extension

Functional capability comparison

Content authoring and editing

Assessment notes:

• Strapi F1.1: Admin panel provides JSON-based content editing; visual editing requires frontend implementation or third-party editor integration
• Contentful F1.1: Rich text editor available but not WYSIWYG for final rendered output; requires preview integration
• Ghost F1.7: Editor shows formatted preview but not actual site template rendering
• Strapi F1.3: Scheduled publishing available in Pro/Enterprise plans only
• Webflow F1.4: Revision history available but limited compared to dedicated CMS; backup-based rather than per-field

Content organisation and structure

Assessment notes:

• Strapi F2.1: Relations support parent-child but no built-in hierarchical URL generation; requires custom implementation
• Ghost F2.1: Pages are flat; hierarchy through navigation menus only
• Ghost F2.3: Limited to posts and pages with tags/authors; custom fields via code injection only
• Strapi/Contentful F2.6: Headless CMS; menu structure must be implemented in frontend
• Webflow F2.2: Reference fields provide tagging; hierarchical taxonomies require workarounds

Multi-language and localisation

Assessment notes:

• WordPress F3.1-F3.4: Requires plugin (WPML or Polylang) for full multi-language support; not core functionality
• Ghost F3.1: Publication settings support multiple languages but require separate Ghost installations or custom routing
• Webflow F3.1: Localisation available on CMS plan and above with site-wide language variants

Workflow and collaboration

Assessment notes:

• Strapi F4.1-F4.2: Review workflows available in Pro and Enterprise plans only
• Contentful F4.1-F4.2: Workflows available on Team plan and above
• Ghost F4.1: Draft and published states only; no custom workflow stages
• Webflow F4.3: Real-time collaborative design; content editing collaboration more limited

Design and theming

Assessment notes:

• Strapi/Contentful F5.1-F5.4: Headless CMS; presentation layer implemented separately
• WordPress F5.4: Block editor provides some visual building; dedicated page builders (Elementor, Divi) as plugins
• Wagtail F5.4: StreamField provides structured content blocks but not drag-drop visual layout
• Webflow F5.4: Visual builder is core functionality with full layout control

SEO and metadata

Assessment notes:

• WordPress/Drupal/Joomla F6.x: Core provides basic capabilities; SEO plugins (Yoast, RankMath, SEO module) provide full feature set
• Strapi/Contentful F6.x: SEO implementation responsibility of frontend; content model can include SEO fields
• Wagtail F6.1: Built-in promote tab with SEO fields; SEO plugins available for additional features

Technical capability comparison

Deployment and hosting

Deployment requirements:

API and headless capabilities

API details:

Security capability comparison

Authentication and access control

MFA methods supported:

Data protection

Security certifications (managed hosting/SaaS)

Operational capability comparison

Administration

Localisation support:

Support comparison

Data management comparison

Import and export

Migration paths:

Commercial comparison

Pricing models

Cost comparison (illustrative, monthly):

Notes:

• Self-hosted costs exclude staff time for maintenance
• “Small org” assumes under 50 content editors, under 100k monthly visitors
• “Medium org” assumes 50-500 editors, 100k-1M monthly visitors
• Nonprofit discounts not reflected in ranges above

Vendor details

Jurisdictional considerations:

• WordPress (Automattic), Strapi, Contentful, Webflow: US-headquartered companies subject to CLOUD Act for hosted services; self-hosted deployments avoid this
• Ghost: Singapore-registered non-profit foundation; Ghost(Pro) servers in multiple regions
• Drupal, Wagtail, Joomla: Open source software with no vendor jurisdiction concerns when self-hosted

Detailed tool assessments

WordPress

Type

Open source

Licence

GPL-2.0-or-later

Current version

6.9 “Gene” (released December 2025)

Deployment options

Self-hosted (PHP/MySQL), managed hosting (numerous providers), WordPress.com SaaS

Source repository

github.com/WordPress/WordPress

Documentation

developer.wordpress.org

Overview

WordPress powers approximately 43% of websites globally, making it the dominant content management system. Originally launched as blogging software in 2003, WordPress evolved into a full CMS with the introduction of custom post types, the REST API, and the block editor (Gutenberg). The platform combines a PHP-based core with a MySQL database and templating system.

The block editor, introduced in WordPress 5.0 and continuously enhanced, provides visual content creation using modular blocks. Full Site Editing capabilities allow theme customisation through the same block interface. WordPress operates through an extensive plugin ecosystem with over 60,000 plugins in the official directory, enabling functionality from e-commerce to membership sites.

WordPress follows a predictable release schedule with major versions every 4-6 months and security updates as needed. The project is governed by the WordPress Foundation with significant contributions from Automattic (the company behind WordPress.com).

Capability assessment for website and CMS

WordPress excels at traditional website use cases where content editors need independence from developers. The block editor provides substantial visual control without code, and the mature theme ecosystem offers designs for every sector. The plugin architecture allows extending functionality without core modifications.

For mission-driven organisations, WordPress offers low technical barriers, extensive documentation, and broad hosting availability. The large user base means finding WordPress-skilled staff or contractors is straightforward. However, the plugin dependency model requires ongoing maintenance attention, and security hardening is essential given WordPress’s popularity as an attack target.

WordPress can operate headlessly through its REST API, though this was a later addition rather than core architecture. The API is comprehensive but adds complexity compared to purpose-built headless CMS platforms.

Key strengths:

• Largest ecosystem of themes, plugins, and developers globally
• Block editor provides visual editing without technical knowledge
• Extensive documentation and community support resources
• Low-cost hosting available; scales to enterprise with appropriate infrastructure
• Mature REST API for headless or hybrid deployments

Key limitations:

• Security requires ongoing attention due to platform popularity and plugin vulnerabilities
• Performance optimisation requires caching plugins and careful configuration
• Multi-language requires third-party plugins (WPML, Polylang) adding cost and complexity
• Editorial workflows require plugins; not native to core
• Plugin quality varies significantly; abandoned plugins create technical debt

Deployment and operations

Self-hosted requirements:

PHP: 7.4+ (8.2+ recommended)
Database: MySQL 5.7+ or MariaDB 10.4+
Web server: Apache with mod_rewrite or Nginx
Memory: 256MB minimum, 512MB+ recommended
Storage: 1GB minimum

Deployment complexity: Low. WordPress is designed for shared hosting environments; installation takes under 10 minutes on compatible hosting.

Operational overhead: Medium. Requires regular updates (core, themes, plugins), security monitoring, and backup management. Automated update capabilities reduce burden.

Upgrade path: Minor updates apply automatically by default. Major version updates require testing but typically have high backward compatibility. Plugin compatibility is the primary upgrade consideration.

Integration capabilities

API coverage: REST API covers posts, pages, users, media, taxonomies, comments, settings. Custom endpoints via plugins or custom code.

Authentication: Application passwords (native), OAuth 2.0 (plugin), JWT (plugin).

Key integrations:

Security assessment

Authentication: Username/password by default; MFA via plugins (Wordfence, Google Authenticator); SSO via plugins (SAML, OAuth providers).

Authorisation: Five default roles (Administrator, Editor, Author, Contributor, Subscriber) with capability system. Custom roles via plugins.

Data protection: Database encryption depends on hosting configuration. HTTPS enforced via configuration or plugin. Audit logging via plugins (WP Activity Log, Simple History).

Security track record: Frequent target due to market share. Core security is actively maintained; plugin vulnerabilities are primary attack vector. Regular security releases address disclosed vulnerabilities.

Cost analysis

Direct costs:

• Software: Free
• Plugins: Free to £200+/year per premium plugin
• Themes: Free to £50-200 one-time

Infrastructure costs (self-hosted):

Hidden costs to consider:

• Premium plugin renewals (often annual)
• Security monitoring services
• Development time for customisation
• Ongoing maintenance labour

Organisational fit

Best suited for:

• Organisations needing marketing-led website updates without developer dependency
• Small IT teams or no dedicated IT where managed WordPress hosting reduces burden
• Sites requiring extensive plugin functionality (membership, e-commerce, events)
• Organisations where WordPress skills are already present

Less suitable for:

• Highly structured content requiring strict governance (consider Drupal)
• API-first projects prioritising developer experience (consider headless CMS)
• Organisations unable to maintain regular update schedule

Migration considerations:

• Migrating to WordPress: Importers available for most major platforms
• Migrating from WordPress: Complete export via WXR format; media requires separate handling

Drupal

Type

Open source

Licence

GPL-2.0-or-later

Current version

11.3 (released January 2026); Drupal CMS 1.x distribution also available

Deployment options

Self-hosted (PHP), managed hosting (Acquia, Pantheon, Platform.sh)

Source repository

git.drupalcode.org/project/drupal

Documentation

drupal.org/docs

Overview

Drupal is an enterprise-grade CMS known for structured content, sophisticated permissions, and multi-site capabilities. Founded in 2001, Drupal powers complex websites for governments, universities, media organisations, and large NGOs. The platform emphasises content architecture, workflow governance, and developer extensibility.

Drupal 11, released in 2024, brought modernised architecture with Symfony 7 and PHP 8.3 requirements. The January 2025 release of “Drupal CMS” (formerly Starshot) provides a more accessible distribution with pre-configured functionality for non-technical users, while core Drupal remains available for custom implementations.

Drupal’s architecture separates content, configuration, and presentation more rigorously than WordPress. Content types, views, and workflows are core concepts with granular configuration. The module ecosystem, while smaller than WordPress’s plugin directory, tends toward higher complexity and enterprise use cases.

Capability assessment for website and CMS

Drupal excels where content structure, governance, and scalability are priorities. Its content type system allows precise modelling of organisational information architecture. Workflow modules (Workspaces, Content Moderation) provide staging and approval processes suitable for regulated environments.

For multi-site deployments, Drupal’s architecture supports shared codebases with per-site configuration, valuable for organisations with federated structures. The taxonomy system handles complex categorisation schemes across large content libraries.

The tradeoff is complexity. Drupal requires more technical skill to implement and maintain than WordPress or Webflow. Theme development assumes Twig templating knowledge. While Drupal CMS aims to lower the barrier, substantial customisation still demands developer involvement.

Key strengths:

• Sophisticated content modelling with custom content types, fields, and relationships
• Granular permissions system supporting complex organisational structures
• Multi-language handling native to core without third-party modules
• Workspaces module enables content staging environments
• Strong multi-site and platform capabilities

Key limitations:

• Steeper learning curve for editors and administrators
• Smaller pool of available developers compared to WordPress
• Theme development requires Twig templating knowledge
• Upgrade path between major versions historically complex (improved in recent versions)
• Fewer turnkey solutions; more custom development expected

Deployment and operations

Self-hosted requirements:

PHP: 8.1+ (8.3 recommended)
Database: MySQL 8.0+, MariaDB 10.6+, or PostgreSQL 14+
Web server: Apache or Nginx
Memory: 128MB minimum, 512MB+ recommended
Storage: 100MB minimum for core; grows with content
Composer: Required for dependency management

Deployment complexity: Medium-High. Composer-based workflow requires command-line familiarity. Acquia and Pantheon provide simplified deployment for managed hosting.

Operational overhead: Medium-High. Configuration management via YAML files enables version control but adds process complexity. Regular security updates required.

Upgrade path: Minor versions (11.1, 11.2) are designed for seamless update. Major version upgrades (10 to 11) require deprecation cleanup but are simpler than historical Drupal upgrades.

Cost analysis

Direct costs:

• Software: Free
• Enterprise modules: Some commercial modules available (£100-500/year)

Infrastructure costs (self-hosted):

Hidden costs to consider:

• Developer time (Drupal expertise premium)
• Module compatibility testing during upgrades
• Configuration management process overhead

Organisational fit

Best suited for:

• Large organisations requiring complex content governance
• Multi-site or multi-language deployments
• Government and higher education with accessibility compliance requirements
• Organisations with existing Drupal expertise

Less suitable for:

• Small organisations without developer access
• Simple brochure websites
• Projects requiring rapid deployment with minimal customisation

Wagtail

Type

Open source

Licence

BSD 3-Clause

Current version

7.0 LTS (released May 2025); 7.2 stable

Deployment options

Self-hosted (Django/Python), managed hosting (Divio, Platform.sh)

Source repository

github.com/wagtail/wagtail

Documentation

docs.wagtail.org

Overview

Wagtail is a Django-based CMS that combines developer-friendly architecture with an elegant editor interface. Originally developed by UK agency Torchbox, Wagtail is used by NASA, Google, Mozilla, and numerous non-profit organisations. The platform emphasises structured content, clean code, and accessibility.

Built on Django, Wagtail inherits Python’s ecosystem advantages: clear code organisation, strong testing frameworks, and extensive libraries. The admin interface prioritises editor experience with a clean design and logical navigation. StreamField, Wagtail’s block-based content system, allows flexible page composition without sacrificing content structure.

Wagtail follows Django’s LTS model, with Long Term Support releases receiving 18 months of security updates. The project maintains active development with quarterly feature releases.

Capability assessment for website and CMS

Wagtail bridges the gap between developer-focused frameworks and editor-focused CMS platforms. Developers get clean Django code with sensible conventions; editors get an intuitive admin interface that doesn’t require technical knowledge.

StreamField deserves particular note: it provides structured content blocks that can be reordered and nested while maintaining content model integrity. This differs from WordPress’s block editor (which stores blocks as serialised HTML) or basic text fields with WYSIWYG editors.

For mission-driven organisations, Wagtail’s accessibility focus is significant. The project maintains WCAG compliance for the admin interface and provides tooling for accessible front-end development. The strong Python/Django community offers resources for organisations with Python expertise.

Key strengths:

• Clean, accessible admin interface designed around editor workflows
• StreamField provides structured yet flexible content composition
• Django foundation offers clear architecture and testing capabilities
• Strong accessibility commitment (admin and output)
• BSD licence permits any use including proprietary modifications

Key limitations:

• Requires Django/Python development skills for implementation
• Smaller ecosystem than WordPress or Drupal; fewer pre-built solutions
• Visual page builder capabilities less developed than proprietary alternatives
• Hosting options more limited; fewer one-click deployments available

Deployment and operations

Self-hosted requirements:

Python: 3.10+
Django: 4.2+ (5.0+ recommended)
Database: PostgreSQL 12+ (recommended), MySQL 8+, SQLite
Web server: Nginx + Gunicorn or equivalent
Memory: 512MB minimum, 2GB+ recommended

Deployment complexity: Medium. Django deployment knowledge required. Platform.sh and Divio provide streamlined deployment.

Operational overhead: Low-Medium. Django’s clear architecture simplifies maintenance. Regular updates are smaller and more predictable than WordPress.

Cost analysis

Infrastructure costs (self-hosted):

Organisational fit

Best suited for:

• Organisations with Python/Django development capability
• Projects requiring clean content architecture with editorial flexibility
• Accessibility-focused deployments
• Organisations wanting to avoid PHP-based CMS platforms

Less suitable for:

• Teams without Python development resources
• Projects requiring extensive pre-built plugins
• Rapid prototyping with turnkey themes

Strapi

Type

Open source (Community Edition)

Licence

MIT (Community Edition)

Current version

5.x (released September 2024)

Deployment options

Self-hosted (Node.js), Strapi Cloud, various PaaS platforms

Source repository

github.com/strapi/strapi

Documentation

docs.strapi.io

Overview

Strapi is an open source headless CMS providing a Node.js-based content repository with REST and GraphQL APIs. The platform enables developers to define content types through an admin interface or code, then consume content via APIs in any frontend technology. Strapi v5, released in late 2024, brought TypeScript support, improved performance, and enhanced content versioning.

As a headless CMS, Strapi separates content management from presentation entirely. Content editors work in Strapi’s admin panel; developers build frontends using any framework (React, Vue, Next.js, mobile apps, etc.) that consume Strapi’s APIs. This architecture suits omnichannel content delivery and JavaScript-focused development teams.

Strapi operates on an open-core model: the Community Edition is MIT-licensed and includes core CMS functionality, while paid tiers (Pro, Enterprise) add features like review workflows, SSO, and enhanced support.

Capability assessment for website and CMS

Strapi excels when development teams need a flexible content backend without frontend constraints. The content type builder allows rapid modelling through the admin UI, generating both database schemas and API endpoints automatically. For JavaScript/TypeScript teams, Strapi integrates naturally with modern frontend tooling.

For mission-driven organisations, Strapi works well when: the organisation has frontend development capability, content will be delivered to multiple channels (web, mobile, digital signage), or there’s a desire to avoid WordPress/PHP legacy. The self-hosted option provides data control without SaaS dependency.

The primary tradeoff is that Strapi doesn’t include frontend presentation. Organisations must build or commission frontend development, adding project scope compared to traditional CMS platforms with themes.

Key strengths:

• Flexible content modelling through visual admin or code
• REST and GraphQL APIs generated automatically
• MIT licence for Community Edition with no usage restrictions
• Node.js/TypeScript architecture aligns with modern JavaScript development
• Strong self-hosted option for data sovereignty

Key limitations:

• No frontend presentation; requires separate frontend development
• Editorial workflow features require paid plans
• Smaller ecosystem than WordPress; fewer integrations
• Admin interface not designed for complex content workflows
• Breaking changes between major versions require migration effort

Deployment and operations

Self-hosted requirements:

Node.js: 18+ or 20+
Database: PostgreSQL 14+ (recommended), MySQL 8+, MariaDB, SQLite
Memory: 2GB minimum
Storage: 1GB minimum

Deployment complexity: Low-Medium. Standard Node.js deployment; Strapi Cloud provides managed option.

Operational overhead: Medium. Regular updates required; v4 to v5 migration required code changes.

Cost analysis

Direct costs:

• Community Edition: Free
• Pro: From £99/month
• Enterprise: Custom pricing

Infrastructure costs:

Organisational fit

Best suited for:

• JavaScript/TypeScript development teams
• Multi-channel content delivery projects
• Organisations wanting API-first architecture
• Projects where frontend is built by separate team

Less suitable for:

• Organisations without frontend development capability
• Simple websites where traditional CMS suffices
• Content-heavy editorial workflows without paid tier

Ghost

Type

Open source

Licence

MIT

Current version

6.x (6.12 as of January 2026)

Deployment options

Self-hosted (Node.js), Ghost(Pro) managed service

Source repository

github.com/TryGhost/Ghost

Documentation

ghost.org/docs

Overview

Ghost is a publishing platform focused on professional blogs, newsletters, and membership sites. Originally launched in 2013 as a WordPress alternative for writers, Ghost has evolved into a complete publishing ecosystem with native membership, newsletter, and monetisation features. The Ghost Foundation operates as a non-profit organisation.

Ghost’s architecture centres on publishing workflows: writing, scheduling, sending newsletters, managing subscribers, and processing payments. The editor provides distraction-free writing with keyboard shortcuts and Markdown support. Unlike WordPress’s extensible plugin architecture, Ghost focuses on core publishing features with limited but high-quality integrations.

The platform can operate as a traditional CMS (Handlebars-based themes render content) or headlessly via the Content API. Ghost(Pro) managed hosting provides a turnkey solution; self-hosting is free but requires Node.js infrastructure.

Capability assessment for website and CMS

Ghost excels specifically for publishing: blogs, newsletters, and membership publications. The writing experience is polished, and native newsletter integration eliminates the need for separate email platforms. For organisations whose primary digital presence is content publishing, Ghost provides focused functionality without CMS complexity.

For mission-driven organisations, Ghost’s nonprofit status and transparent governance align with sector values. Ghost for Nonprofits provides free hosting for qualifying organisations. The platform’s simplicity reduces maintenance burden compared to extensible CMS platforms.

Ghost’s limitations are scope-related. It’s designed for posts and pages, not complex content types. There’s no plugin system; functionality not in core requires custom theme development or external integration. Sites needing events, job boards, or complex taxonomies will find Ghost insufficient.

Key strengths:

• Excellent writing and publishing experience
• Native membership and newsletter functionality
• Clean, focused feature set without complexity
• Non-profit governance with transparent development
• Low operational overhead compared to extensible CMS

Key limitations:

• Limited to posts, pages, and tags; no custom content types
• No plugin architecture; extensibility through themes and integrations only
• Multi-language requires separate Ghost installations
• Fewer themes and customisation options than WordPress
• SEO customisation less extensive than dedicated plugins

Cost analysis

Direct costs:

• Self-hosted: Free
• Ghost(Pro) Starter: £11/month
• Ghost(Pro) Creator: £31/month
• Ghost(Pro) Team: £63/month
• Ghost(Pro) Business: £249+/month
• Ghost for Nonprofits: Free Starter plan for qualifying organisations

Organisational fit

Best suited for:

• Blog-focused or newsletter-focused communications
• Organisations wanting integrated membership/subscription
• Teams prioritising writing experience over site-building flexibility
• Nonprofits eligible for Ghost for Nonprofits programme

Less suitable for:

• Complex websites with multiple content types
• Sites requiring extensive customisation or plugins
• Multi-language publications (without separate installations)

Joomla

Type

Open source

Licence

GPL-2.0-or-later

Current version

6.0.2 (released January 2026); 5.4.2 LTS also supported

Deployment options

Self-hosted (PHP/MySQL), managed hosting (various providers)

Source repository

github.com/joomla/joomla-cms

Documentation

docs.joomla.org

Overview

Joomla is an open source CMS that occupies the middle ground between WordPress’s accessibility and Drupal’s complexity. Launched in 2005 as a fork of Mambo, Joomla is governed by Open Source Matters, Inc., a non-profit organisation. The platform powers approximately 2% of websites globally.

Joomla provides more built-in functionality than WordPress out of the box, including multi-language support, access control levels, and article versioning as core features. The extension ecosystem offers components, modules, and plugins, though the directory is smaller than WordPress’s. Joomla 5 and 6 brought modernised architecture with PHP 8 support and improved upgrade paths.

Capability assessment for website and CMS

Joomla suits organisations wanting more structure than WordPress without Drupal’s complexity. Native access control levels (viewing, editing, publishing) provide content governance without plugins. Multi-language support is built-in rather than requiring commercial plugins as with WordPress.

For mission-driven organisations, Joomla’s non-profit governance and mature feature set provide a stable foundation. The smaller community compared to WordPress means fewer resources and developers, but also less noise and more focused support.

Joomla’s market position has declined relative to WordPress, resulting in fewer new themes and extensions. Organisations should consider long-term ecosystem viability when selecting Joomla.

Key strengths:

• Native multi-language support without commercial plugins
• Granular access control built into core
• Non-profit governance structure
• More structured than WordPress; less complex than Drupal
• Large installed base with long-term support track record

Key limitations:

• Smaller community and ecosystem than WordPress
• Fewer modern themes and contemporary designs
• Finding Joomla developers can be challenging
• Market share decline raises long-term considerations
• Admin interface less polished than competitors

Organisational fit

Best suited for:

• Multi-language sites where WordPress plugin costs are prohibitive
• Organisations with existing Joomla expertise
• Sites requiring content access control without premium plugins
• Community or membership sites using built-in ACL

Less suitable for:

• New projects without specific Joomla requirements
• Teams needing access to large developer talent pool
• Projects requiring modern visual building capabilities

Contentful

Type

Commercial SaaS

Licence

Proprietary

Current version

SaaS (continuous updates)

Deployment options

SaaS only (US and EU data centres)

Source repository

N/A (proprietary)

Documentation

contentful.com/developers/docs

Overview

Contentful is an enterprise-grade headless CMS that provides content infrastructure via APIs. Founded in Berlin in 2013, Contentful has become a leading player in the enterprise headless CMS market, with customers including Spotify, Vodafone, and the British Red Cross. The platform operates entirely as SaaS with no self-hosted option.

Contentful’s architecture separates content modelling (defining content types and fields) from content delivery (APIs serving content to applications). The platform provides REST, GraphQL, and Image APIs, with SDKs for major programming languages. Content is delivered through a global CDN for performance.

The platform operates on tiered pricing: a Community tier provides limited free usage, while Team and Enterprise tiers add collaboration features, higher limits, and compliance certifications.

Capability assessment for website and CMS

Contentful excels as enterprise content infrastructure for multi-channel delivery. The content modelling capabilities are sophisticated, allowing complex relationships and localisation. The API performance (backed by CDN) suits high-traffic applications. For organisations with development resources needing robust content APIs, Contentful provides a polished solution.

For mission-driven organisations, considerations include cost (subscription fees exceed self-hosted alternatives at scale), vendor dependency (no self-hosting escape route), and jurisdiction (US-headquartered company, though EU data centres available).

Key strengths:

• Sophisticated content modelling with relationships and localisation
• High-performance API delivery via global CDN
• Polished admin interface with strong editor experience
• Extensive app marketplace for integrations
• EU data residency option available

Key limitations:

• No self-hosted option; complete vendor dependency
• Significant cost at scale; consumption-based pricing can be unpredictable
• US-headquartered company subject to CLOUD Act
• Requires frontend development; no presentation layer
• Community tier limitations (5 users, 25k records)

Cost analysis

Direct costs:

• Community: Free (5 users, 25k records, 1 space)
• Team: From £300/month (20 users)
• Enterprise: Custom pricing
• Contentful for Nonprofits: 50% discount on paid plans

Organisational fit

Best suited for:

• Enterprise organisations with frontend development capability
• Multi-channel content delivery requirements
• Projects requiring high-availability content APIs
• Organisations with budget for SaaS CMS investment

Less suitable for:

• Organisations requiring data sovereignty or self-hosting
• Small organisations or limited budgets
• Projects where traditional CMS would suffice

Webflow

Type

Commercial SaaS

Licence

Proprietary

Current version

SaaS (continuous updates)

Deployment options

SaaS only (AWS-backed hosting)

Source repository

N/A (proprietary)

Documentation

developers.webflow.com

Overview

Webflow combines visual web design tools with CMS and hosting capabilities. The platform enables designers to build responsive websites visually while generating clean HTML, CSS, and JavaScript. Launched in 2013, Webflow has grown significantly among agencies and marketing teams who want design control without traditional development workflows.

Unlike headless CMS platforms, Webflow provides integrated design and CMS capabilities. The visual Designer allows pixel-level control over layout, styling, and interactions. The CMS Collections feature enables dynamic content with a visual content modelling interface. Sites are hosted on Webflow’s AWS-backed infrastructure with global CDN.

Capability assessment for website and CMS

Webflow suits organisations prioritising design control over content structure. Marketing teams and designers can create sophisticated websites without developer involvement. The visual interface produces actual CSS (not an abstraction layer), so the output code is standards-compliant and exportable.

For mission-driven organisations, Webflow reduces dependency on developers for website updates, potentially lowering costs. The learning curve for the visual designer is substantial but results in significant team capability. Webflow for Nonprofits provides discounted pricing.

Limitations include the SaaS-only model, limited CMS capabilities compared to dedicated platforms, and the learning curve for the visual editor. Sites with complex content structures may outgrow Webflow’s CMS limitations.

Key strengths:

• Visual design control producing real CSS
• Integrated hosting with global CDN
• CMS enables dynamic content within visual design
• Interactions and animations without code
• Export option for static sites (design, not CMS)

Key limitations:

• SaaS-only; no self-hosting option
• CMS capabilities limited compared to dedicated platforms
• Significant learning curve for visual designer
• API limitations for complex integrations
• E-commerce capabilities less mature than dedicated platforms

Cost analysis

Direct costs:

• Site Plans:
  • Starter: Free (2 pages, Webflow branding)
  • Basic: £14/month (custom domain)
  • CMS: £23/month (up to 2,000 CMS items)
  • Business: £39/month (10,000 CMS items)
  • Enterprise: Custom pricing
• Webflow for Nonprofits: 50% discount

Organisational fit

Best suited for:

• Marketing-led website development without developers
• Design agencies building client sites
• Organisations wanting integrated design, CMS, and hosting
• Landing pages and marketing sites with moderate dynamic content

Less suitable for:

• Complex content management requirements
• Organisations requiring self-hosting or data sovereignty
• Sites with thousands of pages or complex relationships
• Developer-led projects preferring code control

Selection guidance

Decision framework

Use this framework to narrow options based on your constraints:

                                    START
                                      |
                                      v
                     +--------------------------------+
                     | Must data remain in your      |
                     | direct control (not SaaS)?    |
                     +---------------+----------------+
                                     |
                     +---------------+---------------+
                     |                               |
                     v                               v
                    YES                             NO
                     |                               |
                     v                               v
          +------------------+           +----------------------+
          | Self-hosted      |           | Do you have frontend |
          | options only:    |           | development capacity?|
          | WordPress        |           +----------+-----------+
          | Drupal           |                      |
          | Wagtail          |            +---------+---------+
          | Strapi           |            |                   |
          | Ghost            |            v                   v
          | Joomla           |           YES                 NO
          +------------------+            |                   |
                                          v                   v
                               +------------------+ +------------------+
                               | Consider all,    | | Traditional CMS  |
                               | including:       | | with themes:     |
                               | Strapi           | | WordPress        |
                               | Contentful       | | Ghost (Pro)      |
                               | Wagtail          | | Webflow          |
                               +------------------+ +------------------+

Figure 1: Initial filtering based on deployment and capability requirements

Recommendations by organisational context

For organisations with minimal IT capacity

Primary recommendation: WordPress with managed hosting

WordPress provides the lowest barrier to entry, largest ecosystem of pre-built solutions, and most available support options. Managed hosting (WordPress.com, WP Engine, or similar) reduces operational burden. The block editor enables content creation without technical skills, and thousands of themes provide turnkey designs.

Alternative: Webflow if design control is priority and CMS needs are moderate. Ghost if focus is publishing/newsletter and eligible for Ghost for Nonprofits.

Avoid: Self-hosted Drupal, Wagtail, or Strapi without development resources.

For organisations with established IT capacity

Primary recommendation: Depends on technical stack and requirements

• Python/Django expertise: Wagtail provides clean architecture with excellent editor experience
• JavaScript/Node.js expertise: Strapi offers flexible headless content management
• PHP expertise with complex governance needs: Drupal provides sophisticated content structures
• Multi-channel content delivery: Strapi or Contentful for API-first architecture

Alternative: WordPress remains viable with Enterprise-grade managed hosting (Acquia, WP VIP, Pantheon) providing the operational support.

For organisations with specific constraints

Strict data sovereignty requirements:

• Self-hosted options only: WordPress, Drupal, Wagtail, Strapi, Ghost, Joomla
• Avoid: Contentful, Webflow (no self-hosting option)

Multi-language without commercial plugins:

• Primary: Drupal (native multi-language), Joomla (native multi-language)
• Alternative: Wagtail, Strapi (native internationalisation)

Minimal budget:

• Primary: WordPress self-hosted, Ghost self-hosted, Joomla
• Consider: Ghost for Nonprofits (free Starter), Webflow for Nonprofits (50% discount)

Publishing and newsletter focus:

• Primary: Ghost
• Alternative: WordPress with newsletter plugin

Migration paths

External resources

Official documentation

Open source projects

Commercial products

Relevant standards

See also

• Document Management - Internal document handling beyond public websites
• Knowledge Management - Internal knowledge bases and wikis
• Intranet and Portals - Internal staff portals
• Accessibility Standards - WCAG compliance requirements