Instruct people how they can suggest topics for the HIG
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by locating the HIG introduction and the current guidance that refers readers to the GNOME HIG. Update that introduction so people are directed to discussions or issues for missing UX topics; done means the path for suggesting topics is clear.
Written by the indexing model from the issue text.
Description
Problem
At the moment we tell people that if a topic isn't covered, they should refer to the GNOME HIG. But this doesn't really help us figure out which UX topics are missing from the HIG
Proposal
In the introduction we should probably instead ask users to use either discussions or issues to start a conversation about UX topics so that we can eventually add those topics to the HIG
- Dominant language
- No language data
- Stars
- 22
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 elementary/hig
-
Needs Copy Needs Design
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
elementary/hig#61 · 2 comments ·
-
Needs Design
Difficulty 3/5 1-2 days Newbie friendliness 25/100
elementary/hig#54 · 2 comments ·
-
Update HIG themingOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
elementary/hig#53 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
elementary/hig#49 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
elementary/hig#48 · 1 comment ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mozilla/bedrock#17413 · 1 reaction ·
Maintainers usually reply within 2 days
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
github/copilot-sdk#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
drizzle-team/drizzle-orm#6418 ·
Maintainers usually reply within 4 days
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lirantal/discoprint#31 ·
Maintainers usually reply within 1 day