<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Page Builder on Nalar</title>
    <link>https://nalar.dev/tags/page-builder/</link>
    <description>Recent content in Page Builder on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/page-builder/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Plugin-Driven Blocks in a React Page Builder</title>
      <link>https://nalar.dev/plugin-driven-page-builder-blocks/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/plugin-driven-page-builder-blocks/</guid>
      <description>&lt;p&gt;A page builder does not need to compile every block into one permanent application bundle. The core can stay stable while independently shipped plugins register new block types, provide editor controls, and define how those blocks appear on the public site.&lt;/p&gt;&#xA;&lt;p&gt;The important boundary is not React itself. It is the contract between the builder core and each block. Once that contract is explicit, the editor can remain a single React application while blocks, CSS, and optional frontend JavaScript are loaded only when required.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
