pittcsc / old-pittcsc-website-archived Goto Github PK

We get a lot of information about jobs, so we decided to keep a running list of jobs we know about as part of the website. Here's what we need to do:

Data

• Job opportunities should be managed by adding entries to a single YAML file markdown files

Index page

• Come up with a component (not a JS component, but a general reusable style) to represent a job
• Job list should be paginated to maybe 10 or so per page. Jekyll supports pagination, use that.

Individual Pages

• Each job listing should have its own page, dynamically generated by Jekyll

Feed

• The job listing feed should be subscribable through RSS. Jekyll should give us tools for making an RSS feed from data; we just need to make sure that we can do this with multiple resources (aka, the job feed does not mess with the Blog feed)

http://kylestetz.github.io/CLNDR/

Unfortunately, Jekyll is pretty inflexible when used with Github Pages when it comes to asset compilation. I would like to use some more modern features (ES6 JS, React) but it's hard to do that when you don't have control over how assets get compiled.

This can be fixed if we use Travis to do the static build instead of Github Pages' default behavior.

Build steps

• Find a Gulp setup that would allow us to use Babel easily
• Build a Gulp workflow that lets us use Jekyll for content management, but use Babel for asset compilation

Hosting/Production Push

• Make the default branch develop instead of master since master will need to contain the built version of the assets
• Set up Travis to build after merge to develop and push the built version to master