Selected work
Corporate website platform for a mid-size technology company
Engagement at a glance
- Corporate Website
- Technology
- 2024
- Mid-size technology company
What happened
Challenge
Brand and content had fragmented across regional sites maintained by different teams — inconsistent design, duplicated effort and slow content updates. The same company description existed in several slightly different versions, and nobody could say which was current. Every regional team had reimplemented the same page patterns, so a brand change meant the same work repeated in parallel by people who did not know the others were doing it.
Approach
We designed a unified component system and rebuilt the corporate site on a structured content model, so every section is assembled from consistent, reusable blocks and content changes no longer require developer time. The content model was derived from the pages that already existed rather than imposed on them, which kept the migration a matter of moving copy into fields instead of rewriting it. Regional variation stayed possible, but as configuration rather than as a separate implementation.
Outcome
One consistent corporate presence, faster content publishing for the marketing team, and a codebase the internal team maintains independently. A brand or layout change is now made once and appears everywhere, and the regional teams compose pages from the shared blocks instead of maintaining parallel implementations of them.
Why this stack
The interesting choice here was not the framework but the decision to derive the content model from the pages that already existed rather than to design an ideal one. That kept the migration a matter of moving copy into fields instead of rewriting it, which is what made it finishable. Regional variation became configuration rather than a fork, so a brand change is made once.
What we would do differently
We underestimated how much of the work was social rather than technical. Several regional teams had good reasons for their divergences, and the ones we treated as inconsistencies early were sometimes genuine local requirements. We would now spend the first week interviewing those teams before proposing a shared model, because a component system nobody agrees with gets worked around rather than used.
Stack
- Next.js
- TypeScript
- Tailwind CSS
Contact
Something similar in flight?
Describe where it currently stands and what worries you about it. You will get a considered reply from an engineer, not an autoresponder.