Skip to content
CV
Browse documentation

Design System

Every visible property comes from a step, and every element exists exactly once. Everything the pages are built from lives here.

Each category loads its own examples. Source contracts sit beneath each preview; native hover and keyboard focus can be tested directly.

Main pages

The shared parts of Home, Work, About and Tools: panel with its crumb bar, row list, „Built with“, ⌘K palette and keys sheet, and the rules of the beacon.

Panel

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/MainPageDemos.astro

src/components/Keycap.astro

src/components/site/RowList.astro

src/components/site/Section.astro

src/components/site/Surface.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<Surface root="Home" first={ui.work}>
   <Section section="demo-a" title={ui.work} count="03"><Fragment slot="meta"><Keycap>J</Keycap><Keycap>K</Keycap><em>{ui.navigate}</em></Fragment><RowList items={rows}/></Section>
   <Section section="demo-b" title={ui.about}><p class="ds-main__pad">{en?'One header for the whole surface; it names the section one is reading.':'Ein Kopf für die ganze Fläche; er nennt den Abschnitt, in dem man gerade liest.'}</p></Section>
  </Surface>

Row list

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/MainPageDemos.astro

src/components/site/RowList.astro

src/components/site/Section.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<Section section="demo-rows" title={ui.cases} count="03"><RowList items={rows}/></Section>

Built with

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/MainPageDemos.astro

src/components/site/BuiltWith.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<BuiltWith locale={locale}/>

⌘K palette

Where to? Cases, pages, contact …Esc

  • CasesPlatform Experience & AIzvoove · 2025 – present
  • CaseszAIn · AI assistantzvoove · 2025 – 2026
  • Caseszvoove Skills · Designing with AIzvoove · 2025 – 2026
  • CasesCompass Design SystemContainer xChange · 2022 – 2025
  • CasesxChange Financial ServicesContainer xChange · 2022 – 2025
  • CasesUWX · Unified Work Experiencezvoove · 2026

↑↓choose↵open?Keys

Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/MainPageDemos.astro

src/components/Keycap.astro

src/components/Zeichen.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="sx-cmd sx-cmd--demo" data-demo-static>
   <div class="sx-cmd__in">
    <p class="sx-cmd__top"><Zeichen icon="search" size={16}/><span class="sx-cmd__q">{ui.cmdPlaceholder}</span><Keycap>Esc</Keycap></p>
    <ul class="sx-cmd__list">{places.slice(0,6).map((p,i)=><li aria-selected={i===0?'true':'false'}><span class="sx-cmd__g">{p.g}</span><span class="sx-cmd__t">{p.t}</span><span class="sx-cmd__s">{p.s}</span></li>)}</ul>
    <p class="sx-cmd__foot"><span><Keycap>↑</Keycap><Keycap>↓</Keycap>{ui.choose}</span><span><Keycap title="Enter">↵</Keycap>{ui.open}</span><span class="sx-cmd__keys"><Keycap>?</Keycap>{ui.keys}</span></p>
   </div>
  </div>

Keys sheet with its switch

Keys on this pageEsc

⌘K
Jump anywhere
JK
Through the work
↵
Open
T
Light / dark
?
This list
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/MainPageDemos.astro

src/components/Keycap.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<div class="sx-cmd sx-cmd--demo" data-demo-static>
   <div class="sx-cmd__in">
    <p class="sx-cmd__top"><b>{ui.keysTitle}</b><Keycap>Esc</Keycap></p>
    <dl class="sx-keys">{ui.keyRows.map(([k,d])=><div><dt>{k.split(' ').map(x=>{const c=cap(x);return <Keycap title={c.t}>{c.k}</Keycap>;})}</dt><dd>{d}</dd></div>)}</dl>
    <label class="sx-keys__off"><input type="checkbox" data-keys-off-demo disabled/><span><b>{ui.keysOff}</b><small>{ui.keysOffHint}</small></span></label>
   </div>
  </div>

Beacon · rules

Place
One canvas behind the page; panels sit above it, the beacon passes behind them.
Start
Beside the claim: right of the headline, in its lower third; it eases into its path over the first stretch.
Path
Seeded per visit, never the same; it follows the reading position and leaves a fading trail.
Budget
60 fps at 4x CPU throttle; 20 fps idle, 60 only while scrolling; colour read only on a theme change.
Off
In hidden tabs, under 768 px; reduced motion: position only, no drift. Without JavaScript the canvas stays empty.
Usage and source contract

Reuse this composition from its source and demo. Keep its existing semantic structure and locale/data contracts.

Primary source: src/components/ds/MainPageDemos.astro

States: default · keyboard focus where interactive · light / dark · reduced motion

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<dl class="ds-main__rules">{beacon.map(([k,v])=><div><dt>{k}</dt><dd>{v}</dd></div>)}</dl>
CV · Maximilian Dahl
In plain words

What do you actually do, Max?

My parents and family have nothing to do with tech or my profession. They told me they did not understand my website. This is for them. And for anyone who would like an explanation without the jargon.

I make software easier to work with.

When someone spends ages searching for a button or has to enter the same information three times, I want to know why. I watch how people work, talk to them and design a better way through the task. Then we try it together.

My title is Principal Designer. That means I also make decisions about how whole products fit together and help the team build on them. I still design and write code myself.

Here is a simple example.

At zvoove, I designed an assistant called zAIn. This simplified example shows the idea:

  1. Someone asks

    “How much holiday do I have left?”

  2. The assistant looks it up

    It finds the information and explains the answer.

  3. The person decides

    If they want to book time off, they review the details before anything is sent.

My job is to work out what people need to see, how the answer should be explained and when the program needs their approval.

A design system is a bit like LEGO.

Imagine every team inventing its own bricks. Nothing fits. With a shared kit, the pieces connect, even when people build different things.

Shared pieces. Different things you can build.
Book time offReview an invoice

In software, those pieces are things like buttons, input fields and messages, plus rules for how they work together. I built this kind of kit at Container xChange. It is called Compass.

What has come out of my work?

One starting point
At zvoove, I designed the shared starting point for several programs and tried it out in code. It became Launchpad, which has been live since August 2026.
Built, too
I built the visible part of the notification centre myself. A backend engineer built the part behind it, and we shipped it together.
A team that can build on the work
At Container xChange, I grew the design team from 4 to 14 together with Niclas. Compass gave designers and developers a shared kit to work with.

What am I particularly good at?

I look beyond the screen in front of me. When several teams run into the same problem, I look for a solution they can share. That is how Compass came about.

And I like making an idea tangible early. I can build a working version myself, put it in front of someone and find out where it falls short. I would rather learn that from using it than from a long discussion about a picture.

What would I like to do next?

I want to help decide what a product should become, support a team and keep building myself. I am looking for a role as a Principal Designer, Team Lead or AI Product Builder, in a team that builds with artificial intelligence.

In plain words: I want to take responsibility for the whole thing, without giving up the part I enjoy most — trying things out and making them work.