WordPress Plugin / ProductCustom WordPress plugin product

Published WordPress maintenance plugin

Maneuvrez Maintenance Studio

An open-source WordPress maintenance and coming-soon plugin with configurable content, design controls, contact channels, social links, and safe access behavior.

Published in the official WordPress Plugin Directory and maintained as an open-source plugin.

View on WordPress.org View source on GitHub

Project summary

Built and released a product-style WordPress plugin that lets admins control maintenance and coming-soon experiences without relying on a bloated page-builder workflow.

Published on WordPress.org with public source, admin controls, responsive rendering, contact channels, and safe request routing.

View matching service: Custom WordPress Plugin Development

Abstract settings illustration for Maneuvrez Maintenance Studio

Project summary

Plugin type

Maintenance / coming soon

Availability

Published on WordPress.org

Control model

Admin-managed content and design

Built and released a product-style WordPress plugin that lets admins control maintenance and coming-soon experiences without relying on a bloated page-builder workflow.

Buyer-facing summary

Client problem

A maintenance page often needs more than one static screen: configurable content, contact options, social links, preview behavior, and safe login access.

What I delivered

I built a public WordPress plugin with admin settings, frontend rendering, Contact Channels, optional maintenance-page and floating contact buttons, bypass behavior, and safe request handling.

Business result

The plugin gives site owners an installable 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 Maintenance Studio was to build a plugin that felt like a small product: clear admin controls, predictable frontend rendering, contact paths, 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.

Maintenance mode had to avoid interfering with WordPress REST, AJAX, cron, WP-CLI, login, logout, and password-recovery flows.

What I built

Admin settings and component controls

Built settings that let admins control maintenance mode, coming-soon mode, page content, design options, social links, contact buttons, and component visibility.

Frontend maintenance rendering

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

Contact Channels and floating access

Added Contact Channels for WhatsApp, Messenger, phone, email, directions, and custom links, with optional maintenance-page buttons and an optional floating contact button that can remain available on the live site.

Preview, login, and bypass behavior

Added administrator bypass, temporary testing bypass, permitted frontend paths, login-access controls, and an optional custom login URL so maintenance mode stays useful without surprising the owner during active work.

Admin-controlled maintenance and coming-soon settingsPublic maintenance/coming soon renderingConfigurable content and design controlsContact Channels and optional contact buttonsSocial linksComponent visibility controlsLogin access and bypass behavior

Technical decisions

WordPress hooks control when the maintenance page appears, while administrator bypass, temporary testing bypass, and permitted frontend paths preserve safe review paths.

Admin settings are treated as product controls, not just raw fields, so content, design, social links, and contact components can be enabled or hidden intentionally.

Login access controls, an optional custom login URL, and safe handling for system requests 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, administrators, REST requests, AJAX calls, cron jobs, WP-CLI, login, logout, or password recovery to work correctly.

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

Outcome

The project progressed from a custom product project into Maneuvrez Maintenance Studio, a public WordPress plugin available through the official WordPress Plugin Directory.

The source code is publicly available, making the implementation easier to inspect than a private portfolio-only project.

It demonstrates WordPress plugin architecture, settings management, admin UX, secure request routing, frontend rendering, sanitization, and release preparation.

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 RenderingRequest Routing

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.

Discuss a custom WordPress plugin View the matching service Review pricing

Related work

WordPress Plugin / Geolocation

Location Radius Redirect Plugin

A WordPress plugin that redirects users based on configured radius rules, center points, shortcodes, and user actions.