For small edits like adding a talk, simply fork, add your talk based off the template given in the next section. Getting your changes back upstream only requires a pull request to uofa-acm master. For more in depth work, you'll need to read the making big edits section below.
While you could fork, change, pull request, and pray you didn't break anything, you can run the uofa-acm site locally to verify. If this interests you, keep reading.
We use the Ruby package manager RVM to install and manage the site dependencies. While RVM is not strictly necessary, it will keep your site-wide Ruby installation (if it exists) pristine.
Getting RVM installed is a single command:
$ \curl -sSL https://get.rvm.io | bash -s stable
You should now have access to rvm
commands in your shell. Go ahead
and install a local copy of Ruby:
$ rvm install ruby
Now grab the Jekyll microblogging framework that allows you to run uofa-acm locally on your machine:
$ gem install jekyll rdiscount
All done! Fork uofa-acm and clone your fork down to your machine:
$ git clone git@github.com:$USER/uofa-acm.github.io.git
$ cd uofa-acm.github.io
$ jekyll serve --watch
From a browser you can load localhost:4000 and view your local copy of uofa-acm. As you make edits the Jekyll serve will reload, so just hit refresh in the browser. Done and done.
The filename of your post should be YYYY-MM-DD-Some-Title.md, where YYYY-MM-DD is the date of your talk. The file you create should go in the _posts directory of the project.
###the file should have the following layout:
---
layout: post
title: Title of your talk
smalltext: Your name
summary: A brief sentence about your talk
tags: talk
---
A full description of your talk goes here.
You can link to your website or presentation like this: [example link](http://example.com/)
Any other Markdown styling will work. See here for additional Markdown syntax