We've done our best to make the barrier of entry to contributing code to Protocol as low as possible. You can even do a lot of stuff directly through GitHub without actually installing Protocol locally, but if you want to do any complex coding work you'll eventually need to set up a local development environment.
- You'll need a GitHub account.
- You'll need to install Git.
- You'll need to install Node and npm.
With those prerequisites met:
- Fork the Protocol GitHub repository to your personal account.
- Clone that remote repo to your computer.
- On your computer’s command line, navigate to the folder to which you just cloned the Protocol repo.
- Within that folder, run
npm start. This will install all the dependencies and launch a local server.
You now have a local instance of the Protocol site running on your computer. You can load the site in a browser at http://localhost:3000. As you edit files they will update automatically and you can see your changes "live" on your local development environment.
- Make whatever edits you need to make, ideally in a fresh branch.
- When you're done, commit your changes and push them to your GitHub remote repository.
- Submit a pull request from your fork to the Mozilla repo.
You can also make some edits directly on github.com without installing the site locally. For that you don't even have to install Git or Node, you just need a GitHub account. This is fine for updating docs or minor tweaks that don’t need extensive testing or review, but for any serious coding you really should have a local instance running so you can see your work as it progresses.
Requesting New or Updated Components
If you would like to request changes to a component or a new component be added to Protocol, please submit an issue on Github using the appropriate issue template. Please make sure to fill out this template as thoroughly as possible, as this will help the team triage effectively.
To report an error you’ve discovered in Protocol, submit an issue on Github with a detailed description of the error and steps to reproduce. If possible, include a link to a live example and/or a screenshot of the bug in effect. Also be sure to mention the browser (and version) and operating system.
You should search for similar issues in case it’s already been reported. In some cases a bug may have been fixed but the fix may not have been deployed, so it’s a good idea to search through closed issues as well.