01Managed Static WordPress
Keep the CMS. Separate the public website.
Continue creating and editing content in WordPress while a publishing process delivers static pages to visitors. This can work well for marketing sites, informational websites, and organizations that need familiar editing tools without a public WordPress installation.
The setup includes decisions about when pages are generated, how changes are reviewed, what happens if a build fails, and how the private CMS is maintained.
Managed Static WordPress →
02WordPress to Static Conversion
Keep the website. Retire the CMS.
If WordPress no longer serves a useful purpose, convert the website into a standalone static implementation. I focus on preserving the design and important content, cleaning up dependencies, and establishing a practical way to make future changes.
This approach is often suitable for sites that are primarily informational and don't depend on user accounts or constantly changing data.
WordPress to Static Conversion →