> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstcommit.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# What to Include in Your Beginner's Paradise Submission

> Submit your hackathon project on Devpost with a public GitHub repo, complete README, and demo presentation. Learn what's required and what's recommended.

Your submission is how you show the world what you built. Every project must be submitted through Devpost at [firstcommit.devpost.com](https://firstcommit.devpost.com) before the deadline. Make sure you include everything required so judges can fairly review your work.

## 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.

<Warning>
  Submitting everything in a single commit will disqualify your project. Judges look for meaningful commit history that shows your development process. Commit regularly as you work, not just once at the end. See [GitHub and Commit History](/building/github-guide) for a full guide.
</Warning>

### 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

Keep it focused and honest. Judges care more about your learning journey than perfect production value.

## 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

<Steps>
  <Step title="Every member registers on Devpost">
    Each teammate must create or log in to a Devpost account before the hackathon ends.
  </Step>

  <Step title="One person creates the submission">
    Choose one team member to fill out the submission form and upload the project details.
  </Step>

  <Step title="Add teammates by email">
    In the submission form, add your teammates using their Devpost-registered email addresses. This gives everyone proper credit.
  </Step>
</Steps>

## Submit Early, Update Often

<Tip>
  You do not need to wait until the last minute to submit. You can submit early and keep editing your submission until the deadline. This gives you time to fix broken links, improve your README, and polish your demo video.
</Tip>

## Related Articles

* [GitHub and Commit History](/building/github-guide)
* [Using AI Tools](/building/using-ai)
* [Key Dates and Timeline](/hackathon/timeline)