ietf-tools / ietf-tools/dev-planning-dispatch
Implement the UI telling users about notifications on the website
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Build the on-site notifications UI: a header bell plus a notifications panel showing the signed-in user's notification items fetched from Pink. Client-side enhancement, signed-in only (bearer via getAccessToken); handle empty/loading/error states, and read/seen if supported. Includes design and build (no separate design card). Accessible; SSR-safe (client-side, absent from the cached anonymous HTML).
Estimate: 3–5 pts (range).
Contributor 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.
Research direction
No files or tests are named. Start by locating the website's client-side entry point and the existing getAccessToken and Pink integration; confirm the notification response and whether read/seen operations are supported. Done means signed-in users can access an accessible bell and panel with loading, empty, error, and notification states, while anonymous cached HTML remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100