<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Node-Editor on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/node-editor/</link>
    <description>Recent content in Node-Editor on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/node-editor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Node-Based UI Editors in 2026: React Flow vs Rete.js vs LiteGraph.js</title>
      <link>https://www.pistack.xyz/posts/2026-09-09-node-based-ui-editors-react-flow-rete-litegraph-comparison/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-09-node-based-ui-editors-react-flow-rete-litegraph-comparison/</guid>
      <description>&lt;p&gt;Every second product team now ships some kind of node graph: workflow builders, data transformation editors, diagramming surfaces, pipeline designers. The hard part is never the idea — it is picking the editor library underneath it. Choose wrong and you rebuild the whole interaction model eighteen months in, when your custom nodes and serialization format are already baked into every user workflow.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
