Menu

One set of design tokens for light and dark themes: how I structured an admin dashboard template
📰

One set of design tokens for light and dark themes: how I structured an admin dashboard template

DEV Community: nestjs·Kuan Nurmuhammed·4 days ago
#LGyct8nJ
#devtonestjs#devto#dev#screen#dark
Long article (330 words) — no AI summary yet.
Reading 0:00
15s threshold

I'm building Kore, an admin dashboard template: a Next.js 15 frontend, a NestJS backend and a matching 120-screen Figma kit. This post is about one decision that shaped the whole project: light and dark themes come from a single set of design tokens, not from two hand-maintained stylesheets.

The problem

Most admin templates I looked at treat dark mode as a second skin. Someone copies the light styles, flips the colors, and then the two drift apart. A new screen gets built in light, dark gets patched later, and the details (hover states, chart backgrounds, borders) end up inconsistent.

The approach

Every color, spacing step and radius is a token with a name that describes its role, not its value (a surface, a border, a muted text color, and so on). Components only ever reference roles.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.