Skip to content

Conversation

@KOLESNiii
Copy link
Collaborator

No description provided.

@KOLESNiii KOLESNiii self-assigned this Jan 15, 2026
@KOLESNiii KOLESNiii requested a review from aak523 January 15, 2026 11:44
Copy link
Collaborator

@aak523 aak523 left a 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.

Copy link
Collaborator

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
Copy link
Collaborator

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.

Copy link
Collaborator

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.

Copy link
Collaborator

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.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to this.

Copy link
Collaborator Author

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

Copy link
Collaborator

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!
Copy link
Collaborator

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.

Copy link
Collaborator

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.

Copy link
Collaborator Author

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.

@KOLESNiii KOLESNiii marked this pull request as ready for review January 18, 2026 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants