Skip to main content
Batoi UIF Docs

Forms

Build governed forms with clear grouping, validation, review state, and submission output.

Version 3.0.0 Version 3 active maintenance Reviewed Aug 11, 2026 Next review Nov 11, 2026
Start Reading Open GitHub Report documentation issue

Owner: Batoi Engineering Reviewed by: Batoi UIF Maintainers Source revision: b2f3478

Start FastLoad UIF in server-rendered pages and initialize declarative behavior. Chart SupportReview native SVG chart types, Flint mappings, and deferred advanced charts. Micro AppsBuild contained app surfaces that live inside larger Batoi routes. AI and MCPDesign approval UI while privileged tool execution stays server-side.
Browse Batoi UIF Documentation Forms
On this page

Forms

Batoi UIF forms should make the workflow state visible.

A form is not just a set of fields. It should communicate what is required, what is optional, what will happen next, and what output will be created.

Structure

Recommended structure:

  • compact header
  • status badge
  • grouped fields
  • inline validation or guidance
  • preview panel
  • primary submit action
  • exportable submission packet

Validation

Client-side validation should guide the user before submission.

Production validation must also happen server-side.

Example

The Workflow Form example demonstrates:

  • required field checks
  • draft and submitted states
  • live review packet preview
  • JSON export