project journal

what we mean

Not a changelog - a story. The high points, the bugs that broke your spirit, and how you eventually fixed them, told day-by-day or hour-by-hour with text, photos, GIFs, and short clips.

how to participate

Create a new branch (e.g. journal or docs) in your project repo and deploy it via GitHub Pages, then submit the link below with your name, campus, and project name. Submitting here is mandatory: having the page live on GitHub Pages alone doesn't enter you, only links submitted through this form are considered for judging. If you're on a team, only one member needs to submit on the team's behalf - not everyone individually. We review submissions after the hackathon and announce the winner alongside the other results.

• —Team entry: only one member needs to submit the form on the team's behalf, not every teammate.
• —Markdown/HTML web page, hosted directly on GitHub Pages (a journal or docs branch of your project repo).
• —The journey: a day-by-day or hour-by-hour build story with text, photos, GIFs, and short clips.
• —Learnings & discoveries: new tools, concepts, or hardware you tried for the first time.
• —Team contribution: who built what, and how your team worked together.
• —Problems & breakthroughs: the biggest roadblocks you faced and the clever (or chaotic) ways you solved them.
• —Judged on storytelling style, visual documentation (photos/GIFs), depth of technical learning, and creative web layout/design.