How to contribute
You will need a GitHub account, if you do not already have one click here to sign up.
Small online edits
To make a small edit follow these steps:
- At the top of every tutorial (like this one where it says 'Click here to edit') there is a link to the document's source, click it and you will be taken to the GitHub website where the document is held.
- At the top of the document's contents there is an edit button (see below), clicking will show a raw text version of the file.
- Make your changes to the file using the Markdown syntax (see this tutorial to learn Markdown)
- When you've finished editing you need to propose the changes, scroll to the bottom of the page to find the 'Propose file change' section. Simply write a short and optional extended description of the changes you made and click 'Propose file change.'
- And that's it!
The online edit button
Once your changes have been proposed, they will be reviewed by a 'docs-keeper'. If accepted, the changes will be added to the original document and will appear on the website within one or two days.
Large online edits
For more substantial edits which cannot be done in a single sitting:
- You will need to 'fork' (i.e. copy) the docs repo to your own GitHub account. Click the 'fork' button on the docs repo (found here). (Note, clicking the edit button automatically does this.)
- Once forked, the docs repo will be copied to a repository in your GitHub repositories.
- You can make changes to any files in this repository using the online edit button.
- Every change you make can be 'saved' by committing your changes to your copy of the repository in the 'Commit changes' section at the bottom of the page.
- You can add new documents by clicking the + symbol at the top of the repository page. Give the new file a name and the extension '.md'.
- Once you're happy with your changes you need to merge them with the original docs repo. Click the green compare button. This page will show how your version of the repo differs from the original repo. To merge your changes with the original, click 'Create pull request' at the top of the page.
- And that's it!
The fork button
The green compare button
Again, your changes will be reviewed by a 'docs-keeper' and if accepted will appear on the website within one or two days.
Offline editing
For more freedom, it's best to clone the docs repo to your local computer:
- Fork the docs repo to your own GitHub account.
- Clone the repo to your local machine:
git clone https://github.com/username/docs.git
- On your computer you can edit the files, add new files including image files.
- Commit and push your changes to your version on your Github account.
- For more details on using git, see the tutorial on git basics.
- Merge your changes by making a pull request!
Become a docs-keeper!
To edit files on the repo without the need for pull requests you will need to join the docs-keepers' team in the BES-QSIG GitHub account.
If you would like to contribute a lot and join the team, please email: dominic.john.bennett@gmail.com.
Anyone and everyone welcome!