Application shell
index.html is the document shell and App.xu is the root Xuda UI mounted into it.
Xuda CLI
Xuda CLI is the path for application-level work. You author `App.xu`, `components/`, `globals/`,
`data/get/`, `data/set/`, `tables/`, `routes/`, and the rest as explicit source units. The CLI compiles
them into the runtime document model in node_modules/.project_data, serves the app locally, and
can sync with cloud docs when an api_key is present.
The root app lives in App.xu. Feature screens go under components/. Shared state
belongs in globals/. Reads and writes live in data/get/ and data/set/.
Tables, routes, alerts, API units, script units, and AI agent resources all get their own homes.
index.html is the document shell and App.xu is the root Xuda UI mounted into it.
Each concern gets a named source unit: component, globals, get_data, set_data, batch, api, javascript, alert, table, route, or ai_agent.
xuda-cli dev compiles your source into node_modules/.project_data/, which is the canonical runtime doc folder.
UI, reads, writes, alerts, tables, and routes stop competing for the same file.
Humans and AI tools can learn the app structure from the folder layout and docs without reverse-engineering a single large program file.
The CLI still compiles into the runtime doc model and can sync with remote docs instead of inventing a disconnected parallel system.
The CLI docs can be published as rendered HTML and raw markdown, which helps developers, crawlers, and AI systems alike.
This page is the high-level overview. The technical site covers the full CLI mental model, runtime flow, project layout, generated docs, source-to-runtime compilation, and each building block in detail.