<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kuan Nurmuhammed</title>
    <description>The latest articles on DEV Community by Kuan Nurmuhammed (@kuan_nurmuhammed_7310cba4).</description>
    <link>https://dev.to/kuan_nurmuhammed_7310cba4</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1578905%2Fb96ff664-bd39-461f-bf7c-d4df296086dc.png</url>
      <title>DEV Community: Kuan Nurmuhammed</title>
      <link>https://dev.to/kuan_nurmuhammed_7310cba4</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kuan_nurmuhammed_7310cba4"/>
    <language>en</language>
    <item>
      <title>One set of design tokens for light and dark themes: how I structured an admin dashboard template</title>
      <dc:creator>Kuan Nurmuhammed</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:40:38 +0000</pubDate>
      <link>https://dev.to/kuan_nurmuhammed_7310cba4/one-set-of-design-tokens-for-light-and-dark-themes-how-i-structured-an-admin-dashboard-template-445f</link>
      <guid>https://dev.to/kuan_nurmuhammed_7310cba4/one-set-of-design-tokens-for-light-and-dark-themes-how-i-structured-an-admin-dashboard-template-445f</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  The approach
&lt;/h2&gt;

&lt;p&gt;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. A theme is just a mapping from roles to values, so switching theme swaps the mapping and nothing else.&lt;/p&gt;

&lt;p&gt;Two practical consequences:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A new screen is correct in both themes by default, because it cannot reference a raw color.&lt;/li&gt;
&lt;li&gt;The Figma kit uses the same token names as the code, so a designer and a developer talk about the same thing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Things that still needed manual checking
&lt;/h2&gt;

&lt;p&gt;Tokens do not fix everything. Third-party pieces such as charts do not inherit your theme on their own. For example, a chart library's hover cursor can show a white background in dark mode until you override it explicitly. I now check hover and active states visually in both themes for every screen instead of trusting the token mapping.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is in the template
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Next.js 15 frontend and NestJS backend&lt;/li&gt;
&lt;li&gt;120-screen Figma kit&lt;/li&gt;
&lt;li&gt;20 product domains (CRM, e-commerce, inbox, kanban and more)&lt;/li&gt;
&lt;li&gt;87 automated tests&lt;/li&gt;
&lt;li&gt;An HTML/CSS edition as well&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Live demo: &lt;a href="https://web-umber-seven-35.vercel.app" rel="noopener noreferrer"&gt;https://web-umber-seven-35.vercel.app&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Product page: &lt;a href="https://kore-admin-template.vercel.app" rel="noopener noreferrer"&gt;https://kore-admin-template.vercel.app&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Case studies on Behance: &lt;a href="https://www.behance.net/kuannurmuhammed1" rel="noopener noreferrer"&gt;https://www.behance.net/kuannurmuhammed1&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's a one-time $68 purchase with a 14-day refund. I'd like to hear how you handle theming in your own dashboards, especially charts and third-party components.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>nextjs</category>
      <category>nestjs</category>
    </item>
  </channel>
</rss>
