No description
| commands | ||
| content | ||
| data | ||
| layouts | ||
| lib | ||
| .gitignore | ||
| .ruby-version | ||
| .travis.yml | ||
| Checks | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| id_rsa.enc | ||
| nanoc.yaml | ||
| package.json | ||
| README.md | ||
| Rules | ||
zeus.ugent.be
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