Many audiences
Customers, energy producers, suppliers, candidates, media and partners need dedicated journeys within one brand experience.
Case study · Energy and digital transformation
ENGIE Zielona Energia.
A bilingual corporate website bringing energy services, knowledge, recruitment and interactive asset maps into one content platform.
59routes across Polish and English
83frontend components
37Strapi content types
46CMS components
25API communication modules
~24klines of application code
01
The starting point
An energy company website must support sales, corporate communication, expert publishing and recruitment, each with a different content structure and publishing rhythm.
Two languages
Polish and English cover pages, posts, categories, services, webinars, FAQs and campaigns.
Different formats
Metrics, timelines and maps sit alongside documents, video, forms and editorial content.
Corporate standards
SEO, accessibility, consent, analytics, security and alignment with ENGIE's visual language.
02
Solution architecture
Next.js delivers the statically published frontend while Strapi manages data models, localisation, media and editorial work.
Next.js frontend
React 18 and TypeScript. 58 page files generate 59 public routes in two languages.
Strapi CMS
37 content types, drafts, localisation and 46 reusable components.
Data layer
25 endpoint modules isolate views from the REST API and handle relations and locales.
Publishing
Static export with sitemap generation, redirects and route uniqueness validation.
Editors manage content without code changes while the frontend controls structure and presentation.
03
A modular content system
Strapi dynamic zones map to typed React components.
10 page blocks
Background, image and form sections, lists, accordions, full media, downloads and video.
Domain models
Services, news, blog, webinars, FAQs, team, ENGIE assets, projects and corporate pages.
Localised data
Fields, relations, slugs and SEO map to Polish and English routes.
Navigation as content
Menus, dropdowns, external links and header variants are CMS-managed.
New campaigns reuse the component language instead of introducing one-off templates.
04
Services and operational data
The site turns ENGIE's broad activity into focused information journeys.
Energy services
Dedicated areas for customers and producers with categories, section navigation and contact calls to action.
Asset maps
Google Maps shows installations in Poland and worldwide with markers, clustering, filters and detail cards.
Knowledge centre
News, blog and webinars include pagination, categories, related content and downloads.
Company and recruitment
History, CSR, team, management systems and jobs from an external platform.
05
SEO and static publishing
The build handles controls normally performed by a server at request time.
CMS-driven metadata
Every page type has localised SEO and social fields.
Automatic sitemap
Configured pages are combined with blog, news and webinar entries.
Redirects
Strapi redirects are exported to a static list also handled by the 404 page.
Route validation
The build detects collisions between dynamic content and system paths.
A release completes only when content, paths, redirects and indexing are consistent.
06
Integrations
The frontend connects the CMS with sales, communication, analytics and HR tools.
Salesforce Web-to-Lead
Contact and newsletter forms submit leads with required consent data.
Google Maps
Interactive asset maps use locations managed in the CMS.
Matomo Cloud
Analytics is loaded centrally without duplicating scripts across views.
YouTube and eRecruiter
Video modules and job listings remain part of one site experience.
07
The ENGIE design system
The visual layer uses semantic tokens for surfaces, text, borders, status and brand accents.
Semantic tokens
Components request brand, neutral, status or accent roles instead of arbitrary colours.
Signature gradient
Blue-to-teal transitions, light surfaces and Lato typography express the brand.
Accessible primitives
Accordions, selects, sliders, checkboxes and navigation use Radix UI.
Purposeful motion
Entry animation, carousels and the layered hero support the content hierarchy.
One system covers the homepage, services, maps, publishing and campaign pages.
08
Results
One platform
Corporate content, services, publishing, webinars, FAQ, recruitment and projects share one architecture.
Complete Polish and English
Routes, content, metadata and collections have parallel localised paths.
Editorial independence
37 models and 46 CMS components provide control without losing frontend consistency.
Extensible builder
Campaigns use reusable blocks aligned with the design system.
Controlled publishing
The build generates the site, sitemap, redirects and valid paths while detecting collisions.
Connected integrations
Sales, maps, analytics, video and recruitment form one experience.
Maintained security
The history includes dependency upgrades, audit fixes and integration hardening.
Continued development
165 commits since August 2024 document improvements to content, SEO, mobile and security.