Forms

A Nebula form is an edit screen: a sticky action bar with Save, Back and Delete, fieldsets of typed fields, client-side validation, and a native POST to a save controller. You describe it in one JSON file. For flat tables the form mounts itself on the controller's route; for EAV entities it is mounted from layout XML.

Page	What it covers
Your first form	An edit form for a custom table, with its data provider and save controller
Form examples	Twelve worked examples adapted from the forms Nebula ships, in the shape a working file has
Form reference	Every key the engine reads: settings, buttons, fieldsets, fields, the 17 field types, layout trees
EAV forms	Product, category and customer forms driven by attribute metadata
Saving and validation	What is posted, where, how it is validated, and the save pipeline
Extending a shipped form	Adding a field or a section to a form Nebula ships

Field types

text, textarea, number, email, password, select, multiselect, toggle, checkbox, date, datetime, hidden, color, file, image and wysiwyg. Each has a template and an Alpine component, and each is documented with an example in the Form reference. A module can add its own; see Extension points.