Events

This page is about adding/managing the events section of the website.

Each event is represented by a markdown file in the _events folder. Each event can either be internal or external. An internal event will have a page on this website, generated from the details in the markdown file in the _events folder. External events are where you have an website elsewhere for your event, but want to list it on the AV Lab website.

You can also make an event series if you want a landing page for a series of events -- like a workshop or a set of talks. This just provides a little bit more structure for your pages.

The events page lists the upcoming and past events (and event series) in date order. Events that have passed will move from the 'Upcoming' list to the 'Past' list: after the event date has passed, and when the events page is recompiled by Jekyll. Recompilation can be triggered by editing events.md and committing the change to the master branch.

Adding an Internal Event

This adds an event to the events list and generates a page for the event.

To add a new page to the events section of the website, you need to make a new markdown file in the _events folder. This will generate an event page and a link on the events list. The address of the event page will be autonomy-and-verification-uol.github.io/events/ followed by the file's name.

The markdown file should have the following header:

---
layout: event
title: "page title"
date : yyyy-mm-dd
---

The the event layout adds the "Back to Events" link to the top of the event page. The "page title" will be displayed at the top of the page. The date will be displayed on the events page and used to determine if the event appears in the 'Upcoming' or 'Past' list.

The body of the markdown file should contain the text you want on the page. So this should describe the event. Take a look at some of the existing event files for examples.

Adding an External Event Page

This only adds an event to the events list, with a link to a page hosted elsewhere.

To add a link in the events list to an external page for your event, make a new markdown file in the _events folder. This will generate an entry in the events list, but it will simply link to the external page (and an external link icon will show after the name to indicate this to the users).

The markdown file should have the following header:

---
layout: event
title: "page title"
date : yyyy-mm-dd
externalURL: "your link"
---

The the event layout adds the "Back to Events" link to the top of the event page. The "page title" will be displayed at the top of the page. The date will be displayed on the events page and used to determine if the event appears in the 'Upcoming@ or 'Past' list. The externalURL is the url of the external page of your event.

Adding an Event Series

This adds a page and an item in the events list, similar to an Internal Event, but is for providing a landing page for a collection of events.

To add a page that collects several events, maybe pages for the same workshop or set of talks, make a new markdown file in the _events folder. This generates a new page, so the name of the new page will be autonomy-and-verification-uol.github.io/events/ followed by the file's name. The event series are listed separately on the events page.

The file should have the following in its header:

layout: event title: "page title" series : true

The the event layout adds the "Back to Events" link to the top of the event page. The "page title" will be displayed at the top of the page. The series : true tells Jekyll that this is an event series.

The body of the markdown file should contain the text you want on the page. So this should describe the collection of events and link to the pages for the events. Take a look at some of the existing event series files for examples.

Adding an Event Workflow

In summary, to add an event page:

1. make a new markdown file in the _events folder,
2. add layout:event, a date, and a title to the file's header,
3. if it is an external event, add an externalURL to the file's header,
4. if it is an event series, add series : true to the file's header,
5. if it is not an external event, add the event page's content to the file, and;
6. commit this change to the master branch.