| The foundation | A content management system with themes, plugins, and a dashboard. | A custom React interface with Vite handling development and production builds. | A React framework for multiple pages, prebuilt content, and server features. |
| Editing your content | Page, post, and media editing are built in. | An editor or CMS is connected where scoped, or you request edits through care. | An editor or CMS is connected where scoped, or you request edits through care. |
| Forms, bookings + stores | Plugins and services extend the site. Configuration and licenses still matter. | Features are built or connected to services within the agreed scope. | Features are built or connected to services. Server features need compatible hosting. |
| Hosting requirements | Normally needs PHP and a database, with managed or self-hosted options. | Built files can use static hosting. Forms and live data may use separate services. | Static hosting for an exported site; a server runtime for dynamic features. |
| Speed + search visibility | Hosting, plugins, images, and caching affect speed. WordPress can be optimized. | A basic React app renders in the browser. Prerendering and search metadata need planning. | Supports prebuilt or server-rendered page HTML. Images, scripts, and metadata still need attention. |
| Ongoing maintenance | Core, themes, plugins, hosting, and backups need care. | Code dependencies, hosting, connected services, and backups need care. | Code dependencies, hosting, connected services, and any server runtime need care. |
| Moving providers later | Open source and movable between compatible hosts. Plugin and service dependencies remain. | Source and built files can move. Connected services have their own requirements. | Source can move. The features used determine which hosts can run the site. |