Skip to content


Repository files navigation

This is the source code to


See in-depth documentation and maintainance guides at the wiki.


Docker setup

Ensure that you have docker and docker-compose installed, along with GNU Make:


make serve

The website should now be available at

You can also build the site into _site:

make build

To automatically run the code formatter, ensure that prettier is installed, then:

make fmt

Manual setup (not recommended)

First, ensure that gem is installed.

Install bundle:

gem install bundle

Install required dependencies:

bundle install

Run jekyll server:

bundle exec jekyll serve

The website should now be available at


See for more information about contributing.


Source code is licensed under the Apache License, Version 2.0 - see the LICENSE file for details.

This does not apply to the contents of assets/, whose rights remain exclusively with their original copyright holders.

Copyright 2016-2022 CSS website contributors

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.


Adding new redirects

To manage a new redirect, then add it to _data/redirects.yaml, following the format of the entries that are already there.

This avoids needing to add files and folders everywhere, keeping the site cleaner.

Writing a new post

To create a new post, create a markdown file in _collections/news with the post content. You can see a template post already there to borrow from.

The filename should follow a precise format - to create this file from a shell:

touch \_collections/news/"$(date +%Y-%m-%d)-<title>.md"

You can add a thumbnail to a post; simply link the thumbnail in the front matter in the markdown file for the post. The thumbnail should be a 150px square for best results.

Calendar Events

The calendar events are accessed from the public CSS Google calendar also available here. They are accessed from the calendar using FullCalendar and an API key managed from the Google Cloud Console.

To add a new calendar event, a member of the CSS committee with access to the calendar must add a new event, and it will automatically appear on the website.

Event formatting

The event data displayed on the webiste is taken directly from the Google Calendar event. Some properties are extracted using XML-like tags from the event description - note that this does not imply that other XML tags are implemented, so no other tags aside from the ones specified here should be used.

Content Source
title the name of it appears on the calendar
date the date and time as it appears on the calendar
location the location as it appears on the calendar
description <desc></desc> tags in the event description, otherwise, the full event description, which may include other tags if used
facebook link <fb></fb> tags in the event description

Note that for the facebook event link, all matching <a></a> tags are then removed from the event description.

The time and date format used is chosen automagically depending on the times and dates given in the calendar event. The below table details the process:

Date Format Used when
DD MMM YYYY - DD MMM YYYY all day when the year changes
DD MMM YYYY HH:MM - DD MMM YYYY HH:MM time specified when year changes
DD MMM - DD MMM all day when month changes
DD MMM HH:MM - DD MMM HH:MM time specified when month changes
DD - DD MMM all day on different days in same month
DD MMM HH:MM - DD MMM HH:MM time specified on different days in same month
DD MM HH:MM - HH:MM same day

Updating the committee

To update the committee:

  1. Add the new committee's photos into assets/committee/full
    • Each image should have a 1:1 ratio.
    • Add the highest quality images you can (they'll be scaled down later).
    • Most common image formats are supported.
  2. Create all the additional files by running _scripts/ _scripts/assets/committee/2019-20 (it's a bash shell script).
  3. Create a new yaml file in _data/committee/ with these tags:
    • academic_year: The academic year of the committee, e.g. 2019/20
    • prefix: Prefix to the role of each member, e.g. "Outgoing Publicity Rep"
    • postfix: Postfix to the role of each member, e.g. "Publicity Rep Elect"
    • current: Display the committee on the main list page, true or false. All committees will always be listed in the archive
      • NB: this is now obsolete as each committee member has a start and end date
    • people: A list of committee members:
      • name: Name
      • pronouns: Pronouns
      • discordtag: Handle on Discord
      • flags: A list of flags they have. Defined in _data\committee-flags.yaml
        • Each committee member can have 0 or more flags assigned in a list. For example: flags: ["interim"]
        • interim: They were elected as an interim rep until the next EGM
        • outgoing: They are outgoing but still attending meetings / working
        • elect: They have been elected but are not necessarily attending meetings / working
      • role: Committee Role
      • picture: Picture
      • start-date: Date they started on the committee. Normally 1st of July for AGMs or the date of the EGM
      • end-date: Date they ended on the committee. If this tag is present they are put into the archive and are not shown in the /committee page
      • bio: >: Multiline Bio