Merge pull request #39 from s-makin/test-branch

Add "getting started" guide

Author: degville

README.md

@@ -99,6 +99,8 @@ Update potentially outdated instructions, commands, or version numbers. These ta
 
 ## Further resources
 
+If you're new to GitHub and working on the command line, you may want to start off with our [getting started guide](getting-started/get_started.md). Even if you are running a Windows machine, you can start contributing using this guide.
+
 ### Community forum
 
 Our community forum is the hub for all things Open Documentation Academy. It includes our _Getting started_ guide and links to our weekly _Documentation office hours_, alongside  meeting notes, updates, external links and discussions.

getting-started/CLI_basics.md

@@ -0,0 +1,23 @@
+# Command line cheaty-cheats
+
+Working on the command line takes a little getting used to, but doesn't need too much practice to get comfortable with it.
+
+|||
+| -- | -- |
+| `cd <folder>` | Change directory down to `<folder>` |
+| `cd ..` | Go back up one directory level |
+| `ls` (or `ls -all`) | Lists all files (including hidden files) |
+| `touch <file name>` | Create an empty file called `<file name>` |
+| `rm <file name>` | Remove the file called `<file name>` |
+| `code <file name>` | Open the named file in VS Code |
+
+
+Although you can use the sequence:
+
+```bash
+touch <file name>
+code <file name>
+```
+
+To create and then open an empty file, if you use `code <file name>` directly without creating the file first, VS code will create the file for you. 
+

getting-started/get_started.md

@@ -0,0 +1,25 @@
+# Getting started as a contributor
+
+This set of guides is intended for anyone who wants to contribute more substantial changes to documentation (or on a more regular basis) using the Ubuntu command line. 
+
+For quick corrections to a page, it's perfectly fine to use the GitHub web interface instead! 
+
+## Prerequisites
+
+Before you start using this guide, you will need to set up [a GitHub account](https://github.com/), if you don't already have one.
+The GitHub documentation is rather good, if you get stuck or need any explanation of particular topics.
+
+## Getting your environment set up
+
+Where you start in this series will depend on whether you're using a Windows machine, or an Ubuntu one. If you're using Windows, start on Part 1. If you are running Ubuntu, or have a dual-boot system where one of your options is Ubuntu, feel free to skip Part 1 and go straight to Part 2. 
+
+1. [Getting started using Windows](start_with_WSL.md)
+2. [Install and configure git](install_git.md)
+3. [Working with git on the command line](using_git.md)
+
+## Optional steps
+
+1. [Set up Sphinx](setup_sphinx.md)
+   This applies if you are working on a project that uses Sphinx to render the documentation.
+1. [Command line cheat sheet](CLI_basics.md)
+   This reference will help remind you of the basic commands needed to work with files on the command line.