massgov / massgov/feature-requests
Figure out content or UX changes related to service more pages that have overly large numbers of "what you need to know" items.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We have some more pages that have large numbers of "What you need to know" items. This taxes the performance of the site and also is pretty bad for usability. We want to look at the examples where this is happening and decide what content or UX changes to make to give them a better solution.
Here are URLs:
https://www.mass.gov/massachusetts-law-about
What you need to know area, 178 items
https://www.mass.gov/courthouse-locator
What you need to know. 354 items
https://www.mass.gov/code-of-massachusetts-regulations-cmr
What you need to know. 175 items
https://www.mass.gov/justices-memorials
What you need to know 85 items
https://www.mass.gov/fact-sheets-on-infectious-diseases
What you need to know: 59 items
https://www.mass.gov/court-forms-by-topic
What you need to know. 42 items
https://www.mass.gov/court-rules-guidelines-and-standards
What you need to know: 42 items
https://www.mass.gov/jury-duty
What you need to know: 24 items
https://www.mass.gov/find-a-massachusetts-watershed
What you need to know: 27 items
https://www.mass.gov/massachusetts-courts-standards-on-substance-abuse
What you need to know: 23 items
https://www.mass.gov/smart-growth-smart-energy-toolkit-modules
What you need to know: 22 items
https://www.mass.gov/court-data-metrics-reports
What you need to know: 20 items
Reference
JIRA DP-8927
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 listed Mass.gov pages, starting with the "What you need to know" sections and their reported item counts. Compare the examples to identify the content or UX problems and document a decided approach for each affected pattern. Done means the affected pages and an agreed solution are clearly defined; the issue does not name files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, design, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100