The Outline: The outline is (1) a brief description of your project, (2) its purpose, and (3) how it works. Paste your outline into the textbox in the DevPost project submission page. Below is more detailed information for each of the three items:

1. Project Description:  Which problem statement did you tackle? What programming languages and tools did you use and how? What cancer resources or other information did you take into account when putting together your solution?
2. Purpose:  What problem were you tackling with your project in the context of cancer? Try to detail your team’s motivation, and explain in detail 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?
3. 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 [2 to 5 minute video or presentation - or whatever platform you choose to showcase your work]: For example, you could choose to screen record someone using the different features of your app with a voice-over explanation. Be creative! This is the primary source judges will use to evaluate your project, so make sure you give the demo the attention it deserves.

The Codebase: We highly encourage GitHub as a shared repository of code for your team. A crucial aspect of GitHub is that it both enables efficient code sharing and timestamps individual commits. All relevant code and information in your project must have been developed after hacking starts at 8 am PT. Breaking this rule will result in your removal from the competition. The codebase is where judges will be able to evaluate the quality of your code and make sure that the work you turn in is in fact, yours. Although we recommend using GitHub, you may choose to deliver your codebase in a Google Drive folder or other such means.