<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>React on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/react/</link>
    <description>Recent content in React on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/react/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Storybook vs Ladle vs React Cosmos: Self-Hosted Component Workshop Guide 2026</title>
      <link>https://www.pistack.xyz/posts/storybook-vs-ladle-vs-react-cosmos-self-hosted-component-workshop-guide-2026/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/storybook-vs-ladle-vs-react-cosmos-self-hosted-component-workshop-guide-2026/</guid>
      <description>&lt;p&gt;Every modern frontend team faces the same problem: UI components grow faster than the documentation can keep up. Components are built, modified, and reused across projects, but without a dedicated workspace, teams end up spinning up full applications just to preview a single button variant. This is where self-hosted component workshops come in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
