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.

Primitives

Buttons

Usage and source contract

Actions use Button; navigation uses buttonVariants on a native anchor. Pass type="button" for non-submit actions.

Primary source: src/components/ui/button.tsx

Variants: variant: primary | secondary | ghost | link · size: sm | md | icon · asChild: boolean (React composition only)

States: default · hover · focus-visible · disabled · aria-busy + disabled (composition)

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<Button type="button" variant="secondary" size="sm">Save</Button>
<Button type="button" aria-busy="true" disabled>Saving…</Button>

Input

Usage and source contract

Use Input for native text/search fields. Always connect a visible label; errors use aria-invalid and aria-describedby.

Primary source: src/components/ui/input.tsx

Variants: size: sm | md · native input props except numeric size

States: empty · filled · focus-visible · disabled · readOnly · aria-invalid + aria-describedby

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<label for="search">Search work</label>
<Input id="search" type="search" size="md" />

Tags

neutral · mdbrand · mdok · mdwarn · mddanger · mdmeta · md
neutral · smbrand · smok · smwarn · smdanger · smmeta · sm
Usage and source contract

Badge communicates a short label, never release status without evidence. State text must remain readable without color.

Primary source: src/components/ui/badge.tsx

Variants: tone: neutral | brand | ok | warn | danger | meta · size: md | sm · dot: boolean

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="flex flex-wrap gap-2">
    <Badge dot>neutral</Badge><Badge tone="brand" dot>brand</Badge><Badge tone="ok" dot>ok</Badge><Badge tone="warn" dot>warn</Badge><Badge tone="danger" dot>danger</Badge>
  </div>
  <div class="flex flex-wrap gap-2"><Badge size="sm" tone="meta">Chat</Badge><Badge size="sm" tone="brand">Human Gate</Badge><Badge size="sm" tone="ok">Autonom</Badge><Badge size="sm" tone="warn">Ausstehend</Badge></div>

Card

A calm surface

Cards hold one unit of content and lift off the page by one shadow step.

Flagship
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/ui/card.tsx

src/components/ui/badge.tsx

src/components/ui/separator.tsx

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

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<Card className="max-w-text">
    <CardHeader><CardTitle>{t(locale, 'ds.cardTitle')}</CardTitle><CardDescription>{t(locale, 'ds.cardBody')}</CardDescription></CardHeader>
    <Separator />
    <div class="flex gap-2"><Badge tone="brand" dot>{t(locale, 'flag.tag')}</Badge></div>
  </Card>

Table

FigureWhat
0 → 1One entry point for every zvoove product, from the first shell prototype to shipping with the zvoove One bundles.
4 → 14Grew the Container xChange design team as Design Co-Lead.
Seven figuresOutstanding customer receivables brought back, a joint initiative in finance.
Since 2017My own design systems, from car2go and SHARE NOW to Compass.
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/ui/table.tsx

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="overflow-hidden rounded-card bg-panel shadow-lift">
    <Table>
      <TableHeader><TableRow><TableHead>{locale === 'de' ? 'Kennzahl' : 'Figure'}</TableHead><TableHead>{locale === 'de' ? 'Was' : 'What'}</TableHead></TableRow></TableHeader>
      <TableBody>
        {proof.map((n) => <TableRow><TableCell className="text-lg font-medium text-ink tabular-nums">{t(locale, `proof.${n}.v`)}</TableCell><TableCell>{t(locale, `proof.${n}.t`)}</TableCell></TableRow>)}
      </TableBody>
    </Table>
  </div>

Dialog, menu, tooltip

Usage and source contract

Use the existing Radix dialog/menu/tooltip wrappers. Dialogs require an accessible title and focus return; tooltips never carry essential content alone.

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

src/components/islands/DsDialogDemo.tsx

src/components/islands/DsTooltipDemo.tsx

src/components/islands/PanelMenu.tsx

src/components/islands/PreRead.tsx

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="flex flex-wrap items-center gap-3">
    <DsDialogDemo client:visible open={t(locale, 'ds.dialogOpen')} title={t(locale, 'ds.dialogTitle')} body={t(locale, 'ds.dialogBody')} close={t(locale, 'ds.close')} />
    <PanelMenu client:visible label={t(locale, 'ds.menuLabel')} items={[{label: t(locale, 'ds.menuAll'), href: '/work/'}, {label: t(locale, 'ds.menuCv'), href: t(locale, 'nav.cvHref')}]} />
    <DsTooltipDemo client:visible trigger={t(locale, 'ds.tooltipTrigger')} text={t(locale, 'ds.tooltip')} />
    <PreRead client:visible trigger={t(locale, 'preread.open')} title={t(locale, 'preread.title')} intro={t(locale, 'preread.intro')} items={[t(locale, 'preread.1'), t(locale, 'preread.2'), t(locale, 'preread.3')]} closeLabel={t(locale, 'ds.close')} />
  </div>

