<?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: Morgan Griffin</title>
    <description>The latest articles on DEV Community by Morgan Griffin (@morgantinkers).</description>
    <link>https://dev.to/morgantinkers</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%2F4214150%2Ff746f127-21c1-4bf6-acd9-292d5ca0f3c8.jpg</url>
      <title>DEV Community: Morgan Griffin</title>
      <link>https://dev.to/morgantinkers</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/morgantinkers"/>
    <language>en</language>
    <item>
      <title>Small design systems: tokens first, components second</title>
      <dc:creator>Morgan Griffin</dc:creator>
      <pubDate>Sun, 01 Nov 2026 15:05:42 +0000</pubDate>
      <link>https://dev.to/morgantinkers/small-design-systems-tokens-first-components-second-2mg8</link>
      <guid>https://dev.to/morgantinkers/small-design-systems-tokens-first-components-second-2mg8</guid>
      <description>&lt;p&gt;Every design system I've built that started with components ended up with a pile of one-off variants. The ones that started with tokens survived.&lt;/p&gt;

&lt;p&gt;Tokens are the decisions: spacing scale, type scale, radii, colors, elevation. Components are just the places those decisions show up.&lt;/p&gt;

&lt;p&gt;The order that works for me:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Name the scales.&lt;/strong&gt; 4/8/12/16 is not a system, it's a suggestion. Pick a small set and stop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write the tokens as CSS variables.&lt;/strong&gt; They work in every framework and they make dark mode a variable swap instead of a refactor.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build one component at a time&lt;/strong&gt;, and delete variants that aren't used twice.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The last part is the hard one. A variant that exists because one screen needed it is not a design system, it's a bug with a name.&lt;/p&gt;

&lt;p&gt;Do you keep tokens in CSS variables, a JS object, or both?&lt;/p&gt;

</description>
      <category>design</category>
      <category>css</category>
      <category>frontend</category>
    </item>
    <item>
      <title>The lock file is the contract</title>
      <dc:creator>Morgan Griffin</dc:creator>
      <pubDate>Thu, 29 Oct 2026 02:37:11 +0000</pubDate>
      <link>https://dev.to/morgantinkers/the-lock-file-is-the-contract-4lnj</link>
      <guid>https://dev.to/morgantinkers/the-lock-file-is-the-contract-4lnj</guid>
      <description>&lt;p&gt;Spent a day on a CI build that worked locally and failed on the runner. Same Node version, same lock file, different result.&lt;/p&gt;

&lt;p&gt;A transitive dependency published a patch between our two installs, and only one had it pinned. The lock file existed, but one pipeline step ran an install that ignored it.&lt;/p&gt;

&lt;p&gt;The fix was one flag. The lesson: a lock file only works if every install path respects it.&lt;/p&gt;

</description>
      <category>dependencies</category>
      <category>javascript</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
