No description
Find a file
2017-02-09 02:31:56 +01:00
commands browser post initial 2016-10-29 22:04:20 +02:00
content don't load quotes json, it's useless for now 2017-02-08 17:20:51 +01:00
data various stuff 2016-08-02 19:54:18 +02:00
layouts redesign gamification tile 2017-02-08 16:31:17 +01:00
lib some code cleanup 2017-02-09 02:31:56 +01:00
.gitignore should not be commited 2016-11-01 11:13:26 +01:00
.ruby-version let's try travis 2016-07-18 13:07:45 +02:00
.travis.yml nanoc environments \o/ 2016-11-21 14:17:29 +01:00
Checks the best way to prevent test failures is not to test at all 2016-09-04 01:44:21 +02:00
Gemfile new zinc url, fixes #141 2017-01-26 15:53:10 +01:00
Gemfile.lock update all the things 2017-01-18 15:17:13 +01: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 update all the things 2017-01-18 15:17:13 +01:00
README.md Update meta-tags info 2016-12-06 10:27:57 +01:00
Rules new zinc url, fixes #141 2017-01-26 15:53:10 +01:00

zeus.ugent.be

Build Status

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