The starting point: technically solid, visually too dense
The previous portfolio already had a solid technical foundation, bilingual content, and detailed project descriptions. At the same time, the landing page sometimes felt like technical documentation: many surfaces carried equal weight, copy blocks were long, and personal orientation was limited in the first viewport.
Technical depth matters in a developer portfolio, but it does not need to be visible everywhere at once. The central relaunch decision was to stage information more clearly: positioning first, selected cases next, and technical depth on the relevant detail pages.
Patrick Scharf comes before the service promise
The new landing page begins with the name, role, and working context rather than an abstract service statement. Visitors immediately know whose portfolio they are viewing and which engineering field the work belongs to.
Instead of constructing an agency persona, the site remains deliberately personal. A compact technical focus panel shows the integration flow and core stack without overloading the introduction.
Project cases as short decision stories
The most important projects are framed as a sequence of starting point, technical decision, and operational impact. This pattern is faster to scan than a feature list and demonstrates how engineering decisions were made.
Details such as error classes, mapping contracts, and rollback paths remain available, but they are expanded only when readers choose to enter a case or a specialist article.
Less surface, stronger hierarchy
The visual system uses a small set of clearly differentiated surfaces within one consistent dark-green palette: a personal hero, layered case areas, a high-contrast operating model, and calm editorial cards. Large typography and consistent spacing carry the hierarchy.
Motion stays restrained and honors the operating system preference for reduced motion. The relaunch prioritizes legibility, quick orientation, and resilient responsive layouts over spectacle.
The technical foundation stays intentionally lean
Astro remains the static foundation. Content continues to live in central data modules, pages are generated statically, and the existing bilingual URL structure remains intact. Presentation improves without replacing a working architecture for its own sake.
The result is a more personal developer site that does not remove technical depth, but makes it available with much better timing.