Sector(s)
The site presents the group, its employer brand and its job offers, in several languages. It had been developed by another provider. Before launch, the group asked Parker+Parker to take it over: check its quality, secure it, start its RGAA accessibility compliance work, then maintain it. The agency now provides corrective maintenance and continuous improvements for the site.
About the project
Results
- A multilingual Drupal site audited on three fronts: code, security and accessibility.
- Findings gathered in a single list, prioritized with the client, which sets the order of fixes.
- A monthly site health report, presented to the steering committee, on four areas: performance, eco-design, accessibility and security monitoring.
Goal
Make a site developed by another provider reliable, bring it closer to RGAA compliance, then keep it healthy over time.
Challenge
- The code had been written by another team, with different conventions.
- Findings had to be prioritized with the client's IT and communication teams.
- Maintenance needed a clear framework: fixes on one side, improvements and audit follow-ups on the other.
Solution
- Site takeover. Retrieval of the code, environments and documentation, then an assessment of the site.
- Three audits. Code audit, security audit and accessibility audit, with findings ranked in three priority levels.
- One reference list. Findings were consolidated with the client's teams into a single list, which now sets the order of fixes.
- Fixes and RGAA batch. Delivery of the priority fixes, then of a batch dedicated to accessibility compliance.
- Maintenance governance. Shared ticket board, client approval before each intervention, a committee every two weeks, regular releases and an emergency procedure.
- Monthly health report. Every month, a report presented to the steering committee tracks performance, eco-design, accessibility and security monitoring, based on automated measurements.
What editors do without developers
The client's teams prepare and publish country versions and translations themselves in the Drupal back office. Parker+Parker maintains the shared platform.
Why Drupal was chosen
The site was already built on Drupal. Keeping it protected the work already done: content model, translations, job offers and design. Drupal's built-in multilingual system serves every country version from a single codebase and a single admin interface, with no separate sites to keep in sync. Its open, documented architecture let a new team audit the code, find what needed fixing and fix it. Security updates, published regularly by the Drupal Security Team, give a clear basis for long-term maintenance.
Technical Specifications
Drupal version:
Key modules/theme/distribution used:
Paragraphs, already in place on the site, is used to build pages.
