Screen: a member's page

Open
  • Is something wrong?
#129 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
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Read the Member page in the shared design/screens.html and design/wireframes.html files first; they are not in the repository. Then inspect the screens and implementations for dependencies #116, #101, #102, #61, and #67. Done means /members/$userId is read-only, shows the comparison sentence, their curve against yours, and every holding, while your own page is your Portfolio.

Written by the indexing model from the issue text.

Description

good first issue

/members/$userId, read-only.

Coverage checklist

  • Header sentence comparing with you, their curve against yours, every holding
  • Your own page is your Portfolio

Depends on

  • #116
  • #101
  • #102
  • #61
  • #67

Read first

  • Screens: design/screens.html and design/wireframes.html (kept outside git, shared separately) › Member page

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.