<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Tailwind on Tenu Tech Brief</title>
    <link>https://cluster-site.onrender.com/tags/tailwind/</link>
    <description>Recent content in Tailwind on Tenu Tech Brief</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Feb 2026 07:59:06 +0000</lastBuildDate>
    <atom:link href="https://cluster-site.onrender.com/tags/tailwind/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Distinguishing &#39;Components&#39; and &#39;Utilities&#39; in Tailwind</title>
      <link>https://cluster-site.onrender.com/posts/distinguishing-components-and-utilities-in-tailwind/</link>
      <pubDate>Wed, 18 Feb 2026 16:21:41 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/distinguishing-components-and-utilities-in-tailwind/</guid>
      <description>• Here&amp;rsquo;s a really quick tip. • You can think of Tailwind utilities as components - because you can literally make a card &amp;lsquo;component&amp;rsquo; out of Tailwind utilities. • @utility card { bo</description>
    </item>
    <item>
      <title>CSS &lt;code&gt;@scope&lt;/code&gt;: An Alternative To Naming Conventions And Heavy Abstractions</title>
      <link>https://cluster-site.onrender.com/posts/css-code@scope/code-an-alternative-to-naming-conventions-and-heavy-abstractions/</link>
      <pubDate>Thu, 05 Feb 2026 08:00:00 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/css-code@scope/code-an-alternative-to-naming-conventions-and-heavy-abstractions/</guid>
      <description>• CSS @scope rule enables component-level scoping without heavy naming conventions. • Eliminates style leakage, reducing the need for overly specific selectors. • BEM and similar n</description>
    </item>
  </channel>
</rss>
