Built site for gh-pages

Author: BradyAJohnston

.nojekyll

@@ -1 +1 @@
-671deeb0
+29e8e21e

assets.html

@@ -35,6 +35,19 @@ generate_asset_api(
 
 `PackageLibrary(anchor, relative)` locates a `.blend` shipped inside your own package (resolved relative to `anchor`, usually `__file__`); use `BundledLibrary("…")` for a library that ships with Blender. You can pass a list of libraries to merge several into one module, and `names={...}` to restrict generation to specific node groups.
 
+If your libraries mix tree types, use `generate_asset_modules` instead — it takes a directory and writes one module per tree type (`geometry.py`, `shader.py`, `compositor.py`), skipping tree types with no assets:
+
+``` python
+from nodebpy.assets import generate_asset_modules, PackageLibrary
+
+generate_asset_modules(
+    PackageLibrary(__file__, "data/my_assets.blend"),
+    "my_addon/nodes/",
+)
+```
+
+Because asset names repeat across editors, splitting also keeps the generated class names collision-free where a single mixed module would silently shadow one tree type’s class with another’s.
+
 The generated module imports from `nodebpy` and looks like any other node module, so import and use it directly:
 
 ``` python

assets.llms.md

@@ -1,6 +1,43 @@
 # Changelog
 
-## v520.5.0 - 2026-06-16
+## v520.7.0 - 2026-07-16
+
+### Enhancements
+
+- **Per-tree-type asset modules** — `nodebpy.assets.generate_asset_modules(libraries, output_dir)` splits the generated asset classes into one module per tree type (`geometry.py` / `shader.py` / `compositor.py`), writing only the tree types that have assets. Asset names repeat across editors (a geometry *and* a compositor “Combine Spherical” both exist), so splitting keeps the generated class names collision-free where a single `generate_asset_api` module would silently shadow one with the other. The CLI splits the same way when the output is a directory:
+
+``` sh
+python -m nodebpy.assets -b my_assets.blend -o my_addon/nodes/
+```
+
+## v520.6.0 - 2026-07-15
+
+### Enhancements
+
+- **Blender 5.2 stable** — `bpy` now tracks the final 5.2 release (CI no longer installs daily builds); the node classes and bundled-essentials asset APIs were regenerated against it. The `SetAttachmentSurface` asset was removed upstream and is no longer generated.
+
+### Fixes
+
+- `to_python` export now preserves a `Value` node’s number. The editable value lives on the node’s *output* socket, which the generic constructor path never examined, so non-default values were silently dropped from the generated code.
+
+## v520.5.2 - 2026-07-07
+
+### Internal
+
+- Documentation cleanup.
+
+## v520.5.1 - 2026-07-07
+
+### Enhancements
+
+- **Interactive graphs in docs / notebooks** — a `TreeBuilder` now displays as an interactive, Blender-styled, pan-and-zoomable node graph in Jupyter and Quarto (via `_repr_html_`, backed by the new `nodebpy.web_render` module using `tree_clipper` and the `geonodes-web-render` web component). Falls back to the existing Mermaid diagram when rendering isn’t available.
+
+### Fixes
+
+- `to_python` export: a single link into a multi-input socket is now emitted as a one-element tuple, since the manual classes (`JoinGeometry`, `MeshBoolean`, …) expect an iterable — previously such trees didn’t round-trip. Unary float/integer math socket methods also emit Blender’s zero-padded socket identifiers (`Value_001`).
+- Regenerated the bundled asset APIs with upstream label fixes — e.g. `cip_start` → `clip_start`, `animated_` → `animated`, and the “Super 8 mm” film-grain preset spelling.
+
+## v520.5.0 - 2026-06-19
 
 ### Enhancements
 

changelog.html

@@ -7,7 +7,7 @@
 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
 
-<title>nodebpy 520.6.0</title>
+<title>nodebpy 520.7.0</title>
 <style>
 /* Default styles provided by pandoc.
 ** See https://pandoc.org/MANUAL.html#variables-for-html for config info.
@@ -77,7 +77,7 @@
 <link href="site_libs/quarto-html/quarto-syntax-highlighting-dark-0a6b7249c26820e032cb0bd839ff02b1.css" rel="stylesheet" id="quarto-text-highlighting-styles">
 <script src="site_libs/bootstrap/bootstrap.min.js"></script>
 <link href="site_libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
-<link href="site_libs/bootstrap/bootstrap-328b4c1962c9a5575e7328ba9c647c56.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="dark">
+<link href="site_libs/bootstrap/bootstrap-da754bb905dfff91d967e43b5e6004aa.min.css" rel="stylesheet" append-hash="true" id="quarto-bootstrap" data-mode="dark">
 <script id="quarto-search-options" type="application/json">{
   "location": "navbar",
   "copy-button": false,
@@ -169,7 +169,7 @@
       <div class="navbar-container container-fluid">
       <div class="navbar-brand-container mx-auto">
     <a class="navbar-brand" href="./index.html">
-    <span class="navbar-title">nodebpy 520.6.0</span>
+    <span class="navbar-title">nodebpy 520.7.0</span>
     </a>
   </div>
             <div id="quarto-search" class="" title="Search"></div>
@@ -294,7 +294,7 @@ <h2 class="anchored" data-anchor-id="creating-nodes-with-code">Creating Nodes Wi
 <blockquote class="blockquote">
 <p>A text-based version of nodes should bring the convenience of writing code with IDE auto-completion, type hinting, with overall compactness and readability, while staying as close as possible to what building a node tree via the GUI feels like.</p>
 </blockquote>
-<div id="89423d36" class="cell" data-execution_count="1">
+<div id="dbefde13" class="cell" data-execution_count="1">
 <div class="code-copy-outer-scaffold"><div class="sourceCode cell-code" id="cb2"><pre class="sourceCode python code-with-copy"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="im">from</span> nodebpy <span class="im">import</span> geometry <span class="im">as</span> g</span>
 <span id="cb2-2"><a href="#cb2-2" aria-hidden="true" tabindex="-1"></a></span>
 <span id="cb2-3"><a href="#cb2-3" aria-hidden="true" tabindex="-1"></a><span class="cf">with</span> g.tree(<span class="st">"AnotherTree"</span>, collapse<span class="op">=</span><span class="va">True</span>) <span class="im">as</span> tree:</span>
@@ -428,7 +428,7 @@ <h2 class="anchored" data-anchor-id="design-considerations">Design Consideration
     }
       var localhostRegex = new RegExp(/^(?:http|https):\/\/localhost\:?[0-9]*\//);
       var mailtoRegex = new RegExp(/^mailto:/);
-        var filterRegex = new RegExp("https:\/\/BradyAJohnston\.github\.io\/nodebpy\/");
+        var filterRegex = new RegExp('/' + window.location.host + '/');
       var isInternal = (href) => {
           return filterRegex.test(href) || localhostRegex.test(href) || mailtoRegex.test(href);
       }