Role & scope
I own and develop OpenForms as a solo project. The current implementation focuses on the API for creating, editing, and publishing forms. The product has not been released.
Form model
Forms store a draft schema and settings alongside a published snapshot. Draft revisions allow the API to reject stale edits rather than overwrite a newer version.
API design
The API implements owner-scoped form creation, listing, editing, and deletion, plus publishing and unpublishing. A public read endpoint retrieves a published form by its slug.
Validation
Server-side validation checks the form schema when saving a draft and applies publication checks before creating a published snapshot. This is form-definition validation; response validation remains planned.
Responses
Submission persistence and response review are planned. The current submission service is a scaffold, so the project does not yet provide a complete response-collection flow.
Architecture
The implemented backend uses NestJS, TypeScript, TypeORM, and PostgreSQL. A Next.js and Tailwind CSS frontend remains a proposed direction.
Roadmap
The next goal is to connect a form-building interface with publishing, submission storage, and response review.