1,000+ government service pages, migrated without dropping accessibility
On a large government Drupal platform I migrated more than 1,000 service pages, kept them WCAG-compliant, and cut page-load times about 25%.
What is public
The constraint, then the result
The organisation is a government platform. I am not publishing the agency name, internal URLs, or documents that are not mine to share. The figures below are the ones I already state publicly.
- Role: Senior Drupal Developer on the platform
- Scope: 1,000+ service pages migrated
- Accessibility: WCAG compliance kept through the move
- Performance: page-load times cut about 25%
That combination is the point of the engagement. A page count without accessibility would have failed the platform’s own standard. A fast page that failed WCAG would have failed it too. The migration had to carry both.
What this does not prove
A public-sector result is not a template you can copy onto a brochure site
Government service pages are structured, repeated, and held to an accessibility bar. A membership site with custom checkout, or a Drupal 7 site still on PHP 7.4, is a different project. I use this work as evidence that I have done the unglamorous part — large content moves, WCAG, and measured load time — not as a promise that every site shrinks load time by 25%.
If you need a similar move, the first step is still an inventory: content types, templates, and which URLs already rank. See Drupal migration and Drupal 7 migration for how that assessment is scoped.
Have a large content set to move?
Send the URL. I’ll tell you whether this kind of migration applies, and what would be different.
Request a free assessment