Required Items
Public GitHub Repository
Every project must have a public GitHub repository. Judges will look at your code, your commit history, and your README to understand how you built your project and how you grew during the hackathon.Complete README
Your README is the first thing judges see when they open your repo. Make it clear, friendly, and complete. It should include:- Project overview: What does your project do? Why did you build it?
- Technologies used: What languages, frameworks, libraries, and tools did you use?
- Setup instructions: How can someone clone your repo and run your project locally?
- Credits: Acknowledge any external resources, tutorials, assets, or libraries you used.
- AI usage disclosure: If you used AI tools, describe how you used them and what parts of the project involved AI assistance.
Demo Presentation (3–5 Minutes)
Record a short video that walks judges through your project. Your demo should cover:- What your project does
- How it works (key features and flow)
- What technologies you used
- Challenges you faced and how you solved them
- What you learned during the hackathon
Recommended Additions
These items are not required, but they can make your submission stronger:- Live deployment link: A working URL judges can visit to try your project
- Screenshots or images: Visual previews of your project in action
- Tech list: A clean summary of your stack (great for quick scanning)
- Presentation slides: If you made slides, consider linking them in your Devpost submission
How to Submit as a Team
1
Every member registers on Devpost
Each teammate must create or log in to a Devpost account before the hackathon ends.
2
One person creates the submission
Choose one team member to fill out the submission form and upload the project details.
3
Add teammates by email
In the submission form, add your teammates using their Devpost-registered email addresses. This gives everyone proper credit.