Datasource-first state
Fields, expressions, updates, and refresh behavior still flow through the Xuda datasource model. Slim is not a disconnected local-state toy.
Xuda Slim
HTML-first reactive runtime for plain pages
No template engine lock-in
Use Xuda as a lighter browser runtime for real reactive pages.
Xuda is the broader reactive runtime and platform behind widgets, panels, workflows, datasource-driven UI,
and embeddable applications. Xuda Slim is the browser-friendly layer that lets you bring that model into
hand-authored HTML pages or explicit project_data trees without booting the full project loader.
What Xuda is
Xuda is a reactive application runtime, and Slim is its lightweight browser face.
Think of Xuda as the engine for datasource-backed UI, expression evaluation, workflow events, panels, and embedded program composition. Slim is the part of that world that lets you bring those capabilities into a plain website without forcing a full framework stack around it.
Composable UI programs
Panels, child programs, special tags, and runtime orchestration still work. That matters when a small page grows into a more serious app.
Why Slim matters
Two authoring modes, one runtime contract.
Slim gives you two good ways to build. You can stay close to the DOM with HTML templates, or you can
generate and ship explicit progUi trees when you want tooling, code generation, or stronger
control over the shape of the UI.
Write normal-looking HTML and sprinkle in xu-* directives.
This is the closest path to Alpine-like authoring. It is ideal when you want fast experiments, documentation examples, or hand-tuned embedded experiences.
Use explicit project_data and progUi objects.
This is the better fit when pages are generated, stored, transformed, or composed programmatically from other Xuda tooling.
What you can build
Slim is comfortable in docs, landing pages, dashboards, and embedded products.
Standalone marketing pages
Use runtime directives for just enough reactivity without bringing in a larger client framework.
Embeddable widgets
Drop a Slim program into a product page, admin surface, or integration portal with a single runtime.
Generated UI
Feed project_data from docs tooling, Xuda Studio output, or your own code generation pipeline.
Explore next
Choose the example area that matches how you want to author.
Both areas cover the same Slim surface. The difference is the representation: one shows hand-authored HTML, and the other shows explicit JSON-style runtime trees.
HTML examples
See every directive in template-style authoring, with short explanations and live previews.
JSON examples
See the same runtime surface expressed as project_data and progUi so the authoring model stays explicit.