Add translation support for form titles
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
### Description
The Web Forms currently translates question labels, options, hints, and constraint messages into the user's selected language. However, the form title remains untranslated, which can hinder user recognition and context before they begin filling out the form.
Translating the form title will:
- Improve user experience by making forms immediately recognizable in the user's language.
- Provide better context about the form's purpose or topic.

Maybe:
| form_title::English | form_title::Spanish | form_id | version | default_language
| -- | -- | -- | --| --|
| Farm Survey | Encuesta agrícola | 12345 | 20150101 | English
---
### Checklist
- **Does it need UI/UX design?**
- [ ] Yes. Describe the UI/UX requirements or attach a Figma link in the "Design" section.
- [X] No
- **Does it need API design?**
- [X] Yes. Specify the endpoints, methods, or data structures needed.
- [ ] No
- **Does it need design around state flow?**
- [ ] Yes. Outline the state flow requirements.
- [X] No
- **Does it need a test plan?**
- [ ] Yes. Add the test plan as a comment in this task or attach the document.
- [X] No
---
### User Stories
**As a data** collector,
**I want to** see the form title translated into my selected language,
**so that** I can quickly recognize the form's context and confirm it is the correct one.
---
### Design
- **Figma**: [Insert URL]
- **Design Docs**: [Insert URL]
---
### Dependencies
-
---
### Additional Notes
-
---
### Related Issues
-
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how Web Forms currently translates question labels, options, hints, and constraint messages, then identify where the form title and its language variants would enter the existing data flow. Define the required API data and behavior before implementation; done means the title is shown in the user's selected language, with suitable coverage for supported languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, internationalization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100