Devinereel

Project viewer for #devinehowest projects, running React on Heroku

Background

This project started of as a fun experiment of ours to quickly deploy a static webapp with React on Heroku and see what we could cook up in a short period of time. We were also bothered with the current viewers and wanted something modern & easily adaptable and editable by everyone. The list of year three students at this time was included in initial v1 release.

Adding yourself

It's highly possible that you are not in the list. Fear not, there is an easy way to add yourself. Either click the button (Opt. A) in the application or submit a pr (Opt. B) to src/js/static/Students.js

1. Option A: will automatically fork this repo, create a patch branch and submit a PR. Please name your pr accordingly. 'Update Students.js' ain't no fun either. Oh and all this is of course only if you have a Github account, duh 🤷
2. Option B: will make you supercool and will guarantee a stable code career throughout Devine (at least, this is what we think 💁)

Maintainers

Current maintainers: Thibault Maekelbergh, Kevin Meyvaert, Lotte Bijlsma

We will gladly turn over this repo to someone else once we graduate. Long live OSS ❤️

The 9 commandments of maintining Devinereel

• Push only to Heroku from the master branch
• Use feature branches prefixed with your initials and merge them into master (eg. tm-persistent-state)
  • Delete these once merged in, no dead branches pls 💀
• Use the labels for issues & pr's.
• Write modern code. Most stuff is transpiled, but then again most of us are going to view this in latest Chrome 😉
• At this moment, if using yarn do not upload yarn.lock to the Heroku slug. Check out this issue as this is the case.
• Resolve modules from absolute paths with Webpack. No arguing about this.
• Clean up unused deps. Preferably keep using the currently integrated Greenkeeper.
• No .env files. We are not going to include a dependency just to set the PORT env. Prefix commands in the shell, or set cloud instance envs instead. (eg. PORT=3000 webpack-dev-server)
• Use gitmoji (preferably creating a hook with gitmoji -i.
• For your tag release you shall always use the funny/catchy name of a briefing PDF.