Group
Description
Xuda Slim
Docs and mental model
Start here
Slim is still Xuda. It just starts from smaller inputs.
The fastest way to understand Slim is to stop thinking of it as a separate framework. It is the same Xuda
runtime you already know, but exposed in a lighter browser path that boots from HTML templates, inline
project_data, or plugin/runtime pages.
Boot modes
Slim is comfortable with three practical starts: HTML-authored templates, inline project_data,
and runtime/plugin pages that load the slim bundle and mount custom code. The important point is that all
three still end up inside the same session, datasource, and render machinery.
Minimal boot
new xuda(document.getElementById("app"), {
domain: "dev.xuda.ai",
prog_id: "demo",
project_data
});
Directive groups
The examples area is organized the same way: start with core state and output, then move through iteration, events, advanced runtime helpers, and finally special structural tags.
When to choose HTML vs project_data
Choose this when people are authoring by hand.
HTML mode is best for documentation, product pages, embedded marketing surfaces, and quick reactive prototypes where you want to stay visually close to the DOM.
Choose this when code or tooling owns the shape.
JSON mode is better when UI is generated, versioned, composed, or emitted by another layer of Xuda or your own build tooling.
Caveats and expectations
Slim is intentionally small, but it is not a completely separate product. Some directives are structural, some are runtime-heavy, and some are better documented than they are visually demoed. That is normal for a runtime layer that is meant to scale upward into larger Xuda programs.
Slim is plugin-free by default in this site. That is why
xu-ui-plugin, xu-multi-view,
and a few orchestration-oriented features are shown with careful notes instead of pretending they are simple
one-line DOM tricks.