Loading
Loading
Loading
Submission flow and visibility.
Last updated: 2026-02-04
Draft vs submitted state for this submission.
Drafts stay private to your team. Submit final when you are ready to be judged.
Public title shown on submission cards and pages.
Pick a clear, concise name so judges and participants can find it.
Unique URL identifier for the submission.
Lowercase letters, numbers, and hyphens only. Used in submission URLs.
Short summary of what you built.
Displayed in listings and overview cards. Keep it quick and clear.
Detailed submission writeup with Markdown formatting.
Use this for technical details, architecture, and longer explanations.
Link to a live demo or hosted experience.
Use a full URL (https://) so judges can open the demo easily.
Link to the source code repository.
Provide a GitHub, GitLab, or similar repository URL.
Link to pitch or presentation slides.
Optional but useful for judging and demos.
Link to a video demo (YouTube, Vimeo, etc).
Required when the event requires a video demo submission.
Add screenshots or visuals for the submission.
Required when the event requires images. Use clear, high-resolution files.
Draft vs final status for a judge score.
Draft scores can change. Final marks your score as complete.
Score each rubric category for this submission.
Required when the rubric is enabled and required by the event. Scores are aggregated into the final leaderboard score.
Private notes for the judge only. Not visible to the team or public.
Private notes for the judge only. Not visible to the team or public.
Assign an award to the submission. Awards are defined by Event staff. Some awards allow for multiple winners.
Assign an award to the submission. Awards are defined by Event staff. Some awards allow for multiple winners.