UX/UI · Development · CMS · Content migration · Deployment
Naše Horoměřice already had an identity, an existing website and years of accumulated content.
The project was not about starting again.
It was about giving that content a clearer structure, a more contemporary interface and an editorial system that could be managed without technical intervention.
Transformation / Drag to compare
A direct comparison using the real archived HTML and the current live website—not reconstructed mockups.
Now
Then01 / Before
The previous Webnode website contained a substantial archive of articles, campaign information, people and permanent content, but much of it had accumulated inside long pages. Rather than discarding it, we used that material as the starting point for a new information architecture.
Explore the previous website ↗02 / The shift
Homepage
↓campaign content → articles → images → permanent information → more articles
Website
↓Homepage · Aktuality · Candidates · Representatives · Fixed pages · Election content
We separated recurring content from permanent structure and gave each type of information its own place.
03 / Design
The existing identity was preserved rather than replaced. The redesign focused on hierarchy, typography, spacing, navigation and responsive behaviour, making the same organisation feel clearer and more deliberate.
Visit Naše Horoměřice ↗04 / CMS
The new site uses Payload CMS with a structured editing model. Instead of giving editors an unrestricted page builder, we created predefined page structures and dedicated content types for the information that actually changes.
Editors manage the content.
The system protects the design.
05 / Development
The public website was developed in Next.js, with Payload CMS managing the editorial layer and Neon providing the database. Structured CMS content feeds predefined website components, keeping the editing experience flexible while the public interface remains consistent.
06 / Migration
The existing material was migrated into the new content model rather than rebuilt manually after launch.
Existing content preserved and moved into the new system.
07 / Ownership
The production website, repository, hosting and operational access were handed over so that Naše Horoměřice could operate the system independently. The goal was not to create dependence on AMUI, but to leave behind a website the organisation could genuinely manage and own.
08 / Outcome
The project transformed an accumulated website into a clearer publishing system. The public experience became easier to navigate and more consistent across devices. The editorial workflow became simpler. And the organisation kept its existing content, identity and control over the infrastructure.
Planning something similar?