If you want to do more than the occasional editing, you'll soon
realise GitHub's editor and preview are too limited. It's better to
work locally on your computer.
All you need to work locally is a [Git client](http://git-scm.com/).
[Clone the repository](https://help.github.com/articles/fork-a-repo/#step-2-create-a-local-clone-of-your-fork)
and start coding right away.
At some point, you will need to preview your work, but pushing to
GitHub each time you want to preview is clumsy. Your best option is to
[install Jekyll and the required dependencies](https://help.github.com/articles/using-jekyll-with-pages/#installing-jekyll)
on your machine. It is recommended to install the
[GitHub pages gem](https://github.com/github/pages-gem) which provides
you with the exact same versions used by GitHub to compile your site.
If you already have Ruby, the install part should be as easy as
~~~
gem install github-pages
~~~
Note that you will need Ruby headers (`ruby-dev` package on Ubuntu) in
order to compile C dependencies.
On OS X, you can just type `sudo gem install github-pages`.
Now you can `cd` into your local clone of the repository and launch
the compilation by
~~~
jekyll serve -w -b''
~~~
Your site will be generated in a `_site` sub-directory, and served
live at <http://localhost:4000/>. Any changes to the sources will
trigger an automatic recompilation!
Have fun!
We collect and develop planning/outreach documents here. They may turn into the beginnings of a web site soon. As we will probably want to use jekyll for that, we will already put the documents into Markdown and YAML.