Contributing to This Wiki
Wiki content development is community driven, and your contributions are welcome!
NEAR uses Docusaurus for documentation. Please refer to their documentation for details on major structural contributions to the documentation.
For simple content changes you have 2 options
- Edit this page
- Create an issue and PR (Please create your branch from the issue you created)
How To Contribute
To contribute, you can use the Github repository: https://github.com/near/wiki. You can start editing any file by clicking "Edit this page" on any page in the wiki (you will need to sign up for Github to make changes).
Once logged in, you will be in the editor. The editor allows you to edit "Markdown" files - a special formatting used for this Wiki.
When you are done with changes, you can describe what have you done in the text field at the bottom.
The next step is to create a Pull Request (PR) that will inform Wiki editors to review your changes.
The Instant PR
This is the fastest way to submit content changes directly from the page where you notice a mistake.
Open any page in on this wiki
[ Edit this page ]button at the bottom of every content page
Make your edits to the document that opens in GitHub by clicking the ✎ (pencil) icon
Submit a PR with your changes and comments for context
Please check all links before submitting a PR. If you are adding a new page, please add it to the sidebar in the
For more information on working with the sidebar, please refer to Docusaurus documentation.
The Typical PR
This is the standard fork-branch-commit workflow for submitting pull requests to open source repositories
- Create an issue for your proposed changes.
- Create a branch from the issue.
- Checkout the branch locally and make your changes in the
Make sure all the dependencies for the website are installed:
# Install dependencies
Run the local docs development server
# Start the site
# Website with live reload is started
Docusaurus server started on port 3000
The website for docs will open your browser locally to port
Make your edits.
Check that the project builds correctly
# Start the site
Commit and push your changes. refence the issue you made in your commit message. e.g.
git commit -m "fix: #1234"
If you do not have permissions to push to the repo, you will need to fork the repo and submit a PR from your fork. Please refer to the issue you created in step 1 for context.
Assign a reviewer to your PR. For now this will be @humanman or @mrdevri
To add images to a page in the wiki, start by adding an image to the folder under
Then you can include the image in a page by typing the following:
![Alt text/description of the image](@site/static/img/image-name.png)
The above text is alt text inside a pair of
 that should explain what is in the image, followed by a pair of
() that have a link to the image in the images folder.
If you create a new page, or would like to change the title of an existing page you can edit the frontmatter in a page.
You can find it at the top of every
.md file, here's an example:
description: A guide to contributing to the wiki.
title: Contributor Guide
This tells browsers and search engines what content is on a page, and what each page is called. Every page should have frontmatter, to make pages on the wiki easy to find and share.
If you want to link to a definition in the glossary, you can use a markdown link:
In the above example, you put the word you're defining inside a pair of
, then you link the glossary page inside
() with a
# followed by the specific word you're linking to.
Images work the same way, but you use
@site/static/img/ instead of
If you want to flex your React skills, you can add a component to a page by changing the file extension from
.mdx. Reference the "Using JSD in Markdown" page of Docusaurus for more details.
This section is for terminology directly related to NEAR:
- NEAR should always be capitalized
- If a definition is in the glossary, link to it when you explain a detailed concept for the first time.
- When you use acronyms, define them the first time you use them in a page.
- In most cases, avoid future tense because it can be ambiguous.
- Headings should be title case.
- Add alt text to images so that screen readers can understand what is happening in a picture.
- Use active voice. Try to use active voice as often as possible, because passive voice can make a sentence ambiguous and hard to understand.
- Avoid listing future plans for a product or feature, in part because when a feature is implemented can be ambiguous, or the product may be cancelled before it ever releases.
- Use markdown (files ending in .md), and avoid using HTML snippets in markdown because HTML can make reading and editing documents in the wiki more complex.
- Be respectful.
For more information on style, please refer to Style Guide page of this section.