ietf-tools / ietf-tools/dev-planning-dispatch

Build front end at Red for surfacing surveys (popover + link-out)

Open
#30 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Red's survey surface — link-out only. Red never authors surveys or captures results (that is Pink/SurveyJS); Red only surfaces open surveys and links out.

Two entry points, both built on the shared engagement-popover component (also used by the route-to-participation prompt):

  • Auto popover: after a short delay (~10s), fetch the list of open surveys from Pink's open-surveys API (the list may differ for signed-in vs anonymous visitors) and show a dismissible popover linking out to a survey on Pink's SurveyJS instance. Track taken (clicked) and dismissed survey ids in localStorage so the user is not re-shown them.
  • Header-nav button → modal listing the full set of open surveys, unfiltered by taken/dismissed.

Each survey item: id, title, description (if available), link. Works for anonymous and signed-in visitors (the list just varies). Reuses the shared engagement popover rather than building a new one.

Estimate: 3–5 pts (range).

Depends on Pink's open-surveys API shape being agreed.

Contributor guide

Open the 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.

Research direction

Start with the shared engagement-popover component and the existing route-to-participation prompt, then inspect the open-surveys API contract once Pink's shape is agreed. Implement the delayed auto popover and header-nav modal for anonymous and signed-in visitors, using localStorage for taken and dismissed survey IDs. Done means both entry points list open surveys correctly, link to Pink's SurveyJS instance, support dismissal, and reuse the shared component.

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
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.