Submission form settings
The submission form controls what hackers must provide when they submit. The same fields are available whether you configure them on a program or on a challenge — only where changes:
- Project-first events: configure the form on the program (in the program's Submission Form Setting panel).
- Challenge-first events: configure the form on each challenge.
See Programs and submission flows to decide which applies.
For each field below you can: turn it on/off, mark it required, and add help text shown beneath the field to guide hackers.
Fields
Project URL
Collects a link to the project (GitHub repo, live site, etc.). On by default. Mark it required if a link is mandatory.
Example help text: "Submit your GitHub repo or deployed app link."
Project Name
Collects the project's name. Off by default. Useful for identification and judging.
Screenshots
Lets hackers upload images with their submission. On by default. Useful for UI-based projects and proof of completion.
Example help text: "Upload screenshots showing your project in action."
Description
A text description of the project. On by default. Recommended for most challenges.
Example help text: "Explain what your project does and how it solves the problem."
Built With (tech stack)
A select field for the technologies used. On by default. Helps with analytics and sponsor reporting.
Example help text: "Select all technologies used in your project."
Demo URL
A link to a demo or live project. Off by default. You can optionally restrict it to YouTube links only (useful for demo videos).
Example help text: "Provide a demo video or live project link."