Unify navigation across the web app
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Review the existing navigation flows across the web app and read related issue #408 on menu drawer design. Define a coherent approach for moving between areas, returning to higher-level pages, and showing the current location; done means the approach is agreed across the app.
Written by the indexing model from the issue text.
Description
Problem
Navigation in the web app varies depending on the current page. Moving to another area of the app or returning to a higher-level page within the same area is handled differently across pages, which can be confusing and difficult to discover.
Desired outcome
Develop a unified navigation concept that makes it clear and consistent how to:
- Move between areas of the app.
- Return to a higher-level page within the current area.
- Understand the current location in the app.
Review the existing flows and define a coherent approach across the web app. The specific UI design is open for discussion.
Related: #408 (menu drawer design).
- Dominant language
- Java
- Stars
- 16
- Forks
- 5
- Avg merge
- 14h 45m
- Merged PRs (30d)
- 25
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from CodeForPhilly/benefit-decision-toolkit
-
documentation Good for newcomer quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#519 ·
Maintainers usually reply within 1 day
-
documentation quick win
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/benefit-decision-toolkit#445 ·
Maintainers usually reply within 1 day
-
Make issue templatesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CodeForPhilly/benefit-decision-toolkit#425 ·
Maintainers usually reply within 1 day
-
Update docs screenshots to reflect new navigation design and use the actual in-app example screenerOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
CodeForPhilly/benefit-decision-toolkit#528 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CodeForPhilly/benefit-decision-toolkit#524 ·
Maintainers usually reply within 1 day
All issues in CodeForPhilly/benefit-decision-toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
beehive-lab/TornadoVM#1151 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
FasterXML/jackson-dataformats-binary#823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day