-
Notifications
You must be signed in to change notification settings - Fork 0
Formatting
The conference calendar's format is an extended Markdown subset.
Conference information is at the top of each file, and talks are below the conference detail.
A title for the conference starts with #
and titles for talks start with ##
. Metadata for each are a level deeper (##
for conference data and ###
for talk data) and have a keyword and colon afterward (## Location:
for example). Additional text-based data for each is free-form and can be either plain text or may have Markdown-formatted text.
We use two empty lines to give a bit of breathing room between blocks of data (such as talks). Although it's not necessary for the parser, the extra space makes it easier for people reading the Markdown source files, so please respect others when formatting and add in a bit of extra space. Thanks!
Each conference is in its own file and the file is contained in a year directory.
Filenames should represent the conference name, as it makes it more obvious when editing and the filenames are seen when .ics (calendar) files are produced. However, the actual conference name is parsed from the contents of the file, so the filename doesn't have to have a 1:1 mapping to the conference title.
When possible, omit the year from the conference's title. (The year directory takes care of making this obvious, and the end result will be seen on the page.)
The conference date is optional, but recommended. (If omitted, then it will be assumed that the first and last talks are the starting and stopping dates of the conference... but it's better to be explicit.)
Talks are optional, as we may just have a presence at a conference (such as sponsoring it) and not have anyone speaking. However, if there are talks, please include all the relevant information. All of the details are optional, except for the title.
If dates and times are left out, then the conference and/or talk will not show up in the calendar output, so make sure to try to have a date and time.
Please specify the timezone when adding times. Full times are listed on the website, but having timezones specified can help calendars do the conversion magic needed to display correct times.
To emphasize talk times, we use ### Time:
for talks and ## Date:
for the conference. However, dates without times (for those with unknown times) are supported for talks.
# Generic Linux Conference
## Location: Boston, MA
## Date: October 13 2013
Here's an optional paragraph or two about the conference. We can do free-form stuff here.
You don't need to have any detailed information about a conference, by-the-way.
For more information, check out the website at http://this.is.just.an.example.com/someconference/
## FOSS is for YOU!
### Name: Sally Smith
### Time: April 13, 2013 14:30 PDT
You can put a lot of text in here. It can be
hard wrapped or just flow off the edge.
It's basically Markdown so you can do anything
Markdown supports, like lists:
1. Foo
* Bar
* baz
2. Fiz
And here's another paragraph, with a link http://exmaple.com/
## Another talk
### Name: Joe Bob Joebob
### Time: November 29, 2013 13:00 CEST
This is a test
## Learning about YAET: "Yet Another Example Talk"
### Names: George Jetson & Fred Flintstone
### Time: December 14, 2013 4:50 GMT+3
This is just another talk example.
Here are more Things–And–Stuff™.