Back to work
WordPress Plugin / ProductCustom WordPress plugin product

Custom WordPress maintenance plugin

Maneuvrez Maintenance Mode Plugin

A custom WordPress maintenance/coming soon plugin with admin-controlled components, preview behavior, buttons, social links, and bypass rules.

Project summary

Built a product-style WordPress plugin that lets admins control a public maintenance page without relying on a bloated page-builder workflow.

Admin-controlled maintenance pages with preview, bypass, buttons, social links, and component visibility.

Abstract maintenance plugin settings illustration

Project summary

Plugin type

Maintenance / coming soon

Control model

Admin-managed components

Built a product-style WordPress plugin that lets admins control a public maintenance page without relying on a bloated page-builder workflow.

Buyer-facing summary

Client problem

A maintenance page often needs more than one static screen: preview behavior, login visibility, buttons, social links, and configurable sections.

What I delivered

I built a custom WordPress plugin with admin settings, frontend rendering, component visibility, bypass behavior, and safe request handling.

Business result

The plugin gives site owners a reusable maintenance workflow without turning routine maintenance into a page-builder project.

Problem

A maintenance page sounds simple until it is used on a real site. Owners need control over copy, buttons, social links, login visibility, and preview behavior while the site is under work.

The goal for Maneuvrez was to build a plugin that felt like a small product: clear admin controls, predictable frontend rendering, and safe bypass behavior.

The plugin needed safe defaults so owners would not accidentally block the wrong requests or lock themselves out.
The public page needed to be configurable without becoming cluttered or difficult to maintain.

What I built

Admin settings and component controls

Built settings that let admins control maintenance mode, page components, social links, custom buttons, and login button visibility.

Frontend maintenance rendering

Rendered a public maintenance/coming soon page through the plugin so the site can present a clean temporary experience without editing theme templates.

Preview and bypass behavior

Added behavior for safe review and admin access, keeping maintenance mode useful without surprising the owner during active work.

Admin-controlled maintenance settingsPublic maintenance/coming soon renderingSocial links and custom buttonsLogin button visibility controlsComponent visibility controlsPreview and bypass behavior

Technical decisions

WordPress hooks control when the maintenance page appears, while bypass and preview behavior preserve safe review paths.
Admin settings are treated as product controls, not just raw fields, so each public component can be enabled or hidden intentionally.
Login button visibility and safe access behavior are part of the plugin workflow rather than afterthoughts.

The hard part was making behavior predictable. A maintenance plugin should not create odd request edge cases or make it difficult for legitimate users to access the site.

I kept the plugin architecture focused on explicit settings and frontend behavior instead of tying the feature to a specific theme or page-builder layout.

Outcome

The plugin became a reusable base for maintenance and coming soon pages.
It demonstrates custom plugin architecture, admin UX, settings management, frontend rendering, feature flags, and product-level planning.

What I would improve

The next improvement would be adding stronger import/export or template presets once the core behavior is stable.

I would avoid adding design options too early; maintenance plugins become hard to use when every visual detail turns into another setting.

Tech stack

WordPressPHPAdmin SettingsFrontend RenderingBypass Rules

Next step

If you need similar work, let’s talk through the constraints first.

The useful part of a project like this usually starts before code: understanding what the CMS should own, what should live in a backend service, and where integrations or automation can stay maintainable.

Start a conversation