Guides are short or long instructions on how to perform various tasks. They are written in Markdown for simplicity and maintainability. Github maintains a cheat sheet for Github flavoured Markdown on this link.
Each guide is a self-contained directory under the guides
directory, with a explanatory name. In that directory, there should at least be a .md
file with the same name. Images used in the guide, should be stored in the same directory.
Use this guide as an example of how to do it.
There are no rules on how long a guide have to be, but it should include what is needed to know, to perform a certain task. If the task is very complex, you can consider splitting the guide up in separate guides, that interlink.
Add link to guide in Guides
section in README.md. And add a link back to README.md at the top of the guide, to be on the safe side.
-
Use headers do divide the content.
- H1 - Main header -
# Main Header
- H2 - Sub header -
## Sub Header
- H3 - Paragraph header -
### Paragraph Header
- H1 - Main header -
-
Use table of contents, if guide won't fit screen without scrolling.
-
Use images where appropriate.
-
Link to other resources
- Link to Google -
[Link description](path/To/Resource)
- Link to Google -