Add a "Who is Using" section
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- web-dev
Research direction
The issue body names no files, tests, entry points, content, or acceptance criteria. Start by inspecting the website structure and clarify what the “Who is Using” section should contain, where it should appear, and how it should be verified as complete.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 dependents/dependents.github.io
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in dependents/dependents.github.io
Similar issues
-
Panic on live viewport resize when unstyled elements exist in display: none subtreePossibly taken @GoCoder7 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DioxusLabs/blitz#1488 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
brave/adblock-lists#3068 ·
Maintainers usually reply within 1 day
-
Art style modal: show the character avatars it reads, and name them in the Use references buttonOpenenhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Refit MenuOpen(RFE) Enhancement Refit Project
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MegaMek/mekhq#10934 · 1 comment ·
Maintainers usually reply within 1 day