Go to file
2017-06-03 12:33:32 +02:00
commands browser post initial 2016-10-29 22:04:20 +02:00
content bump 2017-06-01 02:39:55 +02:00
data Fix elo email 2017-05-03 15:50:27 +02:00
layouts try this for unfurling 2017-05-18 15:33:43 +02:00
lib add sitemap 2017-05-29 14:36:20 +02:00
.codeclimate.yml add mdlint 2017-05-20 15:37:14 +02:00
.gitignore should not be commited 2016-11-01 11:13:26 +01:00
.mdlrc fix some markdown linting 2017-05-22 03:29:42 +02:00
.ruby-version let's try travis 2016-07-18 13:07:45 +02:00
.travis.yml let travis cache nanoc directories 2017-05-17 23:29:03 +02:00
Checks disable html check 2017-05-01 23:56:38 +02:00
Gemfile scripts at end of body 2017-04-23 15:27:43 +02:00
Gemfile.lock scripts at end of body 2017-04-23 15:27:43 +02:00
Guardfile readme n shit 2016-06-09 15:04:10 +02:00
id_rsa.enc add encrypted ssh key 2016-07-18 13:31:59 +02:00
nanoc.yaml nanoc environments \o/ 2016-11-21 14:17:29 +01:00
package.json bump 2017-06-01 02:39:55 +02:00
README.md Add PageSpeed badges 2017-06-03 12:33:32 +02:00
Rules add sitemap 2017-05-29 14:36:20 +02:00

zeus.ugent.be

Build Status Code Climate PageSpeed PageSpeed

Setup

Installation

bundle install
npm install

Developing

bundle exec nanoc live

This will spawn a webserver, and automatically recompile the site when files get changed.

Deploying

The latest builds on master get deployed automatically using travis.

For manual deployment, run

bundle exec nanoc deploy --target public

Posts

Posts should be written in kramdown, a markdown superset which has a very complete syntax guide.

Meta-tags:

Name Type Required
:title String yes
:created_at Date yes
:description String no
:author String no
:lang String no

Events

Example structure:

content/
  assets/
  events/
    15-16/
    16-17/
      battlebots/
        main.md
        intro.md
        codenight.md
        finale.md
      awk.md
      sed.md
      ruby.md
    index.erb

Metadata

Every event is a .md file with the following metadata tags:

Name Type Required
:title String yes
:time Date yes
:location String yes
:description String no
:created_at Date no
:locationlink String no
:facebook URL no
:banner URL no
:image URL no

Grouped events

If there's a series of events (for example summer code nights) these can be grouped by creating a folder containing a main.md, which will need the following metadata:

Name Type Required
:title String yes
:location String no
:banner URL no

Other .md files made in that folder are sub-events which need to fit the metadata description listed earlier