Skip to content

Latest commit

 

History

History
255 lines (199 loc) · 12.1 KB

CONTRIBUTING.md

File metadata and controls

255 lines (199 loc) · 12.1 KB
Raw

Contribute to the documentation

Thank you for your interest in contributing to the MetaMask developer documentation! These docs generally follow the Consensys docs guide. This page describes contribution guidelines specific to MetaMask, and refers to the Consensys docs guide in some places.

Table of contents

Contribution workflow

The MetaMask documentation contribution workflow involves proposing changes by creating branches and pull requests (PRs) on this repository. This facilitates open contributions, testing, and peer review.

To contribute changes:

  1. Search for an existing issue to work on, or create a new issue describing the content issue you'd like to address. Make sure no one else is assigned to the issue, and assign yourself to it. If you don't have permission to assign yourself to it, leave a comment on the issue.

  2. Clone this repository to your computer and navigate into it.

    git clone [email protected]:MetaMask/metamask-docs.git
cd metamask-docs

    Note: If you don't have write access to this repository, you must fork the repository to your personal account and clone your forked repository instead. Add an upstream remote to be able to pull from and push to the original repository.

    git clone [email protected]:<YOUR-USERNAME>/metamask-docs.git
cd metamask-docs
git remote add upstream [email protected]:MetaMask/metamask-docs.git

  3. Create and checkout a topic branch, naming it appropriately. We recommend including the issue number and a short description in the branch name (for example, 183-doc-cli-option), which is a reminder to fix only one issue in a PR.

    git checkout -b <ISSUE-NUM>-<ISSUE-DESC>

    Tip: You can use a Git client such as Fork instead of the command line.

  4. Open this repository in a text editor of your choice (for example, VS Code) and make your changes. Make sure to follow the style guidelines and format your Markdown correctly.

    Notes:

    • All documentation content is located in the wallet, snaps, services, and developer-tools directories.
    • If you add a new documentation page, edit wallet-sidebar.js, snaps-sidebar.js, services-sidebar.js, or dashboard-sidebar.js to add the page to the sidebar.
    • If you delete, rename, or move a documentation file, add a redirect.
    • See additional instructions for updating the interactive API reference.
    • If the PR contains a major change to the documentation content, add an entry to the top of the "What's new?" page.

  5. Preview your changes locally to check that the changes render correctly.

  6. Add and commit your changes, briefly describing your changes in the commit message. Push your changes to the remote origin.

    git add .
git commit -m "<COMMIT-MESSAGE>"
git push origin

  7. On this repository on GitHub, you’ll see a banner prompting you to create a PR with your recent changes. Create a PR, describing your changes in detail. Link the issue that your PR fixes by adding fixes #<ISSUE-NUM> to the PR description.

  8. Specific reviewers are automatically requested when you submit a PR. You can request additional reviewers in the right sidebar of your PR – for example, the original issue raiser. Make any required changes to your PR based on reviewer feedback, repeating steps 5–7.

  9. After your PR is approved by two reviewers, all checks have passed, and your branch has no conflicts with the main branch, you can merge your PR. If you don't have merge access, a maintainer will merge your PR for you. You can delete the topic branch after your PR is merged.

Preview locally

Preview the docs locally using npm or Yarn.

Style guide

Refer to the Consensys documentation style guide.

Add images

All images are located in the wallet/assets, snaps/assets, services/images, and developer-tools/images directories. When adding a new image, such as a screenshot or diagram, make sure the image has a white or #1b1b1d color background in order for it to be compatible with the site's light and dark modes.

Additionally, follow the Consensys guidelines on adding images.

Update the interactive API reference

The Wallet JSON-RPC API reference uses the docusaurus-openrpc plugin to import OpenRPC specifications from MetaMask/api-specs (MetaMask-specific methods) and ethereum/execution-apis (standard Ethereum methods). The site renders documentation for each method based on the specification, and displays an interactive module to test the methods in your browser.

Update MetaMask/api-specs

