Architecture
Architecture
Understand how the backend and client fit together around one shared form system.
FormForge has one core rule: the backend owns the schema and the client consumes it.
That split keeps behavior deterministic. The backend decides what a form is, how it evolves, and what the server accepts. The client decides how the form looks, how users move through it, and how editors orchestrate it in custom screens.
What belongs where
- Backend owns schema definition, validation, publication lifecycle, ownership, public links, response storage, and automation.
- Client owns rendering, builder interactions, progress, navigation, standalone orchestration, and custom UX.
- Shared schema connects both packages through the same contract.