Xuda Slim
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.
xuda.io when you want the platform story.This site is for understanding how Xuda fits together: platform positioning, Slim examples, and how CLI compares to Slim before you drop into implementation details.
xuda.io/technical-docs when you want technical source docs.The technical docs site publishes the crawler-friendly HTML and raw markdown for Xuda CLI and Xuda Slim, so both developers and AI tools can work from the same documentation set.
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.
new xuda(document.getElementById("app"), {
domain: "dev.xuda.ai",
prog_id: "demo",
project_data
});
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.
Description
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.
JSON mode is better when UI is generated, versioned, composed, or emitted by another layer of Xuda or your own build tooling.
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.
xu-ui-plugin and a few
orchestration-oriented features are shown with careful notes instead of pretending they are simple one-line
DOM tricks.