A content platform the team can run themselves

What they came with

Avea, a Swiss longevity brand, wanted to publish serious long-form content in more than one language. The team was lean, and they did not want a developer in the loop for every article.

The early decisions

1. Start from how Avea’s editors actually work, then shape the content structure and editorial workflow around that, rather than starting from a theme.
2. Put publishing in the team’s hands from day one. The admin is built so content goes live without a developer.
3. Build for long-form, search-friendly content, with room to add languages without rework. WordPress was chosen because the team could run it, not because it was new.

Who did what

My role

I led it from the very beginning: the scope, the priorities and the phases with the founder, before launch and in every round of work since.

The team’s role at Code Pros

Our team designed and built the custom theme, the editorial workflow and the integrations, and keeps the platform fast as it grows.

The result

Avea’s team publishes on its own. The same team has built and looked after the website and the Insights hub for the past couple of years.