The Brief
PlanEnergi is an independent Danish consultancy in renewable energy planning — district heating, biogas and Power-to-X, strategic climate planning — working with municipalities, utilities and European research consortia. Two audiences had to be served by one site: partners evaluating whether this team can run their project, and engineers deciding whether to apply. A flat set of service pages couldn't show how the firm's areas, people and project history connect.
What Was Built
1. Three content types, one shared vocabulary
Instead of hand-built pages, the site runs on custom post types: service areas, team members and projects, plus shared taxonomies for area, region and project category. An editor tags a person or a project once, and it shows up wherever that tag belongs. Adding a new specialist or a new project is a content task, not a developer ticket.
2. Areas, people and projects linked, not pasted
On a page like District Heating, the matching specialists and related projects are linked through the shared taxonomies rather than pasted in by hand, so the page follows the team and the project list instead of drifting away from them. The same relations power the team directory, which filters by area and by office region across three locations.
3. Three languages, English at the root
WPML runs three translated versions: English at the domain root, Danish under /da/, German under /de/. For a Danish firm that's a deliberate call — German-speaking and EU consortium partners meet English first, while the home market keeps its own tree. The structure is translated per language instead of being rebuilt as three separate sites, which is why one admin covers all three markets.
4. Recruiting built into the site, not bolted on
Openings are their own post type with a language-aware archive and detail pages, supported by a recruiting block on the homepage and by team pages that show a candidate who they'd be working with. HR opens and closes a role without touching code — so between hiring campaigns the archive is simply empty, which is exactly what an editor-run careers section looks like when nobody is hiring.
The Result
An editor can publish a specialist, a project or a job opening and watch it appear everywhere it belongs, in three languages, without a developer touching a template.
- One admin runs EN/DA/DE instead of three separate sites.
- Team and project pages stay linked automatically as new content is added.
- A careers section the client's own HR team opens and closes on its own.
Stack: WordPress with WPML for EN/DA/DE, custom post types for service areas, team and job openings, shared taxonomies driving the cross-links, and filterable team and project archives. Built in 2023, with hosting and the edge protection layer managed on the client's side.