jduckles/2014-11-27-uct

Software Carpentry University of Cape Town, South Africa Software Carpentry Bootcamps ============================ This repository's `gh-pages` branch is the starting point for a bootcamp website: it contains a template for your bootcamp's home page and the shared lesson materials we have developed. The sections below explain: * how GitHub turns a repository into a web site, * how you can build a website for your bootcamp using this repo as a starting point, * which lessons we have, * where they're located, and * how to add new lessons. To contribute corrections or additions to this repository, see the contribution guidelines. You may also want to view these videos: * Setting Up a Software Carpentry Bootcamp Repository * Adding Lesson Material to the Software Carpentry Bootcamp Repository **Note:** If you are teaching Git in your bootcamp, you should create *two* repositories: one for your bootcamp's website, and one for learners to clone and update during your lessons. You should not try to use the same repo for both purposes because: 1. your website repo is probably going to be fairly large, and 2. you don't want a learner accidentally overwriting your lessons while you're trying to teach. **Table of Contents** * Background * Getting Started * Previewing the Site * Variables * Website Content * Lesson Material * Building Things * Site Map * FAQ Background ---------- There are a few things you need to know in order to understand why we do things the way we do. Most of them are specific to GitHub, rather than Git itself. 1. Git uses the term "clone" to mean "a copy of a repository". GitHub uses the term "fork" to mean, "a copy of a GitHub-hosted repo that is also hosted on GitHub", and the term "clone" to mean "a copy of a GitHub-hosted repo that's located on someone else's machine". In both cases, the duplicate has a remote called `origin` that points to the original repo; other remotes can be added manually. 2. A user on GitHub can only have one fork of a particular repo. …