Concepts
The ideas everything else builds on, each with a link to its full page.
The short version of how Scripting Nodes works. Each section links to the page that covers it in full.
One add-on per file
Each .blend file holds one add-on. Its name and settings are in the node editor's sidebar, in the Scripting Nodes tab. While you work, the add-on is installed and enabled in Blender like any other, so you can use it right away. See Add-on and files.
Node trees are files
An add-on is made of node trees. Each tree becomes one Python file (a module) of the add-on, so split them the way you'd split code: one tree per tool, or one for operators and one for the interface. The Files list in the sidebar sorts trees and scripts into folders, and each folder becomes a package of the add-on. See Add-on and files.
Three kinds of nodes
- Root nodes stand on their own: Operator, Panel, Menu, events. They become the classes and handlers Blender registers.
- Flow nodes do something when a flow reaches them: Print, Run Operator, Set Property, If/Else.
- Value nodes compute something: Math, Combine Strings, Blender data. Their code goes where their output is used.
See Flows and sockets.
Sockets
- Flow sockets (diamonds) set the order things happen in. Logic flows (white) start code Blender runs, like an operator's Execute. Program flows (gray) continue it. Interface flows (yellow) draw UI, like a panel's Draw.
- Data sockets (circles) pass values: text, numbers, vectors, Blender data, lists. Connecting two different types converts the value where it can.
See Flows and sockets.
Data
Properties store values in Blender data or on your operators, and show up as fields. Blender data and data paths read and change what's in the scene. Variables keep values while your add-on runs.
Functions
A node tree with inputs and outputs is a function, like a node group in Geometry Nodes. Call it from other trees to reuse part of a graph.
Scripts and assets
When something is easier to write in Python, add a script. Files your add-on needs, like images or .blend files, are assets that ship with it.
Live rebuilds
Every change to the graph rebuilds the add-on and reloads it a moment later. If something is wrong, the error shows on the node that caused it, and the last working version keeps running. See Live updates.
Export
When you're done, export the add-on as a zip. It works without Scripting Nodes, and the code inside reads like a hand-written add-on.