Not specified
26 proposals
Development of the Architecture for a Unified Fleet Management Platform for WordPress SitesProject Context There is a fleet of several dozen WordPress sites hosted on a single server and maintained by one team. The sites are gradually being transitioned to a unified development and support standard — a common design system with a unified block library (ACF + Gutenberg) and a unified security standard. An architecture is required for centralized management of this fleet.Task A technical architecture for a unified fleet management platform for WordPress sites needs to be developed. The platform is not a metrics dashboard, but a full-fledged system for centralized management and access.Platform Requirements Single Sign-On for Super Administrator — a single entry point for managing all sites in the fleet: overview of status, versions, compliance status. One-click access to the admin panel of each site — the ability to enter the wp-admin of any site in the fleet from a single interface, without storing/entering passwords for each site separately. A well-thought-out authentication mechanism is required (tokens with limited lifespan, binding to a specific user, complete access logging). Role Segmentation: the super admin sees and manages the entire fleet; administrators of individual sites have access only to their own sites. Unified Design System with Site-Level Customization — a common block library (ACF + Gutenberg), distributed to all sites through a central update mechanism, but with the ability for local customization of blocks for a specific site without losing compatibility with future updates of the library. Common Monitoring and Alert Dashboard — status of sites and server, alerts about outages/problems, update status and compliance of each site with respect to the unified standard. Convenient Addition of New Sites to the Network — the platform must support quick cloning/deployment of a new site based on a unified standard (Core plugin, design system) and connect it to the Hub with minimal manual steps.Architectural Constraints (Important) WordPress Multisite is not considered and is not suitable for this task. The reason is not the convenience of the interface, but the fundamental architectural properties of Multisite: A shared database and core for all sites in the network mean a single point of failure: an incorrect plugin or core update can simultaneously disable all sites in the network, not just one. A shared pool of server resources (PHP workers, database connections) means that abnormal load on one site (promotion, traffic spike, attack) degrades the performance of all other sites in the network, including those not related to this load. This systemic property of Multisite cannot be eliminated by process or discipline — therefore, an architecture is required where each site remains an independent installation (own database), and unification and centralized management are achieved by other means.Preliminary Architectural Direction Currently, the most promising architectural approach appears to be Hub & Spoke, where independent WordPress installations (“Spokes”), each with its own database, are united: by a common distributable Core plugin (block library, security baseline, bridge module for connection to the Hub); by a central management application (“Hub”) — site registry, one-click login, monitoring, alerts. However, this architecture is not a predetermined solution. If the executor believes that there is a more suitable architectural approach, they may propose an alternative provided it is technically and economically justified.
A separate task within the terms of reference — a reasoned analysis and recommendation: to build the Hub from scratch custom or to take a ready-made self-hosted solution (MainWP, InfiniteWP, ManageWP or analogs) as a basis and expand it under specific requirements (integration with the Core plugin, compliance tracking of block versions, future marketing layer). A comparative assessment of timelines, support costs, flexibility, and limitations of each option is needed, with a clear recommendation.Architectural Requirements When designing the solution, the following non-functional requirements must be considered: fault tolerance and absence of a single point of failure for the fleet of sites; the ability for independent updating, rollback, and maintenance of each site; minimization of blast radius during failures and update errors; the ability for horizontal scaling as the number of sites grows; security of centralized management and delegated access; the possibility of subsequently isolating the Hub into a separate infrastructure without changing architectural principles; expandability of the platform for adding new centralized services. Moreover, the architecture must remain viable when the number of sites increases from several dozen to 100+ without the need for a fundamental revision of the chosen approach.Long-Term Development of the Platform The platform is viewed as a long-term foundation for the company's digital ecosystem, not just as a tool for administering WordPress sites. When designing, the possibility of subsequently adding centralized services (for example, managing marketing activities, analytics, component library, integrations, and other modules) without the need to rework the basic architecture must be considered.Technologies The specific stack is not predetermined — the executor independently proposes and justifies technologies in the architectural document (language/framework for the Hub, hosting/deployment model, authentication mechanism, etc.), based on the requirements of the task. A reasoned proposal for technologies is a mandatory part of the work result, alongside a comparison of custom vs ready-made solutions for the Hub.What is Required from the Executor Experience in designing multi-site/multi-tenant architectures on WordPress (principally — NOT based on Multisite) Practical experience with MainWP/InfiniteWP/ManageWP or similar fleet management systems — understanding their capabilities and limitations at the API/extendability level Experience in developing production-level WordPress plugins (ACF, Gutenberg block development, REST API) Understanding security issues when building centralized/delegated access systems (token-based auth, access auditing, minimizing blast radius) Ability to prepare architectural documentation: diagrams, API contracts between Hub and sites, data schemaWork Format The first stage — an architectural document with a reasoned solution (custom vs ready-made solution), a scheme of component interaction, API contract Hub ↔ Core plugin, phased implementation plan. The document should include a wireframe scheme of the platform interface (key screens: site registry, admin access, monitoring dashboard). Following the approval of the architecture — further cooperation may be possible.
Important Note Independent architectural development is expected, based on practical experience in designing and operating similar systems. It is not sufficient to provide a compilation of general recommendations or standard responses generated by AI.
Each key architectural decision must be accompanied by a technical justification: why this approach was chosen, what alternatives were considered, what its advantages, limitations, and potential risks are in the context of this project.
If necessary, the executor should refer to practical experience, existing solutions, documentation, open-source projects, or other sources that confirm the viability of the proposed architectural solutions.
Freelancehunt 
