Skip to content
Snippets Groups Projects
Thomas Wood's avatar
Thomas Wood authored
Revert "Merge branch 'master' of https://gitlab.doc.ic.ac.uk/resource-reasoning/www-rw.doc.ic.ac.uk"

This reverts commit a9cf459f5da4fdccf215f3501dd04726cd796070, reversing
changes made to e6f81b0023b73c2e3556f761cc87fe4d6f53cf8b.
661165ba
History
layout: null

Program Specification & Verification Group Website: http://psvg.doc.ic.ac.uk/

Dependency Status

The source code for this site is hosted on the DoC GitLab server, you should have access to edit it if a member of the resource-reasoning group.

DO NOT EDIT THE SOURCE CODE IN /vol/rr/www, IT IS ALL REPLACED EACH TIME THE SITE IS REBUILT FROM VERSION CONTROL

Technical Detail

This website is built using the Jekyll website framework. Pages can be written using Markdown (preferred) or HTML. Files should be named with the extension they're writen in (.md, .markdown, .html, ...), they'll be compiled to .html versions of the file on publication. (Unless otherwise specified with the 'permalink' property of the page).

Pages to be interpreted by the Jekyll framework should be started with a YAML variable block. The variables here can be used to change properties of the page. For further details, see the Jekyll documentation. For example, to set the page title and it's URL:

---
title: Page Name
permalink: /my-custom-page-path/
---

Variables that templates currently take into account are:

  • title, sets the page title
  • menu, (default: false) places the page into the website's navigation menu

The main content of the page should then follow.

Any other files present in the directory structure (except for those prefixed with _, ., or explicitly excluded in _config.yml) will be published unchanged to the website.

Testing and Deployment

The DoC GitLab instance is configured (using .gitlab-ci.yml) to build, test and deploy the website on tests passing. The tests run are to check that the build works (no critical syntax errors in templates), and that internal page links are consistent.

An additional check that external links are still live is also run, but this test is permitted to fail without blocking the deployment.

The site is deployed to /vol/rr/www automatically on successful build.

Locally Building and Testing

If you wish to test the site locally, ensure you have ruby installed, and then initially run:

gem install bundler
bundle install

And to start a local webserver that remakes files whenever changed:

rake serve

You can test for dead links and html errors using:

bundle exec rake test