24
Architecture

Lifecycle

Follow a FormForge form from definition to automation.

The lifecycle

Define the form

Write the form schema in Laravel or edit it through the builder.

Save a draft

Store the current definition without exposing it publicly yet.

Publish the form

Make the current revision available to the renderer and the HTTP API.

Render the form

Load the published schema in the Nuxt client and present it to end users.

Validate the submission

Run server-side validation before persisting the response.

Store the response

Keep the submission, files, and metadata in the backend.

Trigger automations

Dispatch post-submit handlers, exports, or follow-up workflows.

Package split

StageBackendClient
DefineDSL, revisions, lifecycle settingsBuilder UI
PublishStored revision and public metadataSave/publish orchestration
RenderSchema source of truthRenderer, progress, navigation
SubmitValidation and persistenceForm state and submit UI
OperateExports, automation, retentionStandalone workflows and admin UI
If you need a single screen to do everything, use the builder or renderer in standalone mode and keep orchestration outside the component tree.