ENGIE Australia  /  Corporate website  /  Design system

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.

Client
ENGIE Australia
Role
Lead UX/UI designer
Scope
IA, templates, system
Platform
Desktop and mobile
Handover
Built to spec by the dev team
The ENGIE Australia homepage: masthead, hero and the four value propositions
The same homepage on a phone
Homepage  /  Designed as a pair, not derived
Templates
39
Covering every page type across three levels
Components
268
One library, both breakpoints
Top-level sections
8
Down from a navigation nobody could hold in mind
01
The problem

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.

Navigation
Grown by addition, so related services sat in unrelated places.
Pages
Bespoke per campaign, which made every launch a build instead of an assembly.
Enquiry
One general contact form for a household question and a commercial tender alike.
02
Architecture

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.

Level
Templates
What it carries
Level 1
8
Section landing pages, one per top-level destination.
Level 2
15
Service and category pages, where a visitor decides what they need.
Level 3
16
Detail, proof and conversion, including the enquiry and case-study types.
The proposed sitemap
The proposed information architecture
Every section carries its sub-category count, so the shape of the site is arguable before a single page is designed. The footer was structured separately, since it answers a different question from the navigation.
03
Wireframes

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.

Templates
Our Services
Level 1
Our Services wireframe
A section landing routes; it does not sell. A summary band and the value propositions, then one card per service area: electrical and communications, AV, mechanical, fire protection. It closes on "Why ENGIE?" because the decision at this depth is whether to keep going, not what to buy.
Solutions for Territories
Level 2
Solutions for Territories wireframe
The first template that has to argue. Value propositions, then alternating image and text blocks for the narrative, then three solution cards: Better Cities, District Heating and Cooling, Energy Networks. A council reading this is comparing approaches, so the page gives them prose before it gives them a choice.
Electrical & Communications
Level 3
Electrical and Communications wireframe
Seven sub-services in a three-up grid, from data network cabling to cable assembly. The uneven count is the point: the grid had to hold three, seven or four items without a bespoke layout, which is what made it a template instead of a page.
Better Cities
Level 3
Better Cities wireframe
A solution page rather than a service list. Summary, two alternating narrative blocks, the articles rail, then the enquiry band. Same parts as the Territories template, fewer of them, because a visitor this deep has already chosen.
Security System Installation
Level 4
Security System Installation wireframe
The deepest template, and the only one with a call to action in the hero. Three narrative blocks, testimonials, then the contact form. At this depth the visitor knows what they want, so the page stops explaining and starts collecting.
04
Final design

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.

Pages
Homepage
Level 1
Homepage, desktop
Homepage, phone
First screen, phone
Hero, a four-item value strip carrying the numbers that matter to a commercial buyer, a guided tour prompt, trusted partners, then the three Solutions cards, projects and client testimonials. It sends a visitor onward in the first screen instead of trying to sell from the homepage.
Our Solutions
Level 1
Our Solutions, desktop
Our Solutions, phone
First screen, phone
The same skeleton at the shortest length in the set. Hero, value strip, three audience cards splitting territories, businesses and consumers, then one "Why ENGIE?" block. This is the page that separates a household from a facilities manager, and the whole job is done above the footer.
Solutions for Territories
Level 2
Solutions for Territories, desktop
Solutions for Territories, phone
First screen, phone
The longest page, and the one that earns its length. Three solution cards, three alternating narrative blocks, a paginated projects rail, then a full enquiry form with the enquiry type as radio buttons, so a routed lead arrives already categorised.
05
The system

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.

In the library
Navigation, including a mega-menu designed against the new eight-section structure.
Hero, banner and section-header types, ranked by how much weight a page needs to carry.
Card, listing and table patterns for service, case-study and document content.
Form fields, validation states and the enquiry patterns the contact form is built from.
How it was used
Every template assembled from library components, so a change to a card updates each page using it.
Desktop and mobile designed as a pair, never one derived from the other.
Low-fidelity structure agreed before any visual design, as in section 03.
Specifications handed over screen by screen for the development team to build against.
06
Outcome

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.

01
Eight top-level sections, replacing a navigation that had grown by addition.
02
Thirty-nine templates across three levels, each designed for desktop and mobile.
03
A 268-component library, so a page launch is assembly instead of a bespoke build.
04
An enquiry form specified down to its failure states and reviewed against the build.
Scope of the work

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.