SegmentSwitcher

Usage and source contract

Use links for navigation and buttons for in-page choices. Exactly one current/pressed item.

Primary source: src/components/SegmentSwitcher.astro

Variants: mode: links | buttons

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="flex flex-wrap items-center gap-6">
    <SegmentSwitcher name="lang-demo" mode="links" label={t(locale, 'lang.label')} items={[{value: 'de', label: 'DE', lang: 'de', href: localePath('de', '/design-system/'), current: locale === 'de'}, {value: 'en', label: 'EN', lang: 'en', href: localePath('en', '/design-system/'), current: locale === 'en'}]} />
    <SegmentSwitcher name="theme-demo" mode="buttons" label={t(locale, 'switch.theme')} items={[{value: 'system', label: t(locale, 'theme.system'), current: true}, {value: 'light', label: t(locale, 'theme.light')}, {value: 'dark', label: t(locale, 'theme.dark')}]} />
  </div>

Icon control

Usage and source contract

Use IconButton or iconButtonVariants; every icon-only control needs an accessible name.

Primary source: src/components/ui/icon-button.tsx

src/components/Zeichen.astro

Variants: size: md | sm

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="flex items-center gap-3">
    <button type="button" data-c="icon-button" class={iconButtonVariants()} aria-label={t(locale, 'ds.close')}><Zeichen icon="close" size={16} /></button>
    <button type="button" data-c="icon-button" class={iconButtonVariants({size: 'sm'})} aria-label="Zoom"><Zeichen icon="expand" size={16} /></button>
  </div>

Shortcuts

CKSWLT↵Esc?

Chapters CPre-read KRead the case RStory S / W

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/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="flex flex-col gap-4"><div class="flex items-center gap-2 text-xs text-ink-muted"><Keycap>C</Keycap><Keycap>K</Keycap><Keycap>S</Keycap><Keycap>W</Keycap><Keycap>L</Keycap><Keycap>T</Keycap><Keycap title="Enter">↵</Keycap><Keycap>Esc</Keycap><Keycap>?</Keycap></div><p class="flex flex-wrap items-center gap-6 text-xs text-ink-muted"><span class="inline-flex items-center gap-2">{t(locale,'case.chapters')} <Keycap>C</Keycap></span><span class="inline-flex items-center gap-2">{t(locale,'case.preRead')} <Keycap>K</Keycap></span><span class="inline-flex items-center gap-2">{t(locale,'case.readCase')} <Keycap>R</Keycap></span><span class="inline-flex items-center gap-2">Story <Keycap>S</Keycap> / <Keycap>W</Keycap></span></p></div>

Switch · Radix

Usage and source contract

Use the existing Radix Switch with a visible label and controlled on/off semantics.

Primary source: src/components/ui/switch.tsx

src/components/islands/SwitchDemo.tsx

Variants: checked | unchecked · disabled

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

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<SwitchDemo client:load label={t(locale,'keys.enabled')}/>

KeyboardHelp

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/islands/KeyboardHelp.tsx

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.
<button hidden type="button" data-keyboard-help aria-haspopup="dialog" aria-expanded="false" aria-keyshortcuts="?" class="inline-flex min-h-8 items-center gap-2 rounded-control border border-line px-3 text-sm hover:bg-sunken focus-visible:outline-2 focus-visible:outline-ring"><Keycap>?</Keycap>{t(locale,'island.label')}</button>
  <KeyboardHelp client:load title={t(locale,'island.label')} close={t(locale,'case.close')} enabled={t(locale,'keys.enabled')} hint={t(locale,'keys.hint')} native={t(locale,'keys.native')} sections={{reading:t(locale,'keys.reading'),page:t(locale,'keys.page'),focus:t(locale,'keys.focus')}} shortcuts={[{key:'?',label:t(locale,'keys.help')},{key:'L',label:t(locale,'island.lang')},{key:'T',label:t(locale,'island.theme')}]}/>

Metadata chip

Figma MakeClaude CodeLovable
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/ControlDemos.astro

src/components/ui/badge.tsx

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="flex flex-wrap gap-2"><Badge tone="meta">Figma Make</Badge><Badge tone="meta">Claude Code</Badge><Badge tone="meta">Lovable</Badge></div>

Glossary term

Every action with an effect passes the .

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/islands/Term.tsx

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

  • Use native semantics and visible keyboard focus.
  • Check 320px, long content and both themes.
<p class="max-w-text">{t(locale, 'term.before')}<Term client:visible term={t(locale, 'term.word')} title={t(locale, 'term.title')} body={t(locale, 'term.body')} />{t(locale, 'term.after')}</p>
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.