Skip to content
Verified

Overview and choosing a path

One reactive runtime, two ways to author it, both compiling to the same document model.

Xu is Xuda's code-first framework: a reactive runtime driven by xu-* HTML attributes, with no build step, no JSX and no virtual DOM required to get moving. You decorate real markup, and the runtime binds it to state.

There is one runtime and two authoring paths, and both produce the same thing.

The same document model, underneath

Both paths compile down to the document model the Xuda platform already runs. A Slim page, a CLI component and a Studio-authored component all go through the same HTML parser module, so a component built in one surface opens and runs in the others.

If you are undecided, start with Slim. The xu-* attributes you learn there are the same attributes the CLI's .xu files compile to, so nothing is wasted when you move up.

Not exclusive with Studio or the API

Studio, the CLI, Slim and the API all read and write the same project documents. A typical project mixes them: shape the app in Studio, then reach for the CLI or Slim for the parts that are easier to script than to click through. See Choose your path for how Xu fits next to Studio and the API.

What's in this part of the docs