Context
Twelve questions today and it will grow. The glossary and the contributor wall both have a search box; the FAQ does not, so finding a specific answer means reading every heading.
What to change
Files: faq.html, a new script, css/components.css
Requirements:
- Add a search box matching the glossary's, reusing
.wall-controls and .wall-search
- Filter on both the question and the answer text, not the question alone
- Show a count, and a clear message when nothing matches
- Hide non-matching
<details> rather than deleting them, so open state survives
- Announce the result count politely for screen readers
Acceptance criteria
How to verify locally
python3 -m http.server 8000
Then open http://localhost:8000.
Difficulty
Intermediate.
New here? Comment /claim on this issue and a bot will assign it to you. Then read CONTRIBUTING.md.
Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear. You can also come to a PR Debug Clinic (Oct 12 or Oct 21).
Context
Twelve questions today and it will grow. The glossary and the contributor wall both have a search box; the FAQ does not, so finding a specific answer means reading every heading.
What to change
Files:
faq.html, a new script,css/components.cssRequirements:
.wall-controlsand.wall-search<details>rather than deleting them, so open state survivesAcceptance criteria
How to verify locally
Then open http://localhost:8000.
Difficulty
Intermediate.
New here? Comment
/claimon this issue and a bot will assign it to you. Then read CONTRIBUTING.md.Stuck at any point? Comment here saying what you have tried and where it stopped working — that is not an admission of failure, it is how we find out the instructions were unclear. You can also come to a PR Debug Clinic (Oct 12 or Oct 21).