Hackathon Organizer Guide
  • Introduction
  • overview
    • What is a Hackathon?
    • What is MLH?
    • MLH Hackcon
    • MLH Community Values
    • Event Types
      • Digital Events
        • Digital Mini Events
          • Marble Races
          • Pokemon Showdown
          • Wiki Races
          • Hacker Hangouts
        • Streamyard
  • General Information
    • Hackathon Timeline
    • Finding the Date and Purpose
    • Build Your Leadership Team
    • Locking Down a Venue
    • Hackathon Budgeting
      • Legal Considerations
    • Getting Sponsorship
      • Introduction to Fundraising
      • Understanding Your Sponsors
        • Evaluating In-kind Sponsorships
      • Potential Sponsor Perks
      • Sponsorship Prospectus
      • The 5-Step MLH Sponsorship Process
      • Cheat Sheet: Emailing Your Sponsors
    • Hackathon Website
      • Making an Accessible Design
      • Placeholder Website
      • Main Website
    • Marketing Your Event
      • Promoting Your Event
        • Marketing Email Template
      • Marketing Goals & Timelines
    • Managing Registrations
      • Registrations
      • Free Registration Tool - OrganizerHQ (OHQ)
      • Sending Reminders
        • Email Templates
      • Check-in Process
    • Event Logistics
      • Hackathon Communication Platform
      • Project Challenges
      • Ordering Swag and Prizes
      • Set Up Your Event
      • Working with Food Vendors
      • Hosting Hackers with Dietary Restrictions
      • Distributing Meals
      • Transportation/Travel Plans
      • Hardware
      • Prepare Your Emergency Plan
    • Judging and Submissions
      • Rules for Your Hackathon
      • Judging Plan
      • Cheating Check
      • Judges Communication and Recruiting
      • Hackathon Submission Portal
        • Using Devpost
        • Using Devfolio
        • Using DoraHacks
    • Hackathon Scheduling
      • Detailed Run of Show
      • Run-Through with the Team
      • MLH Tips and Templates
    • Mentorship
    • Day of Logistics and Hacker Experience
      • Help Desk Recommendations
      • Fun Mini Events
      • Workshops
      • Opening Ceremony
      • Closing Ceremony
    • After the Event
  • Organizer Resources
    • Template Links
    • Getting Support from Others
    • Leadership Resources
    • Marketing Resources
    • Registrations Resources
      • GDPR in Europe
    • Host Exciting Mini-Events
      • Cup Stacking
      • MLH Mini Events
        • WereWolf
        • Slideshow Karaoke
        • !Light
        • MS Paint Bob Ross
    • Keeping Records
    • Software for Hackathons
  • Contributors
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. General Information
  2. Judging and Submissions

Hackathon Submission Portal

PreviousJudges Communication and RecruitingNextUsing Devpost

Last updated 23 days ago

Was this helpful?

Hackathon portals are one of the most important needs for any hackathon to get the projects submitted in the right way. Though one might think that these portals are just working as a form collecting data from the attendees to showcase the project, just using a simple form can be a big problem in terms of judging a hackathon.

Hackathon portals provide separate pages for judges to look over the different details of the project, providing hackers with a page where they can fill in details and publish their projects in front of the world! They allow hackers to show off their projects after the event, and show which projects won the different prizes at an event. Other than that, various tools and services these portals provide are a great way to enhance the overall hacking and organizing experience for everyone involved. They provide clear prize lists, can be utilized to help with judging, and more!

While there are a ton of different platforms to use for judging, Devpost is the most common at MLH Hackathons.

If your event chooses not to use Devpost (we recommend using Devpost as it is much easier than custom making a platform) you should have have the ability to create an export of projects that has the fields below. We also included an anonomized example Devpost export below. While some in the example are Devpost specific and just recommendations to help you, this list is the required fields to submit to MLH after your event.

  • Project Name

  • Submission URL (so that project can be viewed post event)

  • About the Project

  • Try it out / GitHub Link

  • Did you register a domain name this weekend? If so what was the domain?

  • Opt-In Prizes (any categories/tracks they submitted to)

  • Built With

  • Share feedback about any technology you interacted with at this hackathon. Remember to mention what tech you're reviewing

  • Schools of team members

  • Team Member Information (separate columns for each field and each team member)

    • First

    • Last

    • Email

Using Devpost
Using Devfolio
Using DoraHacks