<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - User Interface - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ User Interface Articles feed</description>
    <item>
      <title>Article: From Reusable to Regeneratable: Rethinking the Shared UI Component Library</title>
      <link>https://www.infoq.com/articles/regeneratable-ui-component-library/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=User+Interface-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/regeneratable-ui-component-library/en/headerimage/regeneratable-ui-component-library-header-1790758478325.jpg"/&gt;&lt;p&gt;Regeneration has changed reuse economics. A model pointed at a solid design system can produce most standard UI on demand, so paying to keep a canonical component package alive is much harder to justify than it used to be. Keep the design system, tokens, guidelines and tests central. They are what actually buy you consistency.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Web Development</category>
      <category>Web Components</category>
      <category>User Interface</category>
      <category>JavaScript</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 02 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/regeneratable-ui-component-library/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=User+Interface-articles</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-10-02T09:00:00Z</dc:date>
      <dc:identifier>/articles/regeneratable-ui-component-library/en</dc:identifier>
    </item>
  </channel>
</rss>
