FormForge Client

Standalone Usage

External save, publish, and preview patterns for FormForge Builder and Renderer.

Standalone usage keeps the FormForge UI but moves orchestration out of the component tree.

Use it when you want to:

save or publish forms from your own toolbar
hide the settings tab for system-owned forms
auto-publish every save for a specific workflow
keep a renderer preview aligned with the currently selected builder block
generate tenant-aware public links from the backend

What standalone means

the builder can expose save and publish methods through a component ref
the builder can hide its settings tab without persisting that choice in the backend
the renderer can show progress, previous, next, and submit controls in simulation mode
the backend can resolve public_url at response time through a request-aware resolver

Use standalone mode for orchestration, not for a different schema format. The same FormForge schema still powers the builder, the renderer, and the backend APIs.

Guides

Standalone builder

Expose save and publish actions outside the builder component.

Standalone renderer

Keep progress and navigation visible while you preview one block at a time.

Public links

Configure a resolver that generates tenant-aware public_url values.

Testing and FAQ

Development commands, test focus areas, and quick answers.

Standalone Builder

Use the builder UI while handling save and publish actions from your own screen.