Verified
project_data authoring
Build the Xuda runtime tree explicitly as data, for a generator or deterministic output.
Slim can also be authored from explicit runtime JSON. In this mode your code builds the same program shape the Xuda runtime already consumes, useful when another system owns the UI tree or the page should be generated deterministically.
Instead of writing:
you build the node tree directly:
Mounting it
The shape
When JSON authoring is the better fit
Use it when a builder or code tool generates the program, you want exact control over node ids and
structure, or you are teaching the runtime shape itself. It is also the fastest way to understand
what the CLI's compiler emits behind the scenes: .xu files ultimately
compile to this same document model.