Eniwa Website Relaunch

The question

I started working with Eniwa in 2023 during my time at Linkgroup. The initial task was to prepare the relaunch of eniwa.ch, a website covering a broad range of services and serving very different audiences, from private households and businesses to municipalities and other stakeholders.

Before discussing design or technology, we first needed a clear picture of what the project would actually involve.

I started the project with an Open Project Framework workshop. Together with the Eniwa team, we went through the different parts of the project, discussed requirements, responsibilities and open questions, and created a shared understanding of the scope.

That became the foundation for the planning that followed.

Choosing the right technical setup

One of the larger decisions was the choice of CMS and technical architecture.

Rather than starting with a preferred system, I evaluated the requirements against a range of possible solutions. The resulting CMS evaluation grew to around 70 pages and covered the functional requirements, editorial experience, technical considerations, integrations, costs and the longer-term implications of each option.

Craft CMS was ultimately selected as the backend, combined with Nuxt for the frontend in a headless setup.

The architecture gives the editorial team a flexible CMS while keeping the frontend independent and leaving room for the wider digital ecosystem to evolve over time.

Staying involved throughout the project

My role continued well beyond the initial planning.

I supported Eniwa with strategic and technical questions, project planning and project management, helped translate requirements between the different teams and led the development side of the project.

Linkgroup was the lead agency and responsible for the design and overall client relationship. Development was handled by the team at PAKD on behalf of Linkgroup.

This setup meant I was involved on both sides of many important decisions. I could discuss business and communication requirements with Eniwa and Linkgroup, then work directly with the development team on how those requirements should be implemented.

For me, that is often where consulting becomes most useful. Decisions made early in a project have technical consequences later, and questions that come up during development can just as easily affect the original concept.

What got built

The new eniwa.ch is based on a headless architecture with Craft CMS and a Nuxt frontend.

Alongside the main content platform, we integrated website forms with Salesforce Pardot so enquiries and marketing processes could connect directly with Eniwa's existing systems.

The project was developed over several phases and involved close collaboration between Eniwa, Linkgroup and PAKD.

My responsibility throughout was to keep the different parts connected: the requirements, the technical architecture, the people involved and the decisions that had to be made along the way.

What came of it

The new website went live in May 2025 after more than two years of planning, concept work, design and development.

For me, the project is a good example of the role I like to take on in larger digital projects. I can help establish the project before anything is designed, go deep into questions such as technology selection and architecture, and stay involved during implementation when the theoretical decisions inevitably meet reality.

A project of this size involves a lot of people with very different areas of expertise. Having someone who understands the business requirements, can talk to designers and developers and keeps an eye on the overall direction makes those conversations considerably easier.