Tilt Renewables
A renewable energy generator with 21 wind, solar and battery projects, each needing to behave like its own small site. We rebuilt the WordPress site so the team can edit all of it, with the right people on the right pages.
- Client
- Renewable energy generator, Australia
- Industry
- Energy & infrastructure
- Shipped
- 2026
- Live at
- Coming soon
Not slow. Just painful to change.
Tilt Renewables develops and runs wind farms, solar farms and batteries across Australia. Each project is a small world of its own: planning documents, community pages, newsletters, benefit programmes, regulatory filings that must point at a stable address. The WordPress site had never been built for that. Project pages lived in a flexible-content field, sub-pages sat as flat top-level slugs, media was split across two hosts, and the projects were not even exposed to the API. Updating one project meant a developer, or a very patient editor.
The site loaded in 1.6 seconds, so speed was not the complaint. Structure was. A team of twelve people needed to edit it, and not everyone should be able to touch everything.
Every project is its own small site.
A pre-rendered Astro site on Cloudflare, edited in CloudCannon. Each of the 21 projects is a folder: a project home with key facts, a location map, stages, stats, gallery and documents, then real sub-pages underneath it (planning and approvals, community, benefits), each with a stable address the regulators can cite. Every project gets its own sidebar, with a second level of anchors for the page you are on, and a newsletter switch that turns a sub-page into a dated newsletter with its own archive.
The news archive, the 21 projects and 12 leader bios came across by script, with 335 redirects so nothing that was linked before goes dark.
Who can edit what.
Twelve people edit the site, in three tiers. Some can edit all of it. Some can only touch news and projects. Some can touch everything except the project pages. Four publishers, and only those four, can send changes live. All editing happens on a staging site; production is locked and only takes reviewed changes through a pull request.
The permission groups run on CloudCannon's file-level rules, scoped by folder, so a project added next year inherits the same restrictions. We scripted the groups, so they can be rebuilt in a minute rather than clicked together again.
A resource hub that builds itself.
Every project carries its own documents: planning applications, approvals, newsletters, community reports. The Resource Hub gathers all 701 of them, across 19 projects and seven document types, into one filterable library with search and shareable links. Nobody maintains it. The hub is collected at build time from the project pages themselves, so it is right on every build, including the ones editors trigger from the CMS, and a check warns if a document is ever placed where the hub cannot see it.
The same build indexes every page for search, writes the sitemap and llms.txt, and pushes every image through the optimiser, which editors cannot bypass by pasting a raw link. Documents and videos live in a Cloudflare R2 library the team uploads to from inside CloudCannon.
The same pages, measured.
The old site was not slow, so the gain is smaller than on most rebuilds. It is still three times faster, with a perfect performance score, on a site with far more in it.
GTmetrix grade
- Before
- B
- After
- A
Performance score
- Before
- 87
- After
- 100
Fully loaded
- Before
- 1.6s
- After
- 549ms
GTmetrix, September 2026, homepage, same location and device for both.
The numbers.
3×
faster
fully loaded in 549 ms, from 1.6 s, with a perfect performance score
21
project mini-sites
each with its own pages, sidebar, documents and newsletter archive
701
documents in one resource hub
collected from 19 projects at every build, nothing to run by hand
3
editing tiers
twelve editors in four permission groups, publishing rights kept separate
335
redirects
every old WordPress address still lands somewhere
Counts from the build, September 2026. The site keeps growing as the team publishes.
Theirs to keep.
The repository lives in Tilt's own GitHub organisation, the site in their own CloudCannon organisation and Cloudflare account, and every document in their own R2 bucket. The permission groups are a script they hold. If we disappeared tomorrow, the team would keep editing.
- Astro
the site, pre-rendered, 273 pages in about four minutes
- CloudCannon
visual editing, staging and publishing, four permission groups
- Cloudflare
hosting on Workers, plus the R2 document library
- Pagefind
search across every page, rebuilt on each deploy
- Mapbox
the location map on every project
- Basin
the four forms
