ietf-tools / ietf-tools/dev-planning-dispatch
Define when to provide the onscreen prompt
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Show the participation prompt after a short delay (N seconds), once ever per visitor — once shown or dismissed it never reappears (tracked in localStorage). Links out to a fixed external participation landing page.
Open: whether the trigger rules + landing URL are static client-side config in Red (assumed for the estimate) or fetched from Pink/an API. Static = no Pink dependency; dynamic = a light Pink-contract dependency.
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
Start by locating the Red client-side prompt entry point and deciding whether its trigger rules and landing URL are static configuration or fetched through Pink/an API. Define the short delay, once-ever display and dismissal persistence with localStorage, plus the fixed external destination; done means the prompt does not reappear after display or dismissal and the chosen dependency boundary is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100