Design principles
Use these principles to settle a design question the rest of the system leaves open. Each one says what it changes in a design.
Is it needed
Before a field, a column or a label goes on a screen, ask what a recruiter would lose without it. If the answer is nothing, leave it out.
A WerkOS screen opens on its task, such as the candidates for a welding job in Split, not on a banner about itself. A heading names its subject, with no label above it.
Both themes at once
WerkOS ships a light theme and a dark theme together. Design and check both at the same time, not light first and dark later.
A color is a token with a value for each theme, and a hex code in a component breaks one of the two. Paper stays white in both themes: report pages, slides and PDFs.
Restraint
Let the content carry the screen. Use the Werklist blue as the one accent on neutral ground, separate things with space, and write labels in sentence case.
A view has one primary button. Buttons are flat, with no gradient or glow, and a surface is set apart by its fill instead of a border.
Permitted
A heading in sentence case that names its subject
People scan headings, so the heading does the work.
A gray box with rounded corners and no border
Its fill sets it apart from the page.
Not permitted
An uppercase label above a heading
It repeats the heading louder, and people learn to skip it.
A badge, tag or pill added for decoration
The screen looks like a template, and a real status loses its weight.