Define outline for contributor documentation for ideal package structure

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start with Mark's comment on Issue 28, then review the requirements in issue 53 for the contributor documentation outline. Done means a team-reviewed outline for ideal package structure, separate follow-up issues for each area, and those tickets added to the epic with points.

Written by the indexing model from the issue text.

Description

team-wallet-framework

This issue is for creating the outline of what would need to go into the contributor documenation around ideal package structure.

When creating the outline please see the comment from Mark on Issue 28

As part of this work please get feedback from team to finalize the outline and then create issues for filling in each of the areas of the outline. Please add the tickets to the epic and ensure they are pointed.

Dominant language
JavaScript
Stars
86
Forks
42
No merged PRs in 30d

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.

More from MetaMask/contributor-docs

All issues in MetaMask/contributor-docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.