This repository organizes overall documentation issues across the IPFS project.
We would love ❤️ your help to improve existing items or make new ones even better! We also have bounties available!
If you find something wrong within this repository, please raise an issue here →. Unless the issue is urgent, updates will be batch-merged into main on Tuesdays or Thursdays.
You can earn the undying love of the IPFS community and make some money by closing an issue with the bounty tag! Submissions must be production-ready and meet all the specifications listed on the issue page. Check out the current list of open bounties →
If you are attempting to close an issue, great! Thanks for the help! Please leave a comment within the issue requesting to be assigned to that issue before submitting a pull request. This minimizes the chance of multiple different contributors duplicating work by submitting pull requests for the same issue. If you submit a pull request to an issue without first being assigned to it, that pull request may not be accepted.
Everyone has an opinion when it comes to docs, and that's a good thing! Having folks from different backgrounds add to a discussion empowers everyone within that discussion. So if you've got something to add or would like to bring up a topic for discussion about the IPFS Docs project, please do so! Just create an issue using the kind/question tag!.
If you want to build this site locally, run the following:
-
Clone this repository:
git clone https://github.com/ipfs/ipfs-docs.git
-
Move into the
ipfs-docsfolder and install the NPM dependencies:cd ipfs-docs npm install -
Boot up the application in dev mode:
npm start
-
Open localhost:8080 in your browser.
-
Close the local server with
CTRL+c. -
To restart the local server, run
npm startfrom within theipfs-docsfolder.
- @johnnymatthews: Project leadership, organization, and primary contact
- @cwaring: Development support
All software code is copyright (c) Protocol Labs, Inc. under the MIT license. Other written documentation and content is copyright (c) Protocol Labs, Inc. under the Creative Commons Attribution-Share-Alike License.