Compare website platforms

Editors create posts and pages with blocks. The theme and any additional blocks determine the available layout and content options.

Store staff manage products and add pages and blog posts in the admin. Themes provide the storefront layout and its editable sections.

The project needs a chosen or developed editing interface. An administration tool such as Laravel Nova can manage application data; agree the editorial workflow separately.

Editors manage pages, block content and publishing in a CMS interface. Page types and fields are defined for the project; moderation workflows can be configured.

Add a commerce solution such as WooCommerce for products, orders, payments and shipping. The store configuration and extensions become part of the project to maintain.

Commerce is central to the service, with a product catalogue, inventory and store administration. Confirm the checkout, payment, shipping and app requirements for your market.

Develop or integrate the catalogue, checkout and order workflow your application needs. Cashier supports Stripe billing and subscriptions; it is one component of a commerce project.

Ecommerce is not included in the CMS itself. Integrate a Django commerce solution or an external service, and plan how content, products and orders connect.

Extend the CMS through plugins, custom content types and hooks. For unusual business processes, assess the development and plugin dependencies the solution would introduce.

Extend the store with apps, platform APIs and a custom storefront. Check whether the required workflow can use the available commerce APIs before committing to it.

An application framework for building your own workflows, data models and interfaces. Its database, queue and testing tools provide foundations; the project team develops the actual features.

Combine a content management system with a Django application. It can be added to an existing Django project when editorial content and custom application features need to work together.

Arrange hosting and agree who owns backups, WordPress updates and plugin/theme compatibility. Managed hosting can take on some tasks; confirm exactly what its service covers.

Hosting is included for a Shopify-hosted store. Your team still manages the store configuration and its apps; a separately built application or storefront needs its own deployment plan.

Choose a deployment or managed hosting service. Agree ownership of application updates, dependencies, backups and monitoring alongside the hosting provider’s responsibilities.

Choose a Wagtail provider, a Python hosting service or your own infrastructure. The level of managed service varies; agree who maintains the application and its data.

Use plugins and server-side code, or the REST API for posts, pages and other content. Check authentication, data ownership and support for each connected service.

Use commerce APIs, apps and webhooks. Storefront APIs serve customer-facing experiences; admin integrations handle store data. Match the API and access permissions to the task.

Build application endpoints and connect to other services in code. Its HTTP client supports outgoing API requests; plan authentication, retries and ongoing integration maintenance.

Use Wagtail content APIs and custom Django integration code. Choose the API version and authentication for the read or write operations your application requires.