Managed publishing
Keep WordPress. Publish a Static Website.
Continue working in the WordPress dashboard while visitors receive prebuilt pages from a separate public website. StaticMax handles the technical setup between the two.
- 01WordPressPrivate content editing
- 02Static publishingGenerate, check, deploy
- 03Your public websitePrebuilt pages for visitors
WordPress for editing. Static files for visitors.
WordPress is a useful content management system. You can organize pages and posts, work with custom fields, and let people update the site without editing code. It doesn't always need to be responsible for serving the public website, too.
With managed static publishing, WordPress remains the place where content is created. A publishing process generates the pages and assets that visitors receive. The public site can then be deployed to static hosting without exposing the WordPress login or database there.
This separation is especially useful when content editors need WordPress, but the public website is primarily informational.
How updates reach the public site
Edit in WordPress
Content editors continue using the WordPress dashboard and the editing tools appropriate to the site. Existing content structures can often be retained, although some plugins and dynamic blocks may need adjustments.
Generate and review
When changes are ready, a build generates the static website. Depending on the project, this can be triggered manually, on publication, or through an agreed schedule. The output is checked for missing files and other issues before deployment.
Publish the new version
The finished files are deployed to the public hosting environment. A defined deployment process can help prevent a failed build from replacing a working website.
Where managed static WordPress works best
This approach is worth considering for business websites, organizational sites, blogs, documentation, and content libraries where most visitors read public pages without signing in.
It is a less natural fit for websites whose public pages depend heavily on logged-in users, real-time inventory, custom checkout flows, or server-side personalization. Those features may call for a hybrid architecture instead.
What happens to plugins and forms?
Plugins that help manage content inside WordPress may continue to be useful. Plugins that expect to run PHP or WordPress AJAX requests for public visitors will not necessarily work on the static version.
Forms, search, filters, and integrations need to be evaluated one by one. Where appropriate, I can connect them to separate services or custom endpoints rather than keeping WordPress publicly accessible simply to support one feature.
WordPress still needs maintenance
Keeping WordPress private reduces exposure on the public website, but it does not make the CMS maintenance-free. WordPress, themes, plugins, accounts, backups, and the environment used for editing still need attention. Managed publishing should make responsibilities clearer, not hide them.
A publishing workflow built around your team
Some clients want to publish immediately after an edit. Others prefer preview and approval before a new version goes live. The right workflow depends on how often the website changes and who is responsible for updates.
StaticMax can assess the current setup, implement the publishing process, and provide ongoing technical support.
Common questions
Can I continue using the WordPress block editor?
Often, yes. The important question is whether the resulting frontend content and any associated scripts work properly when exported. That is checked during the assessment.
Does every WordPress update publish automatically?
Not unless that workflow is configured. Builds can be automatic or manual, with optional checks or approval stages based on the project.
Is this the same as headless WordPress?
They're related, but not identical. A headless website can render content dynamically through an API. Managed static publishing generates finished pages ahead of time so visitors do not need WordPress to render each request.
A sensible place to start
Start with the website you have.
Send your website address and a little about what you need. I’ll review the options and help you choose a practical way forward.