codeforboston / codeforboston/docassemble-juvenilesealing
Provide a blank form to the petitioner at the start
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
We were wondering long ago how to deal with the fact that the petitioner will be asked all these questions and get such a simple form at the end. There are multiple concerns with that. We can deal with that by adding a second page where we show them the form, with the ability to download it if they want, and say why it is our tool will help. That gives them the opportunity to fill it out themselves if they want and to take away the unpleasant surprise they might otherwise have at the end.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or an entry point. Begin by locating the interview flow that first asks the petitioner questions and the form template or download action it produces. Done means a second opening page previews the form, offers a download, and explains why the tool helps.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100