Find file
94 lines (67 sloc) 2.63 KB

Build Status

Please log any issues.

Any editorial questions: Laura Gill or Simon Tennant can help

Contributing new content and updates

  • Fork the code to your own git repository.
  • Make your changes in /content/pages or directly in GitHub.
  • When you are happy with your updates, submit a pull request describing the changes.
  • IMPORTANT :- Before sending a Pull Request make sure that your forked repo is in sync with the base repo.
  • The updates will be reviewed and merged in.

Communication forum

Please use for discussions about the site, content, generation etc.

Site generation

Gentle introduction to Pelican

Pelican's QUICKSTART page is a good place to learn about the basics of Pelican (installation, project skeleton, development cycle, etc.).

Installation instructions

git clone ssh://
# install Pelican and dependencies


  • Pelican 3.3
  • ghp-import
  • Markdown 2.3.1

Runing the server in development mode

make serve

If you want the server to autoreload whenever a file change, you can instead do:

make devserver

View at http://localhost:8000


  Makefile (development configuration) (production configuration)
    <generated files - published to gh-pages branch>
      <website page files>
    <website theme>

Site generation

To just generate a new version (without starting up a local webserver) just do:

make html

Theme development

You can modify the theme (layout and styling) in the directory.

Make changes to Sass files, not compiled CSS.

npm i then run grunt to compile Sass.