How FPR works and help popovers

Open
  • Is something wrong?
#142 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
documentation, frontend

Research direction

Read docs/product/user-stories.md under Help, then review the separately shared design/screens.html and design/wireframes.html at “How FPR works.” Implement the /help page and contextual ⓘ popovers with links to their sections; nothing should open automatically. The checklist defines completion, and work depends on #116 and #53.

Written by the indexing model from the issue text.

Description

good first issue

/help, and ⓘ next to the ideas that need it.

Coverage checklist

  • One page of short sections, each with its own link
  • ⓘ popovers link to their section
  • Nothing opens by itself

Depends on

  • #116
  • #53

Read first

  • Screens: design/screens.html and design/wireframes.html (kept outside git, shared separately) › How FPR works
  • docs/product/user-stories.md › Help

Track: Together · Kind: Screen · Size: S

Dominant language
JavaScript
Stars
0
Forks
0
Avg merge
43m
Merged PRs (30d)
23

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 Fringhian/fpr

All issues in Fringhian/fpr

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.