The finished site in 34 seconds, recorded on the production build.

Problem

Every page talks to two readers.

The 17-year-old wants the adventure; the parent paying wants safety. The old site had grown page by page for years: cartoon doctors on the homepage, long text pages, a different pattern on every page. My job was to redesign and rebuild all of it in code, beside the lead designer.

The old homepage: a headline beside two cartoon doctors, a Google rating, and press logos under two buttons
The old homepage.
The old Pilsen university page, a long text page from the previous site
The old university page.

What I found

A prototype you could read as the student or as the parent.

Before any visual design, I moved the old site’s content and the data for 23 universities into a clickable prototype with the review built in: read a page as the student or as the parent, move today’s date so the deadlines change, and see the open questions on the page. The parent compares universities in five tabs, so every page had to scan.

What it cost

A prototype that looks finished invites polish before the structure is right. The first reviews were about structure only, on purpose.

Proof

Every page of the old site had a place in the new structure before any visual design started.

See the second build
The reworked prototype from the same week, a second structure for the homepage
The second build, the same week.
The first prototype: a full-bleed film still with the headline Medizin studieren. Ohne NC. Ab Herbst, under a reviewer toolbar with language, date, reader and open-points switches
The prototype, with its review toolbar.

What I decided

Half the scroll, nothing deleted.

The university page still looked complex. I rebuilt every section on one skeleton: the answer as the heading, one sentence of context, one picture, one way to read more. Secondary detail folded. No sentence went, on all 23.

What it cost

More of the page sits behind a tap, so a reader who wants everything has to open it.

Proof

Same content, about half the length on both screens, and half the words before anything is opened.

See the page on its side and the final page
The same university page twice at one scale, turned on its side: folded on top, about half the length of the fully opened page below
The same page on its side: folded on top, every fold opened below.
The final Pilsen university page: a photo with a white overview card overlapping its foot, holding two actions and six facts
The final university page.
5,982

pixels of scroll on a desktop, down from 12,521

7,673

pixels of scroll on a phone, down from 14,430

619

words before opening anything, down from 1,171

One university, the same content, measured on a staging build.

What I decided

17 directions, one look.

No moodboards, no Figma. I built 15 complete directions in code, the same content side by side. The lead picked a mix of three, then said too much blue, so I made a calmer 17th: white, rounded photo plates, one orange action.

What it cost

15 directions is a lot to review. It only worked because they were side by side, same content, same sections.

Proof

One round of picking settled the look for the rest of the project.

See direction 17 and the variants
  • Every homepage section came in versions he could switch in the browser, and when refining the process page only moved blocks, I built four concepts instead.
Direction 17: a white page, a rounded photo plate with the headline on it, an action card overlapping its foot
Direction 17, the one that shipped.
Homepage hero variant: the headline aligned left on the photo, the actions in a card at the foot
Hero, left.
Homepage hero variant: the headline centered on the photo, the actions in a centered card
Hero, centered.
Six versions of the homepage proof section in a grid: a strip, tiles, large cards, a headline with numbers, a centered number row and small tiles
Six ways to show the proof.
Four versions of the homepage steps section: centered mini interfaces, a card per step, a left column and large numerals
Four of the eight ways to draw the steps.
Four concepts for the process page side by side: a calendar, a phone journey, two paths, and a combination
Four concepts for the process page: calendar, phone journey, two paths, combined.
Four step scenes from the refined process page: the starting point, four steps, step one, and the effort
The refined steps, drawn as small working interfaces.
Sixteen homepage designs in a grid, the same content in sixteen visual directions, from a dark teal poster to a white editorial layout
16 of the 17 directions, same content, side by side.

What I decided

One system, not a pattern per page.

Pages had grown their own patterns: four layouts for the same questions, a new testimonial shape on almost every page, text-only and split heroes. I gave each page one owner, built only from shared parts, and after four rounds every inner page got one hero: the homepage’s photo plate with a white card cut into its foot.

What it cost

One owner per page is slower than changing many pages at once, and every other page waited through four rounds of the hero.

Proof

One hero system now runs on every inner page, at every width.

See every before and after
  • FAQs

    Four layouts for the same questions became one.

  • Quotes

    A new testimonial shape on almost every page became two: written and film.

  • Heroes

    Text-only and split heroes on the inner pages became one hero system, built from the homepage.

Three versions of the cost page: an early text page with three figures, a later layout, and the final photo hero
Costs: two earlier rounds, then the final.
The booking page before, a long page with the form further down
Booking, before.
The booking page after: the promise beside a three-step form
Booking, after.
The about page before, text only
About, before.
The about page after, a group photo of new students in the hero
About, after.
Three rounds of the process page hero: a split hero, a full photo, and the final photo plate with a card
The process page hero: split, photo, plate.
The same three hero rounds on a phone
The same three rounds on a phone.
The testimonials page with a split hero, text left and photo right
Testimonials, round one.
The testimonials page with the final plate hero
Testimonials, final.
The offer page before the redesign, a text-led hero
Offer, before.
The offer page after, a photo hero in the homepage’s system
Offer, after.

What shipped

Every page type, rebuilt in code.

The phone came first in every review, so here is the site on one.

Four final pages on a phone: home, a university, the process and costs

The walk on a phone, then home, a university, the process, costs.

Proof

A 285-issue audit, fixed in five passes, then every page checked at five widths. A cold read of the production build still found a photo of the wrong building and one fee explained two ways. Every page in the sitemap loaded on the final build.

  • Pages

    The homepage, 23 university pages, 9 country pages, the process, offer, cost and question pages, testimonials, a video library, the forms, the blog and the webinars: 214 pages in all.

  • Redirects

    Every one of the 324 old addresses answers with a permanent redirect, so search rankings move with the content.

  • Forms

    Short, one column, one question at a time where it helps. When a lead can’t be sent, the form says so and gives a phone number instead of failing quietly.

  • Consent

    Video and analytics load only after a yes, and a visitor can change the answer from the footer.

  • Access

    Zero contrast failures in axe after the accessibility pass, a skip link, and focus that always shows.

See every page type

Looking back

Next time, one system from day one.

The fastest weeks were the ones where I explored wide and then cut hard. The slowest were the ones where many pages changed at once; one owner per page and shared parts fixed it, and I would start that way.

Beyond the brief

The site hasn’t launched yet, so I have no numbers from real visitors.

Claude Code wrote most of the code, built the directions and variants, and ran the checks. I set the direction, chose between versions and judged every screen.