Hackathon Rules and Resources

Hackathon Rules

  1. The primary objective of the event is to meet people while having fun building something new. Don’t do anything that would detract from the fairness or fun of the event.
  2. The bulk of the construction should happen during the weekend. It’s not going to be a fun event if some teams show up on Sunday with super-elaborate projects that they’ve been working on for months. Teams that do this will be automatically disqualified.
  3. Brainstorming, planning, and mock ups are fine to prepare in advance of the Hackathon Weekend. You are also allowed to consider what APIs and third party services you plan to use.
  4. You can use whatever tools and spaces are at your disposal. You’re strongly encouraged to attend the Hackathon Workshop and work at the Hackathon Weekend event location because that’s where the real excitement and energy will be! In order to qualify for the prizes, you must be present to register and also meet with the judges to present your project on Sunday between 2pm and 5pm.
  5. Projects must be submitted to by 1pm Sunday. Instructions for submitting these projects will be provided during the Hackathon Weekend. 
  6. Each participant may compete on one team only- not on multiple teams/projects. Teams will be limited to 2-5 people per team to keep competition fair and healthy. Please list all team members that contributed to your project on your presentation in the “Team Members” slide, even if they did not officially sign up for the hackathon. It is not fair to receive extra outside help without disclosing that information so the judges can take that into consideration (don’t try to make it look like 2 people did the work of 4).
  7. Anyone in violation of these rules (at the organizer’s discretion) will be asked to leave and their project will be deemed ineligible compete.


We have put together some resources to get you moving in the right direction. Take some time to browse through the examples and links to other useful tools and resources.

Intro Google Slides
In the introduction, we give a brief introduction on how the Hackathon is scored as well how teams should be constructed.  We also introduce a very basic business model generation known at the “lean canvas".

Design  Google Slides

We covered the difference between UX (User Experience) and UI (User Interface) as well as the processes involved with rapid prototyping.

Front End Development  Google Slides

Intro to Java Script, Bootstrap, and AJAX.
Backend Slides  Google Slides

API discussion with examples.
Pitch Deck Google Slides

Tool Downloads


Backend (Flask Project):  https://github.com/Bytelion/hackathon_backend_2018
Front End Project: https://github.com/Bytelion/hackathon_frontend_2018
Not Needed:  LiteCoin https://github.com/litecoin-project/litecoin

Team Resources

Team form: This is the form you will use to create and define your team and the roles each member will fill.  Hackathon Team Form

Team Rubric: This is the form that the judges will use to score your final project. This will give your team an idea of what the judges are looking for what what aspects of the process hold more weight.  2019 Hackathon Rubric