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

Nothing on a signup's page leads to the help page on closing and reopening

Open Beginner friendly
  • Is something wrong?
#654 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
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
accessibility, frontend

Research direction

Start with ClosedNotice and Banner in src/components/banner.tsx, then read ClosedNotice.test.tsx and the computer close test in tests/e2e/organizer.spec.ts. Add the help link to the closed notice in the same tab, preserving its current live region and focus behavior. Done means the unit test checks the link and URL, pnpm budgets passes, and the listed lint, typecheck, knip, and test commands pass.

Written by the indexing model from the issue text.

Description

enhancement pipeline:proposed pipeline:ux

Needs your OK: this adds a link to a help page in the grey Signup closed box, the first link from an organizer screen to a particular help page. Swap pipeline:proposed for pipeline:ready to have it built.

What happens

  • There's a help page for this. "Close or reopen a signup" (#650) says what closing does to the people signed up, to reminders and to the link, and how to reopen.
  • Nothing on the signup's page links to it.
    • Close signup's question (CloseSignupConfirm) doesn't. On a computer it's in the ⋯ panel, and on a phone in the More actions sheet.
    • The grey Signup closed box (ClosedNotice) doesn't either. Since #649 it shows only right after Close signup on that page.
    • Help in the header goes to the /help index.
  • No organizer screen links to a particular help page today. The only links to help are the header's and the footer's.
  • The walkthrough noted it. In the UX walkthrough on #610 it was a polish note.

Fix, in outline

  • Add a link to /help/close-or-reopen-a-signup in the grey Signup closed box, after its text: "How closing and reopening work".
  • Give Banner (src/components/banner.tsx) an optional link, rather than drawing a second box (CLAUDE.md: reuse banners). It takes only a title and a body today.
  • Open it in the same tab, so the browser's Back returns to the signup.

Watch for

  • Overlap with #587, which also proposes giving Banner an action slot, for the preview page. Whichever lands second should use the other's slot rather than add a second one.
  • Budgets. ClosedNotice loads on every signup tab, and those budgets were raised by 1 kB in #649. [id] and /edit are at 129.1 of 130 kB, so check pnpm budgets.
  • The box isn't a live region (live={false}), and its ✕ gives focus to the title. Keep both.
  • Tests: ClosedNotice.test.tsx, and the computer close test in tests/e2e/organizer.spec.ts, which checks the box.
  • Help page: "While it's closed" mentions the grey box. Nothing there needs to change, but run the help-pages skill's affected-articles.mjs on the diff.
  • CHANGELOG: add a line under Unreleased › Changed.

Choices this makes

  • In the box, not in Close's question. The question is a moment to decide, and a link there pulls people away from it. The box shows right after closing, when someone may wonder what happens next.
  • Same tab.
  • The words "How closing and reopening work".
  • Only this help page. Linking other screens to their help pages is a separate decision.

Done when

  • Right after Close signup, the grey box shows the link, and it opens /help/close-or-reopen-a-signup in the same tab.
  • A unit test in ClosedNotice.test.tsx checks the link and its address.
  • pnpm budgets passes.
  • pnpm lint && pnpm typecheck && pnpm knip && pnpm test pass.

From the UX walkthrough comment on #610 (https://github.com/richshaw/OpenSignup/pull/610#issuecomment-6402399737). Checked against ClosedNotice, CloseSignupConfirm and Banner on main at 1d4ff3a. https://claude.ai/code/session_01LrYa57fvbqWjZj89iH975K

Dominant language
TypeScript
Stars
19
Forks
4
Avg merge
20h 9m
Merged PRs (30d)
156

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 richshaw/OpenSignup

All issues in richshaw/OpenSignup

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.