-
Notifications
You must be signed in to change notification settings - Fork 0
Feat: Devpost HackPack #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
aak523
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. A few points on overall structure mainly but the individual sections are very well written.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A DevPost checklist / TL;DR at some point could be useful. (I think DurHack had one of these?)
| - **Wall of text**: Use bullet points, headers, and whitespace | ||
| - **No visuals**: Screenshots and diagrams make your project tangible | ||
|
|
||
| ## Judge Mindset |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, it would be useful to talk more about sponsor categories and how to appeal to judges for those.
Specifically for this section, you could briefly mention that hackers should tailor parts of their submission (especially the tech stack and solution) to relevant sponsor prizes they're targeting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, especially since the Devpost is heavily used for the BUO categories, and arguably less so for the other onsite judging categories.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be good to have an example of a great DevPost submission at some point? Could ask one of our hacker briefing speakers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I used previous winners' DevPosts as a reference when writing this. Maybe I could just add a link to last years' DevPosts? Theres a way to see ALL the submissions, and all the winners have a tag in the corner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with you doing this, and explicitly mentioning to look out for that tag.
| 4. Add **all** teammates | ||
|
|
||
| > [!NOTE] | ||
| > Only one person needs to submit, but everyone must be added! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will get back to you on this, but not sure it's strictly true. Submissions are managed through the internal IC Hack platform, so as long as you're in a team on there, you should be good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most likely only one person needs to submit (could be the group leader only though?). But yes let's check this first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I have implemented all the other requested changes. I am happy with it once we clear up this section.
No description provided.