No description
Find a file
2016-10-29 22:04:20 +02:00
.bundle add img to events 2016-09-13 17:13:43 +02:00
commands browser post initial 2016-10-29 22:04:20 +02:00
content browser post initial 2016-10-29 22:04:20 +02:00
data various stuff 2016-08-02 19:54:18 +02:00
layouts header stuff 2016-10-18 01:04:51 +02:00
lib make development faster by not compiling literally everything 2016-10-15 21:32:45 +02:00
.author-information browser post initial 2016-10-29 22:04:20 +02:00
.gitignore navigation 2016-07-31 19:28:23 +02:00
.ruby-version let's try travis 2016-07-18 13:07:45 +02:00
.travis.yml fix deploy 2016-10-15 21:47:19 +02:00
Checks the best way to prevent test failures is not to test at all 2016-09-04 01:44:21 +02:00
Gemfile nokogiri is a pain to install, and no long necessary 2016-10-16 12:30:01 +02:00
Gemfile.lock nokogiri is a pain to install, and no long necessary 2016-10-16 12:30:01 +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 make really deploy ready 2016-10-05 23:59:33 +02:00
package.json staying up to date is important 2016-10-17 00:16:46 +02:00
README.md improve readme 2016-09-03 23:39:14 +02:00
Rules remove useless output files 2016-10-15 21:43:29 +02: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.

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:

Required

  • title: String
  • time: Date
  • location: String

Optional

  • banner: URL

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:

Required

  • title: String

Optional

  • location: String
  • banner: URL

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