Guide
The Guide section explains how to use VibeFlui features together in application screens.
Use this section after reading the schema and registry foundations. The pages here focus on practical usage: how a schema connects to providers, actions, feedback, forms, tables, layout configuration, and theming.
What this section covers
| Area | Purpose |
|---|---|
Providers And Endpoints | Configure static data, server-backed data, endpoint behavior, provider response contracts, query state, and submit flow. |
Actions | Configure built-in and custom actions for create, edit, delete, row actions, bulk actions, submit actions, handlers, endpoints, confirmation dialogs, permissions, and feedback messages. |
Feedback | Understand how VibeFlui resolves operation feedback from response status, messages, modes, table states, form submission, and action results. |
Forms | Configure form fields, validation, options, conditional fields, layout groups, tabs, wizard flow, submit behavior, computed values, transformations, value mapping, custom fields, and adapters. |
Tables | Configure table columns, data binding, static and server modes, search, filters, sorting, pagination, row actions, row selection, bulk actions, export controls, column visibility, persistence, states, widths, scrolling, styling, and renderers. |
Layout | Organize schema-driven screens with root layout, form layout, detail layout, dashboard layout, grids, groups, sections, surfaces, tabs, wizard steps, multi-resource layouts, widths, and theme slots. |
Theming | Configure theme values, class name slots, class name resolvers, class name conditions, variants, presets, adapter theme behavior, merge strategy, and color mode. |
How to read this section
Start with providers if the page needs data loading or submit behavior. Continue with forms, tables, and actions based on the UI surface you are building. Use feedback and theming once the screen behavior is clear.
For advanced customization, keep schemas declarative and place runtime functions, React components, handlers, adapters, and resolvers in the registry.