<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Container Queries on Nalar</title>
    <link>https://nalar.dev/tags/container-queries/</link>
    <description>Recent content in Container Queries on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/container-queries/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Container Queries for Component-Level Responsive CSS</title>
      <link>https://nalar.dev/container-queries-component-responsive-design/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/container-queries-component-responsive-design/</guid>
      <description>&lt;p&gt;Media queries answer a viewport-level question: how wide is the browser? Reusable components often need a different answer: how much space does &lt;em&gt;this component&lt;/em&gt; have where it was placed?&lt;/p&gt;&#xA;&lt;p&gt;CSS container queries solve that problem. A card can render compactly in a sidebar and switch to a horizontal layout in a wide content area without knowing either page layout in advance.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-viewport-breakpoints-leak-layout-assumptions&#34;&gt;Why viewport breakpoints leak layout assumptions&lt;/h2&gt;&#xA;&lt;p&gt;Consider a reusable article card. A media query might switch it to two columns when the viewport exceeds 900 pixels:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
