Digitalization of Forms — From Static Documents to Dynamic Experiences
Replacing static, document-based forms with a dynamic, schema-driven forms platform — validated, accessible, and reusable across brands — built alongside our Principal Engineer.
Context
Across the platform, many forms still lived as static documents or one-off, hand-built implementations. Each new form meant repetitive engineering work, and changes were slow to ship.
Problem
Static and bespoke forms share the same costs: no shared validation, inconsistent accessibility, duplicated UI, and tight coupling to engineering for every field change. Content and marketing teams couldn’t iterate, and quality varied form to form.
My Role
- One of the two primary engineers driving the initiative, alongside our Principal Engineer
- Helping shape the architecture for schema-driven, reusable forms
- Leading frontend implementation and the shared field component library
Approach & Key Decisions
Treat a form as data, not as a hand-coded layout: a single schema describes fields, validation, and behavior, and the platform renders and validates from that source of truth.
Schema-driven foundations
- Zod schemas as the single source of truth for shape and validation
- React Hook Form for form state, performance, and validation wiring
- Contentful to configure and compose forms without code changes
- A reusable, accessible field component library shared across brands
Goals
- Consistent validation and accessibility by default
- New forms created and changed without bespoke engineering
- Reusable across brands from a single platform
- Less engineering toil and faster iteration for content teams
Why This Matters
Forms are critical data-capture and conversion surfaces. A platform approach makes them reliable and accessible by default, while freeing engineering from routine form work.