-
Notifications
You must be signed in to change notification settings - Fork 6
Flow
Sledge is an application that is used throughout an entire hackathon, so it is split up into four phases:
- Pre-hackathon Phase
- Submissions Phase
- Judging Phase
- Post-hackathon Phase
User: Admins
In the pre-hackathon phase, the Sledge admins will have to set up a new hackathon in Sledge. This includes setting the season, the categories, and the criteria for each category. There may be other optional settings as well.
Admin: An admin is somebody who has control to the Admin dashboard in Sledge. This is generally someone who is in charge of the hackathon, or is managing the submissions and judging process.
Season: The season the hackathon is being hosted. Ex. Spring 2021.
Category: What the hackers base their hacks on, and eventually submit to. Can be a track or a superlative. To win in a category, a submission must score the highest in that category.
Track: A type of category. Hackers can only submit their projects to one track. The winners of a track consist of a first place winner and a runner-up. Ex. Maverick Track, Health Track, etc.
Superlative: A type of category. Hackers can submit their projects to as many superlatives as they want. Only a single team can win a superlative prize. Ex. Best Solo Hack, Best Beginner Hack, Best Failure to Launch, etc.
Criteria: The standards by which a hack is judged. These criteria can vary per category. Some examples of more general criteria are: Functionality, Creativity, Technical Difficulty, etc. An example of a more specific criterion is Impact for the Health Track.
When an admin logs in, they will see their admin dashboard.
When a hacker logs in, they will see their past HackRU submissions. The submit button is grayed out.
When a judge logs in, they will see... something :)
User: Hackers
Once the hackathon begins, the submissions phase of Sledge begins. It is started when an admin presses the toggle button for the submissions phase. During this time, hackers are allowed to create, edit, and submit hacks to HackRU. Once a hack is submitted, it will be judged.
- When a hacker creates a new submission, this new submission is created for everybody on their team as well.
- When a hacker submits their hack, their hack is submitted for everybody on their team as well.
Hacker: A hacker is a single participant of the hackathon.
Team: A team is a group of 1 to 4 hackers.
Submission/Hack: Submission and hack are used interchangeably at the moment. A submission/hack is what a team submits to HackRU to be evaluated by judges. The submission/hack with the highest score in a category wins that prize.
When an admin logs in, they will see their admin dashboard.
When a hacker logs in, they will see their past HackRU submissions, as well as a submit button.
When a judge logs in, they will see the categories for the hackathon. Maybe something else as well, like instructions on how to use Sledge.
User: Judges
To start the judging phase, the submissions phase must be turned off via the toggle button in order to toggle the judging phase. During this phase, judges are allowed to begin judging submissions based on the category they are judging.
Judge: A judge is a person who evaluates hacks. They can choose to judge one or more categories.
When an admin logs in, they will see their admin dashboard.
When a hacker logs in, they will see their past HackRU submissions. The submit button is grayed out.
When a judge logs in, they will see a list of categories they are judging. If they click on one of those, they will be shown submissions for them to evaluate.
Once both the submissions and judging phases are turned off, the admins are able to see all possible winners for the hackathon. They will see a list of possible combinations of winners for each category. Admins will also have to mark the hackathon as complete.
When an admin logs in, they will see their admin dashboard.
When a hacker logs in, they will see their past HackRU submissions. The submit button is grayed out.
When a judge logs in, they will see... something :)
Welcome
Using Sledge
Development
Archive