One View Across WordPress, Drupal, and Custom Sites
The platform debate that never ends
Every large estate has one: the long-running argument about whether everything should move to Drupal, or WordPress, or something new. Meanwhile, sites keep running on all of them, plus a few custom stacks nobody wants to touch.
The argument often blocks governance. Teams wait for consolidation before they inventory, score, or set policy. Consolidation does not come, and the estate keeps growing.
Mixed platforms are normal
Different platforms exist for good reasons. A research group chose Drupal for structured content. A department picked WordPress because its editors knew it. A vendor built a custom app. Forcing them all onto one platform can be the right long-term decision, but it should not be the precondition for knowing what you have.
A governance layer above the platforms
Accorbis is a standalone web governance platform. It gives one dashboard across the WordPress, Drupal, and custom sites an organization already runs. It is not a CMS and not a hosting company.
It sits above WordPress, Drupal, and custom sites. Discovery finds them. The dashboard shows each one’s owner, platform, and status, with accessibility, performance, uptime, and security scoring across all of them. No agent is installed on the sites and no CMS migration is required.
What one view lets you do
Compare like with like
See whether accessibility problems cluster on one platform, then find the shared code behind them and fix it at the source.
Track updates
Spot sites running outdated core versions or plugins regardless of CMS.
Set one policy
Accessibility, security, and ownership rules that apply across the estate, not per platform.
Make the platform decision with data
If consolidation is right, the inventory tells you what has to move and what can be retired first.
What stays the same
Editors keep using the CMS they know. Hosting stays where it is unless you decide otherwise. Hosting with Accorbis is a separate line, only for the sites you choose. Migration and rebuild work comes from your implementation partner.
A hypothetical: the consolidation that waited for data
Imagine a university that has argued for years about moving everything to one CMS. It puts governance on hold until the decision is made. Meanwhile, three new department sites launch on a third platform. When the university finally sees its estate in one dashboard, it learns that most accessibility issues come from two old themes, not from any one CMS. Fixing those themes matters more than the platform debate.
The data did not settle the platform question. It showed which question mattered first.
A checklist for a mixed-platform estate
- Record platform and version for every site.
- Group sites by theme or design system, not only by CMS.
- Compare accessibility and security scores by group.
- Flag sites running unsupported versions.
- Agree one set of policies that applies regardless of platform.
- Revisit the consolidation question once a year with current data.
Decision criteria for consolidating a site
- Is the site on an unsupported version with no upgrade path?
- Would moving it reduce maintenance more than it costs?
- Do its editors have the skills for the target platform, or a plan to learn?
- Is its content still needed in its current form?
If none of these apply, governing the site where it is may be the better choice.
Common mistakes in mixed estates
- Separate lists per platform. The Drupal team and the WordPress team each keep their own inventory, and neither sees the whole estate.
- Policy written for one CMS. Rules that only make sense on one platform leave the rest ungoverned.
- Custom sites ignored. Apps built outside a CMS are often the oldest and least maintained.
- Waiting for consolidation. Governance delayed until a migration that may never happen.
What to report once you have one view
For each platform and theme group: how many sites, how many have owners, how many run unsupported versions, and where accessibility and security scores are lowest. That gives leadership a clear picture of where the estate stands, and it turns the platform debate into a decision about specific sites rather than a general preference.
Frequently asked questions
Does Accorbis replace WordPress or Drupal?
No. It governs them. Your sites stay on their current platforms.
Do we need admin access to every site?
Not for discovery and monitoring of public sites. Owners still need access to make fixes.
Will this help us decide whether to consolidate?
Yes. The inventory and scores give you the facts to make that call.
Can policies differ by platform?
Most policies, such as accessibility and ownership rules, should apply everywhere. Platform-specific rules, such as update schedules, can sit alongside them.
Who runs migrations if we decide to consolidate?
Migration is services work from your team or implementation partner. It is not part of the platform subscription.
Do editors need to learn Accorbis?
Editors keep working in their CMS. The dashboard is mainly for the people who govern the estate.
Does governing in place cost more than consolidating?
It depends on the estate. One view of every site gives you the facts to compare the two for each site, rather than deciding for the whole estate at once.
Next step
Schedule a 30-minute working session and see your platform mix in one place.
