When the page is still the natural source of truth.
Best for docs, product pages, embedded widgets, lightweight internal surfaces, and experiments where hand-authored HTML matters more than app scaffolding.
Xuda
Start here
Decision guide
Choose Xuda Slim for page-first work, and Xuda CLI for app-first work.
Both paths sit on the same broader Xuda ideas. The right choice depends on whether you want to author near the DOM or author a fuller application as typed source units.
When the app deserves dedicated source structure.
Best for dashboards, panels, forms, CRUD flows, shared logic units, tables, routes, and teams that want explicit building blocks and generated runtime docs.
How to decide
Ask what kind of thing you are building first.
If it feels like a page
Start with Xuda Slim when your work is mostly HTML, content, and a small layer of reactive behavior.
If it feels like an application
Start with Xuda CLI when the product needs screens, logic units, persistence, app structure, and source generation.
If you need technical implementation docs
Go straight to xuda.io/technical-docs for repo-driven technical references aimed at both developers and AI tools.
Next moves
Use the path that matches the job in front of you.
Xuda Slim path
Start with the current overview, then open the Slim docs and the HTML/JSON examples to understand the runtime directives and authoring styles.
Xuda CLI path
Read the high-level CLI overview here, then jump into the technical documentation for building blocks, project structure, generation flow, and example apps.