ux: the homepage has no search field in the first screen; #search sits ~3 screens down again
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
Research direction
Start by reading the homepage layout and the catalog code that reads #catalog?q=…; the issue does not name specific files. Check how the catalog search state is populated, then identify where the hero or catalog controls can expose that search. Done when the field is visible without scrolling at 390 px and 1366 px widths and submitting a query shows filtered results.
Written by the indexing model from the issue text.
Description
Why it matters
A visitor who arrives with a need ("pixel tileset", "footstep sounds") should be able to search straight away. Right now the first screen has no search field. This is a regression of #26: the newer homepage sections pushed the catalog back down.
Evidence
#search sits at y≈2377 px on desktop (1366×800) and y≈3191 px on mobile (390×844), below the filmstrip, Starter stacks and Safe starting points.
Suggested approach
Add a search input to the hero that submits to #catalog?q=… (the same state the catalog already reads), or move the catalog controls above the editorial sections.
Done when
A search field is visible without scrolling at 390 px and 1366 px widths, and typing in it lands on filtered results.
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 15
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 TMHSDigital/Free-Game-Dev-Assets
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Free-Game-Dev-Assets#178 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Free-Game-Dev-Assets#176 ·
Maintainers usually reply within 1 day
-
copy: headline and README badge count 418 including 2 deprecated entries; the catalog shows 416Openbug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TMHSDigital/Free-Game-Dev-Assets#175 ·
Maintainers usually reply within 1 day
-
bug hardening priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#170 ·
Maintainers usually reply within 1 day
-
hardening priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TMHSDigital/Free-Game-Dev-Assets#169 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/Free-Game-Dev-Assets
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LucasSantana-Dev/Lucky#2945 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
brijeshb42/monaco-vim#175 ·
-
good first issue
Difficulty 2/5 3-5 days Newbie friendliness 62/100
paipai1999/POS-system#3 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MikeMcl/bignumber.js#418 ·