Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Add keyboard shortcut navigation ('j'/'k' and arrow keys) for browsing directory cards

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
html
Domain
frontend, web-dev

Research direction

Start by locating the directory card rendering and the existing / search-bar shortcut in the web app UI. Add keyboard navigation for j/k and arrow keys, Enter to open the highlighted resource, and c to copy its URL, while leaving shortcuts inactive when the search input is focused; done means each behavior works consistently across the cards.

Written by the indexing model from the issue text.

Description

enhancement feature-request
Feature Name / Concept

Vim-style ('j' / 'k') and arrow-key card navigation

Area of Impact

Web App UI / UX (devshelf.ritualdev.in)

Problem or Opportunity

Power users and keyboard-first developers frequently visit DevShelf looking for tools without reaching for the mouse. We currently support / to focus the search bar, but navigating down through cards requires manual mouse scrolling.

Proposed Solution & Technical Details
  • When search input is not focused, pressing j or ArrowDown highlights the next resource card with an active cyan glow.
  • Pressing k or ArrowUp moves focus to the previous card.
  • Pressing Enter opens the highlighted item's repository / website in a new tab.
  • Pressing c copies the card URL directly to the clipboard.
Are you interested in implementing this?

Yes, I would love to open a PR for this!

Dominant language
HTML
Stars
3
Forks
3
Avg merge
1h 42m
Merged PRs (30d)
11

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RitualDev-Lab/DevShelf

All issues in RitualDev-Lab/DevShelf

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.