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

UI/UX improvements

Open Beginner friendly
  • Is something wrong?
#73 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
accessibility, frontend

Research direction

Start with RootLayout in apps/web/src/router.tsx and inspect the overflow menu pattern in styles.css. Check the signed-in top bar at about 375px wide, then implement a way to reach Sign out within two taps without horizontal overflow. Done when that behavior works for a signed-in user on mobile.

Written by the indexing model from the issue text.

Description

enhancement

Umbrella issue for small UI and user-experience improvements. Each item can be picked up as its own branch/PR; tick it off here when it lands.

Checklist

  • Mobile: no way to sign out. On a phone-width viewport there is no reachable sign-out control for a signed-in user.

Details

Mobile: no way to sign out

The top bar in apps/web/src/router.tsx (RootLayout) renders Reports, Write, @handle, Settings and Sign out inline in one flex row. On narrow screens that row has no room, so the Sign out button (the last item) is pushed off-screen or squeezed out and can't be tapped.

Expected: a signed-in user on mobile can find and use Sign out.

Possible approaches:

  • Collapse the account links (handle, Settings, Sign out, and Reports for admins) into an account/overflow menu on small screens. The app already has an overflow-menu pattern in styles.css that could be reused.
  • Or add Sign out to the Settings page as a fallback.

Acceptance: at ~375px width, a signed-in user can reach Sign out in at most two taps, and the top bar doesn't overflow horizontally.

Ideas to add

Add further UI/UX items below as they come up.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
10h 51m
Merged PRs (30d)
48

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 dnerever/OpenRecipe

All issues in dnerever/OpenRecipe

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.