[Discovery] - Break down Upload Document into multiple steps
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 23
- Avg merge
- 11m
- Merged PRs (30d)
- 4
Description
Note: This issue is marked for discovery. It is open for discussion and not necessarily decided upon.
Describe the Current Behavior/Feature:
Currently, the Upload Document modal contains every input and interaction on a single screen. This is completely functional but potentially could be made smoother, at least for smaller screens.
Rationale:
Users may prefer a workflow where fewer things are presented all at once. It would create more sections, but they would be less crowded and perhaps overwhelming. This is particularly a concern for trauma-informed design. As well as accessibility, since a large amount of smaller-sized items could be burdensome for the vision-impaired, and multiple inputs so close to one another increase the possibility of misclicking.
Proposed Changes:
Break down the existing modal into at least one additional step in order to more closely match the Figma design:
Possible Drawbacks:
Breaking up a working feature can be risky if not done carefully. Doing it may also prove unduly cumbersome.
Alternatives Considered:
Consider if there are other ways to reduce screen "busyness".
If we do decided to move forward with breaking down this modal, we may want to consider doing the same for other similar other modals.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current Upload Document modal alongside the linked Figma workflow and assess whether an additional step improves the experience on smaller screens. First clarify the desired flow and acceptance criteria through the open discussion; done would mean an agreed design and implementation scope, not just a speculative breakdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100