Architecture

FormGenerator stays slim: core owns shared field types. Feature modules own specialised question components and pass a small questionRenderers map when creating the form.

┌──────────────────────────────────────────────────────────┐
│  Page (YouthStarterOffer, PlayerDetails, …)              │
│    new FormGenerator(el, {                               │
│      questions,                                          │
│      questionRenderers: householdQuestionRenderers       │
│    })                                                    │
└────────────────────────────┬─────────────────────────────┘
                             │
┌────────────────────────────▼─────────────────────────────┐
│  FormGenerator                                           │
│    this.questionRenderers = {                            │
│      ...coreQuestionRenderers,   ← shared types          │
│      ...config.questionRenderers ← module overrides      │
│    }                                                     │
│    renderQuestion() → registry[questionType](…)          │
└────────────────────────────┬─────────────────────────────┘
                             │
        ┌────────────────────┼────────────────────┐
        ▼                    ▼                    ▼
   RadioComponent     SchoolFinder      HouseHoldMemberList
   (core)             (core)            (Household module)

Piece	Path	Role
`FormGenerator`	`components/FormGenerator/index.js`	Orchestration, steps, validation, answers
`QuestionTypes` / `FormTypes`	`components/FormGenerator/questionTypes.js`	Shared type string constants
`coreQuestionRenderers`	`components/FormGenerator/questionRenderers.js`	Map of core `questionType` → component factory
Household renderers	`pages/HouseholdAccounts/formQuestions/`	Module types + components kept with Household

Form types

Type	Constant	Behaviour
Step form	`FormTypes.StepForm`	One step visible at a time; final step submits
Section form	`FormTypes.SectionForm`	All sections on one page; submit visibility controlled by config