Welcome to the OSU Security Club Website! This site is powered by Jekyll and hosted on Github.
- Fork the repository
- Clone it
- Checkout your own branch
$ git checkout -b <USERNAME>/contrib
- Installing Jekyll is very easy:
$ gem install jekyll
. If you have any problems, check out the Jekyll website - In the root of the website (same directory as
_config.yml
), run$ jekyll serve
- Visit 127.0.0.1:4000 to see the site! It updates live as you make your changes, so no need to keep rebuilding.
Once you've made all the changes you'd like run
$ git status
$ git add <FILE>
all of the files you changed.- Commit your changes
$ git commit
and enter a helpful commit message describing what you did. - Push to your branch
$ git push origin <branchname>
- Go to https://github.com/osusec/osusec.github.io and click the big green button. You want to compare master to the branch you just pushed to.
- Create a pull request, but don't merge it! We will look over your pull request as soon as we can and see if we can merge it.
- Profit.
The file structure may seem a little unintuitive if you haven't used Jekyll before, so let me clarify things a little.
The about page and meeting-notes page require some templating, so they are in their own directories. This is both so they are easy to find, and so that their urls are pretty (ie http://url.com/about/). If you are interested in modifying them, both of them are html pages which use /layouts/default.html as their template. The people directory contains biography of all of the officers, which gets compiled into the about page, and the events directory contains all of the events which get thrown onto the index page. These need to be prepended with a date (any date) according to Jekyll law; I don't like it either, it's just how it is. There are template pages in both of these directories that can help you get started adding a new person or event.
The layouts directory
contains, well, layouts (or templates) that other pages use. For
instance, all of the pages with "layout: post" use layouts/post.html
page as their template, injecting things like title and content
into the variables on the layouts/post.html
page.
The assets directory contains css and images. Link to it using
assets/<filepath to thing>
This is where Resources and Code of Ethics pages live. They are "normal" pages that don't require special html like about and meeting notes. They're written in markdown, and then compiled into html.
This is the directory the site gets built into. Don't touch it. Please.