Sector(s)
The company runs a network of branches. Its Drupal 9 site had to be redesigned on new brand guidelines, from mockups produced by a design agency. Parker+Parker wrote the specifications, developed the blocks and page templates, migrated the branch pages by import and rebuilt the delivery time lookup tool. The upgrade to Drupal 10 was part of the redesign.
About the project
Results
- More than 30 blocks, including the header and footer, that editors configure without code.
- More than 100 branch pages generated by import, each with its original web address.
- Ready-to-use page templates for the editorial team.
Goal
Redesign the site on a new visual identity. The delivery time lookup tool and the branch directory had to be kept through the redesign.
Challenge
- The editorial team publishes rarely, so blocks had to stay simple to fill in.
- Branch pages could not be rewritten by hand, and their web addresses had to stay stable.
- The delivery time tool had to be rebuilt to match the new design, rather than carried over as is.
Solution
- Specifications and block breakdown. One user story per feature, then a breakdown into numbered blocks, plus the header and footer.
- Blocks and page templates. Each template comes pre-filled: the team starts a page from a ready-made structure.
- Branch migration. Branch data was exported from the former site, then imported into a Branch content type. Each branch page was generated with its original web address.
- Rebuilt delivery time tool. Visitors enter the details of their shipment and see delivery times on a map.
- Search. Site search extended to several content types, and branch search by city.
- Testing and editor training. Acceptance testing, then training of the team on content editing.
Standards
Color contrast and the number of colors were reviewed at the mockup stage, before development.
What editors do without developers
The team creates its pages from the pre-filled templates and fills in the blocks in the back office. It was trained on content editing once the blocks were in place.
Why Drupal was chosen
The site already ran on Drupal 9. Moving to Drupal 10 during the redesign avoided a separate upgrade project later. Block-based pages met the main editorial need: a small team that publishes occasionally needed blocks it can fill in and arrange without a developer. Drupal's content modeling made it possible to treat the branch directory as structured content, which made the import possible.
Technical Specifications
Drupal version:
No contributed module is central to this project. Blocks, page templates and the Branch content type rely on Drupal core's content modeling.
