Thirty-nine templates instead of four hundred pages.
A full rebuild of ENGIE's Australian website. The site had grown one campaign at a time, so each new offer arrived as a bespoke page. I reduced it to eight top-level sections and a set of thirty-nine templates, built on a component library the marketing team assembles pages from without a designer.


A site built one campaign at a time.
ENGIE sells to two audiences that share almost nothing. A household wants a plan and a bill it can understand. A facilities manager wants fire compliance, mechanical servicing, and a tender response by Friday. Both arrived on the same site, and the site had been extended for whichever campaign was running at the time.
The result was a navigation that had stopped describing the business, and a page library where every new offer meant a new bespoke layout for the developers to build from scratch.
Eight sections, three levels deep.
The new structure starts from what a visitor came to do, so a household and a facilities manager separate on the first click instead of competing inside the same menu. Three levels of depth, with a template for each level instead of a layout for each page.

Structure settled before anything was styled.
Every template was wireframed and signed off in grey. It keeps the review on the thing that matters at that stage, which is whether a visitor can find what they came for, and it stops a stakeholder approving a layout because they liked the photograph.
Five templates below, in order of depth. The same modules recur down the set: a summary band, alternating image and text blocks, a card grid, the articles rail, an enquiry band. That repetition is the argument for the component library.





The same skeleton, three depths.
Three levels of the Solutions branch, resolved. Each page is the wireframe filled in with ENGIE's photography and the brand blue, and each one carries the same parts in the same order: hero, a four-item value strip, a card set, then whatever that level owes the visitor. What changes with depth is the ending. A section landing hands off to the next level; a solution page ends in the enquiry form.






A library, so a launch is an assembly job.
Thirty-nine templates only stay maintainable if they are built from shared parts. The component library covers navigation, hero and banner types, card and listing patterns, forms, tables and the footer, each defined at both breakpoints so a mobile layout is a designed state and not a squeezed desktop.
A site the marketing team can run.
The work shipped as an architecture, a template set and a component library, handed to the development team as specifications they built against. The measure of it is that a new ENGIE offer no longer needs a designer to reach the web.
My scope ended at design and handover, so the figures here describe what was delivered and not what it changed. Traffic and conversion measurement sat with ENGIE.