Resources

Everything you need to get certified

Short guides on building your project, writing it up, and getting it through review. Submissions close in 84 days.

Read this first

A good GitHub repository is required, and it has to contain everything

Your repository is your submission. A reviewer certifies what they can open, read, and run. Empty repos, private repos, and single-commit code dumps get sent back.

  • Public, not private, not a zip
  • The complete source, not a subset
  • README: what it is, a screenshot, how to run it
  • A LICENSE file (MIT is one click)
  • Real commit history, not one big upload
  • No API keys, .env files, or tokens

Test it: hand the link to someone who has never seen your project. If they can't understand it and get it running without asking you anything, it isn't ready.

Finalist 101

Start here if you're not sure what this program is.

Building

The habits that make a project easy to certify.

Submitting

What review looks like and what has to be in place first.

Program

The award, the trip, and what we do with your information.

Still stuck?

The Hack Club Slack is the fastest way to get an answer from someone who has already shipped a project.