hackathon post

Author: wagslane

content/news/hackathon-2025.md

@@ -0,0 +1,80 @@
+---
+title: "2025 Hackathon"
+author: lane
+date: "2025-07-25"
+categories:
+  - "news"
+images:
+  - /img/800/bootsbackend.png.webp
+imageAlts:
+  - "Boots flexing"
+---
+
+Welcome to the Boot.dev 2025 Hackathon!!! Thanks so much for participating. As a reminder, submissions due before **Monday, July 28th 9:00 AM (Mountain Time)** in the [Discord community](https://www.boot.dev/community.) We hope that this event gives you an amazing excuse to knock out your [personal project](https://www.boot.dev/courses/build-personal-project-1) or your [capstone project](https://www.boot.dev/courses/build-capstone-project) and have a blast doing it! Even if you don't win, you'll have a great portfolio piece to use on your job search.
+GLHF!
+
+## 2025 Winners
+
+??? (we will update this page with winners after the event)
+
+## Timeline
+
+- Submissions due July 28th 9:00 AM (Mountain Time)
+- Voting Due July 28th 12:00 AM (Mountain Time)
+- Winners Announced July 29th 9:00 AM (Mountain Time) - _We've made this change so we have more time for manual review_
+
+## Submission Instructions
+
+Submit your project in this format as a _single message_ in Discord to the proper submissions channel.
+
+```
+Github: https://github.com/my-username/my-repo
+Post: https://linkedin.com/...
+Title: <1-6 word project title>
+Description: <Maximum 2 sentence description of the project>
+```
+
+Pro submission channel: #pro-hackathon-submit
+Amateur submission channel: #amateur-hackathon-submit
+
+## Voting Instructions
+
+- You _must_ vote for at least 3 other projects in your category. You vote by starring their repo on GitHub.
+- You may vote for your own project as well (in this case at least 4)
+- You may vote for more projects if you wish (and we encourage it! It will help us get better results)
+
+The Boot.dev team will use the votes to filter down to a reasonable number of submissions and then manually choose the winners.
+
+We will view the votes as suggestions and as a way to manage the number of submissions - at the end of the day we have full discretion to choose whichever winners we think are most deserving.
+
+You MUST vote before the voting deadline at noon on monday. You may vote before submissions close.
+
+## Judging Criteria
+
+- Creative awesomeness (how cool it is)
+- Technical awesomeness (how challenging it is to build)
+- Code quality (how well you implemented it)
+
+## Prizes
+
+- Top 10 in each category are physical event-specific commemorative coins
+- Top 3 winners in each category will also receive letters of recommendation
+- All winners will be listed on the Hackathon Page on the blog (if you want to use an alias, that's fine, we'll communicate with you should you win)
+
+## Misc Rules
+
+- You can work in groups of 1-3
+- If anyone in your team has held a (paid) job as a developer, you'll compete in the pro category rather than the amateur category
+- All submissions must be submitted BEFORE the deadline, no exceptions
+- Any social platform can be used for the post, but the link must be publicly available and the post must not be "private" or "unlisted" in any way
+- You will be rated on the quality of your code and the awesomeness of the project - presentation MATTERS
+- You are NOT allowed to write any code for the before the kickoff event on Friday, but you may use assets from before (e.g. images)
+- You do NOT need to be a paying member to participate (but if you are we of course appreciate you :bootsheart: )
+- There is no specific theme for the hackathon - you can code whatever you like.
+- The project must be easily installable and runnable in under 5 minutes with clear instructions provided on the README
+- You MUST vote for at least 3 other projects. You may vote for your own, and you may vote for more than 3
+- You may use AI however you wish, but just like using library code, your pure-vibe-code will not be seen as "yours", so use sparingly
+- You may use libraries, but you will be judged based on the code _you_ built, so if it's just a simple wrapper it won't be seen as impressive
+- The easier it is to demo, see, install, and use your project, the better. You can host it, but you don't have to. You can require API keys, but the judges may not have time to set them up, so be smart about the usability and presentation of your project.
+- Your social post should primarily be about your project, but it MUST mention that you build it for the Boot.dev hackathon, bonus points for tagging a bootdotdev social handle
+- There is no need to "enroll" - you participate simply by submitting an entry