Skip to content
SproutAceve · v3.12.0
Get started
Overview What is your role? Getting started Install Adopting Sprout
Foundations
Brand & logos Color Typography Spacing & layout Elevation Iconography Accessibility
Components
Overview Buttons Inputs & forms Data grid Ribbon toolbar Navigation Cards Dialog Tabs Context menu
Practice
Interaction & motion Voice & content Product patterns AI patterns
People & ethics
Design principles Personas UX ethics Trust & direction Meet the makers UX Strategi
Playground
Build the systemplay Tower of tokensplay
Behind the system
How it works Why it pays Changelogv3.12 Roadmap Contribute
People

Meet the makers.

Sprout has a Personas page for the people we design for. This is the other half — the designers who actually build and tend the system. Small team, strong opinions, shared craft. Say hello.

Mv
Mikel von Krogh
Head of design · Sprout maintainer
Systems & governance

“The system should win the argument, so the team never has to have it twice.”

Figma variables, Code Connect, and chasing the perfect espresso shot.

LinkedIn Bio Slack
MA
Mathias Andresen
Design system lead · Sprout maintainer
Tokens & theming

“A token you can't explain in one sentence is a token you'll regret.”

Dark-mode contrast curves and a worryingly large mechanical keyboard.

LinkedIn Bio Slack
AY
Amanda Yu
Product designer
Interaction & motion

“Motion is punctuation, not a paragraph. A little goes a long way.”

Spring curves, bouldering, and an unreasonable number of oat-milk cortados.

LinkedIn Bio Slack
EP
Eddie Persson
Product designer
Data-dense UI

“If the table can breathe, the spreadsheet can finally retire.”

Tufte reissues and getting very small type to read perfectly.

LinkedIn Bio Slack
RR
Richard Radnocci
Senior product designer
Field & mobile UX

“Design it for gloves, in the rain, on a flaky 4G connection.”

Offline-first patterns and far too much disc golf.

LinkedIn Bio Slack

How we work

One system, one set of decisions, made together.

Maintainers, not gatekeepers

Sprout is maintained by a couple of us, but it's built by everyone who uses it. Anyone can open a merge request, propose a token, or argue for a new pattern — the maintainers just keep the whole thing coherent.

We sit across products and markets, which is the point: a button that only works for one team isn't a system, it's a preference. Every decision here had to survive at least one person who disagreed.

Want to join in? The fastest way is to ship something small and open a merge request. We'll meet you there.

← PreviousTrust & directionNext →UX Strategi
Sprout · Aceve Design System · v3.12.0
Figma library GitLabReleases