Most of what you do will take place on:

• Slack - communication with your team, non-profits, mentors

• DevPost - your project's documentation

• GitHub - your code must be publically available

• Heroku - when you productionalize your code, use Heroku as one of the easiest ways to make it available to the masses

Here's how your hackathon week looks:

1. Day 0: Join our Slack community

2. Day 1 (Monday): Find a team and declare a nonprofit problem you're working on. Figure out when everyone can meet to chat about how you plan to solve the problem. Determine schedules - you don't need to dedicate every hour of the week to hacking, we know you have jobs, schoolwork, and a life to live!

3. Day 2 (Tuesday): Have a design, some wireframe mocks (Use: UXPin, Figma, Miro). Start your DevPost submission for our DevPost Hackathon

4. Day 3 (Wednesday): Start slinging code with your team, determine who is working on what, how frequently you'll meet, and make sure you all are aligned on what you are building and what success looks like.

5. Day 4 (Thursday): Take a good look at your DevPost submission and update it with the problem your team is solving, and how you are solving it. Start recording your 4 minute demo video using tools like Loom or Quicktime.

6. Days 5,6,7 (Friday to Sunday): With the week mostly over, no classes, you're done with work: this is where the bulk of your work will likely happen.

7. Day 6 (Saturday): Make sure you are thinking about how you will present your work, how you align to judging criteria, and make sure your DevPost Submission (1st place from 2020), GitHub README (example from 2020) and demo videos (example from 2020) are looking good!

8. Each day: We'll trigger a Slack-based standup for you and your team. A Slackbot will ask you (1) what you've worked on, (2) what you plan to work on, (3) what is blocking you. This will be shared back with your team to get everyone on the same page (especially if you are across multiple timezones). We've found this to be invaluable both in our software engineering careers and at Opportunity Hack.

9. Any day: Ask a mentor for help, review, advice, a high five 👋

Here are some example nonprofits focusing on Economic Empowerment:

1. https://www.ywca.org/

2. https://www.azecon.org/

3. http://www.cplc.org/

4. http://economicintegrity.org/

5. https://www.onecommunityfoundation.org/

6. http://www.positivepathsaz.org/

7. https://www.aaed.com/

8. https://www.jobpath.net/

9. https://sarsef.org/

10. https://phoenix.dressforsuccess.org/

11. https://gangplankhq.com/

12. https://www.herowomenrising.org/

13. https://econa-az.com/

Before the hackathon, we will want to spend about 2 hours total with you to refine your problem statement so that hackers have a good idea of the problem you have. Our volunteers use Google Meet to chat with you virtually.

Most of what nonprofits are involved with will take place on:

• Slack - communication with teams who are working on your problem. Help them better understand your needs, your customers, data, process, anything and everything.

• Phone calls/SMS - your team will want to chat with you over the phone or through text messages.