AMUI

Evolve.
Stay you.

A clearer website. A better publishing experience. An identity people still recognise.

For organisations whose website no longer reflects the work they do. We start by understanding what already has value, then redesign the parts that hold it back.

Discuss your project
01 / The evidence

An established identity. A new experience.

Naše Horoměřice already had a website and a CMS. AMUI preserved its identity while reworking the public experience, content structure and editorial system. The case study shows the design and implementation decisions, including migration into Payload CMS.

Drag the image to compare before and after, or focus the slider and use the arrow keys.

Naše Horoměřice / A real transformationExplore the difference
Naše Horoměřice before the redesign
Naše Horoměřice after the redesign
50%
Preserve the recognition

Still recognisably them.

The existing identity stays at the centre. Colour and familiar visual material connect the new website to the organisation people already know.

Identity retained · Content structure rebuilt · 41 news items, 76 media items and 15 candidate records migrated to Payload CMS.

02 / The scope

Decide what stays. Make change count.

01

Review the current site.

We look at navigation, important content, page layouts, publishing and the journeys visitors need to complete. Available search and enquiry evidence helps identify the priorities.

02

Reshape the experience.

We plan clearer content hierarchy and responsive layouts. Existing logos, colours and useful brand assets can remain part of the design rather than being replaced automatically.

03

Plan the transition.

We review content exports and existing URLs. The scope identifies what is retained, rewritten, migrated or retired, with redirects planned where page addresses change.

04

Build and hand over.

We develop the agreed website and CMS, review important journeys and launch configuration, and walk your team through the new publishing experience.

The proposal defines the deliverables, review stages and responsibilities for your project. Additional applications, content creation and ongoing support are agreed separately where needed.

Continuity / What comes with you

Change the website.
Preserve what still matters.

Before replacing anything, we agree what needs to carry forward and how. Content, search, systems and infrastructure each need their own transition plan.

Continuity map / 01Illustrative routes / Decisions agreed together
AContent route
  1. 01 / What exists

    Existing copy

    Pages, documents, rough notes

  2. 02 / AMUI decisions

    Review what is useful

    • Keep
    • Rewrite
    • Merge
    • Retire
    Only what is agreed carries forward
  3. 03 / Intended destination

    Approved page content

    Why it mattersThe new structure starts with real material, not guesswork.

BMedia route
  1. 01 / What exists

    Images & files

    Photography, downloads, older assets

  2. 02 / AMUI decisions

    Inventory and map the gaps

    • Reuse
    • Reformat
    • Replace
    • Retire
    Only what is agreed carries forward
  3. 03 / Intended destination

    Media in its new home

    Why it mattersUseful assets carry forward. Missing files have a plan.

Missing material is identified early. Nothing is retired without agreement.

Technical continuity is planned; unchanged search rankings cannot be guaranteed.

Content & media routes shown.
The right starting point

A redesign does not have to become a rebrand.

Sometimes the identity is doing its job and the website needs better structure, typography or development. Sometimes the visual identity needs work too. We separate those decisions during discovery so the proposal addresses the actual problem. For a new website without an existing site to migrate, start with our website design and development service.

Explore website design & development
03 / Decisions & outputs

Know what
gets resolved.

Select an area to see the decisions and outputs it resolves.

Decision area 01 / 04

Audit

A keep, change or retire inventory makes the boundaries clear. Priorities and major risks are recorded, including dependencies on existing content, forms and integrations.

Concrete outputs
A decision record
01Keep / change / retire
02Agreed priorities
03Risk register
04Dependencies
04 / What shapes the scope

Know what
shapes the work.

A visual refresh and a CMS migration are different projects. The quote reflects the depth of change, the content involved and the technical constraints of the existing site.

  • Number of page types and volume of existing content
  • Availability and quality of CMS exports and media
  • Changes to navigation, URLs and integrations
  • Design scope, content approvals and launch constraints

Share your current materials, priorities, budget constraints and any deadline. We can then recommend a scope and agree realistic milestones.

Discuss your redesign
05 / Your next step

Ready for the next version?

Send your current website and tell us what needs to change. The first 15-minute conversation is free.

Discuss your project

Necessary storage keeps your privacy choice. Optional analytics help us understand site performance and are loaded only with permission.

Read the Cookie Policy