WordPress
Consider it when people need to publish and edit pages or articles using a CMS. Plan for hosting, updates, backups, security and careful plugin choices.
Website platform comparison
There is no best platform for every business. Compare the trade-offs, then use the scenario picker to create a shortlist that fits your site’s actual needs.
What are you building?
Scenario-based shortlist
Content-led business website
The shortlist is guidance, not an automatic technical audit. Hosting, subscriptions, extensions, development scope and team skills can change the right choice.
Compare the options
The table describes typical responsibilities. A particular build can differ based on its theme, apps, plugins, APIs and custom code.
| Decision factor | WordPress | Shopify | WooCommerce | Custom PHP | React-based |
|---|---|---|---|---|---|
| Typical fit | Business websites, publishing and content-led sites | Hosted online stores and product commerce | WordPress sites that need a configurable store | Bespoke websites, portals and server-side workflows | Interactive app-like user interfaces |
| Content editing | Built-in CMS; editing experience depends on theme and plugins | Built-in store and page content management | WordPress editor plus product/catalogue management | An admin/CMS must be selected or built if editors need one | Usually needs a CMS or backend to manage changing content |
| E-commerce | Possible through commerce plugins; setup and upkeep vary | Commerce is the core product; platform manages much of the store infrastructure | Commerce plugin with a broad WordPress extension ecosystem | Can be tailored, but checkout, order and payment flows need implementation | Frontend alone is not a complete store; connect a commerce backend |
| Custom workflows | Plugins or custom development; plugin constraints apply | Apps and platform APIs; platform rules still apply | Flexible through extensions and development; compatibility needs care | Direct control over server-side behavior, with more work to build and maintain | Strong for interactive UI; business logic and data still need a backend |
| Hosting and upkeep | Owner or host typically manages hosting, updates, backups and security | Hosted service reduces server administration; store settings and apps still need care | Owner or host manages WordPress hosting, updates, backups and plugin compatibility | Hosting, updates, backups, security and monitoring need an owner | Frontend hosting is only one part; APIs, CMS and services also need upkeep |
| Main trade-off | Broad ecosystem and flexibility, with plugin and maintenance decisions | Convenient commerce tooling, with platform and app constraints | Control inside WordPress, with more hosting and extension responsibility | Purpose-built control, with more bespoke development responsibility | Flexible UI, but not a turnkey CMS, store or backend |
Shopify
Consider it when a business primarily needs an online store and prefers a managed commerce platform. Check its plan, app and customization fit before committing.
WooCommerce
Consider it when a store needs to work closely with WordPress content and the owner can manage, or arrange, hosting and extension maintenance.
Custom PHP
Consider it when specific server-side workflows justify a tailored build. Define who maintains the code, admin tools, security and backups.
React-based development
Consider it for app-like interactions. Treat React as a frontend technology; identify the API, data store, CMS or commerce service needed alongside it.
Decision guide: start with the content editors, checkout needs, custom workflows, ownership of ongoing maintenance and integrations. Compare the full cost and responsibility of running the chosen setup—not just the initial build.
