The Project Submission

 

You will submit your project on our DevPost page. Your submission should include a comprehensive Project Description and a compelling Demo.

• Project Description: Your description should be a brief but complete overview of your project, including the following:

  • Project Overview: Which problem statement did you tackle? What programming languages and tools did you use, and how did you use them? What cancer resources or other information did you take into account when creating your solution?

  • Purpose: What problem were you tackling in the context of cancer? Detail your team’s motivation and explain why you believe your project matters. What is the future of your project, and how does it make some aspect of life better for individuals impacted by cancer or those involved in their care?

  • How it works: What can a user do with your project? What are your user stories? What data sets did you use to make meaningful conclusions?

 

The Demo & Presentation

 

Your demo is your chance to shine and show the judges what you built. This is the primary source judges will use to evaluate your project, so give it the attention it deserves.

You have the flexibility to present your project in a way that best highlights your work. You can choose to:

• Live Demo: A live, interactive demonstration of your tool or application, with a team member speaking and showing its features.

• Presentation & Walkthrough: A presentation deck (e.g., in Google Slides or PowerPoint) that explains your project, your process, and what inspired your team, followed by a live walkthrough or pre-recorded video of your project in action.

• Video-Only: A pre-recorded video (2 to 5 minutes) showcasing your project with a voice-over explanation.

Regardless of your chosen format, your presentation should be 2-5 minutes total.

 

The Codebase

 

We highly encourage using GitHub as a shared repository of code for your team. It allows for efficient code sharing and timestamps individual commits. All relevant code and information in your project must be developed after hacking starts at 8 am PT. Breaking this rule will result in immediate disqualification. The codebase is where judges will be able to evaluate the quality of your code and ensure the work you turn in is your own.

 

Our Community Guidelines

 

This event is founded on the principles of respect, collaboration, and community. Hack4Hope is an event to raise funds for cancer advocacy, and we expect all participants to embody these values. We have a zero-tolerance policy for harassment or inappropriate behavior. Please use appropriate language, treat everyone with kindness and respect, and help us maintain a safe and supportive environment for all.