To update documentation for MetaMask-specific JSON-RPC API methods:

  1. Fork MetaMask/api-specs, clone the forked repository to your computer, and navigate into it:

    git clone [email protected]:<YOUR-USERNAME>/api-specs.git
cd api-specs

  2. Follow the repository's README.md instructions to edit the OpenRPC specification and generate the output file, openrpc.json.

  3. To test the API updates in the MetaMask doc site's interactive reference, make the following temporary changes on a local branch of the doc site, metamask-docs:

    1. Copy and paste the output file openrpc.json into the root directory of metamask-docs.
    2. In docusaurus.config.js, update the following line to point to your local output file: 
      openrpcDocument:
-  "https://metamask.github.io/api-specs/0.10.5/openrpc.json",
+  "./openrpc.json",
    3. Preview the doc site locally, navigate to the API reference, and view your updates.

  4. Add and commit your changes to api-specs, and create a PR.

  5. Once your PR is approved and merged, the following must happen to publish the changes to the MetaMask doc site:

    1. A new version of api-specs must be released by a user with write access to the repository. To release, go to the Create Release Pull Request action, select Run workflow, and enter a specific version to bump to in the last text box (for example, 0.10.6). This creates a PR releasing a version of api-specs.
    2. Once the release PR is merged, the Publish Release action must be approved by an npm publisher. You can request an approval in the #metamask-dev Slack channel tagging @metamask-npm-publishers. For example:

      @metamask-npm-publishers @metamask/[email protected] is awaiting deployment :rocketship: https://github.com/MetaMask/api-specs/actions/runs/10615788573

    3. Once the release is published on npm, docusaurus.config.js in metamask-docs must be updated with the new api-specs version to publish. For example: 
      openrpcDocument:
-  "https://metamask.github.io/api-specs/0.10.5/openrpc.json",
+  "https://metamask.github.io/api-specs/0.10.6/openrpc.json",

Update ethereum/execution-apis

To update documentation for standard Ethereum JSON-RPC API methods:

  1. Fork ethereum/execution-apis, clone the forked repository to your computer, and navigate into it:

    git clone [email protected]:<YOUR-USERNAME>/execution-apis.git
cd execution-apis

  2. Follow the repository's README.md instructions to edit the OpenRPC specification and generate the output file, openrpc.json.

  3. To test the API updates in the MetaMask doc site's interactive reference, make the following temporary changes on a local branch of the doc site, metamask-docs:

    1. Copy and paste the output file openrpc.json into the root directory of metamask-docs.
    2. In docusaurus.config.js, update the following line to point to your local output file: 
      openrpcDocument:
-  "https://metamask.github.io/api-specs/0.10.5/openrpc.json",
+  "./openrpc.json",
    3. Preview the doc site locally, navigate to the API reference, and view your updates.

  4. Add and commit your changes to execution-apis, and create a PR.

  5. Once your PR is approved and merged, the following must happen to publish the changes to the MetaMask doc site:

    1. api-specs must import the updated Ethereum API specification. Go to the commit history of the assembled-spec branch of execution-apis. Copy the full commit hash of the latest commit titled "assemble openrpc.json." Update the following line in merge-openrpc.js of api-specs with the updated commit hash, and create a PR: 
      const getFilteredExecutionAPIs = () => {
-  return fetch("https://raw.githubusercontent.com/ethereum/execution-apis/ac19b518a2596221cd7cd6421ee3dc654d7ff3b7/refs-openrpc.json")
+  return fetch("https://raw.githubusercontent.com/ethereum/execution-apis/f75d4cc8eeb5d1952bd69f901954686b74c34c9b/refs-openrpc.json")
    2. Once the change to merge-openrpc.js is merged, Step 5 in Update MetaMask/api-specs must be completed to publish the changes to the MetaMask doc site.

Test analytics

The docusaurus-plugin-segment plugin enables simple usage analytics to inform documentation improvements.

If you need to test analytics events in your local development environment, export the appropriate key for the environment you are testing against before building and running the project:

export SEGMENT_ANALYTICS_KEY="<your key>"

Then build the project in production mode using the following command:

npm run build && npm run serve