Coding4TX's Hackathon @ Galvanize brings students together to work with tech mentors and compete for the prizes listed on the site. All attendees will also get C/I SWAG and free food all day long from 9am - 5pm!
Our event schedule is below -- please listen carefully for announcements that pertain to your team and for opportunities to attend workshops:
8:00am - 8:30am: Judge Check-In + Info Session
8:30am - 9am: Check-In
9:00am - 9:30am: Project Brief and Initial Team Meeting
9:30am-10am: Hackathon Kickoff Celebration + Explanation of Project and Deliverables
10am - 10:30am: Ideation Presentation and Student Brainstorm
10:30am-11:00am: Wireframing 101, Basic Website Creation with HTML/CSS
11:00am- 12:30pm: Work Time
12:30pm - 1pm: Lunch and Work Time
1pm - 2:30pm: Work Time
2:30pm-2:45: Final Project Submissions
2:45- 3:15: Pitch Practice
3:15pm - 4:00pm: Student Product Pitches to Judges
4:00pm-4:15pm: Clean Up while Judges Deliberate
4:15pm-5:00pm: Award Ceremony with Prizes presented by Mayor Steve Adler!
Eligibility
Your group must have between 3 and 5 participants from your school.
All students must complete an initial brainstorming activity before they arrive at the hackathon.
All students must have their permission slips upon arrival or have their teacher e-mail permission slips to [email protected] before arrival
Requirements
PLANNING GUIDE:
Use this guide to help you plan and organize your project bit.ly/cihacksguide
You need to describe your problem and solution (related to bias or civics) that you've identified, validated, and developed in detail.
Problem: Describe the problem that you are trying to solve with your team and why it is a problem. Explain the validation process that you used and the results of your validation process (i.e. "We surveyed __ people and __ people said that this was a good problem. This is why we decided to continue working on this problem.)
Solution: Describe your tech solution that helps to solve your problem and why it is a good solution. Be detailed while describing the features and explain the results of the validation process for your solution, as well. (i.e. "We surveyed __ people and __ people said that this was a good solution. This is why we decided to continue working on this solution.)
Wireframes / Sketches and Websites: You will plan the layout of your product with at least three wireframes or product sketches on the website that you present at the end of the day.
EACH GROUP HAS 4 DELIVERABLES DUE TODAY:
- Wireframes or Sketches: Each group must produce, either digitally or by hand, at least three wireframes or sketches of their app or product to show the judges what their tech solution might look like.
- Website: Each group must produce one website using www.neocities.org (or Thimble if you're more familair with that text editor) to showcase their problem, solution, and the pictures of their wireframes or sketches. This website link should be included in the final submission of each group's project.
- DevPost Written Descriptions: Allocate at least 20 minutes to complete this valuable part of your submission in DevPost. Write a detailed description of your tech product that answers all of the questions presented to you by DevPost about your product.
- 2 Minute Pitch: Present your problem, solution, wireframes / sketches, and website in an engaging and persuasive way!
Prizes
Best Overall - High School Prize
Four Little Bits kits for the winning team, with a ton of fun ahead building awesome circuits, gizmos, gadgets, and bitsbots.
Best Design - High School Prize
T-Shirts from MongoDB!
Most Creative Solution - High School Prize
T-Shirts from Code/Interactive!
Best Overall - Middle School Prize
MakeDo's!
Best Design - Middle School Prize
MakeDo's!
Most Creative Solutions - Middle School Prize
MakeDo's!
Devpost Achievements
Submitting to this hackathon could earn you:
How to enter
All hackers who are chosen by their teachers to attend the hackathon will work with mentors all day long to build a tech products that solve a problem in education.
Step 1: Identify the Problem: The problem that you choose to solve can be any problem that affects your life and education in any way, including teaching, communicating, learning inside or outside a classroom, factors affecting your home or school environment, issues with friends, or any other problem that you can think of. Think about problems that affect all age groups, from Pre-K to College.
Step 2: Brainstorm Solutions: Think of tech solutions that you can implement for the problem that you identify. This can include a new tech product, app, or a modification or addition to an existing tech product. Think about all of the factors surrounding your problem that are NOT currently addressed using technology and brainstorm how to add technology to that part of your education.
Step 3: Research: Make sure that your idea is original and feasible by researching other technologies and apps that already exist. If your idea already exists, maybe you can make it better or add an extra feature, or you might need to go back to brainstorming to think of another solution.
Step 4: Validation: Validate your problem by asking students at the hackathon if they experience that problem. If no one experiences that problem, perhaps you're not solving the right thing! Validate your solution by asking students at the hackathon if they would use that product. Be prepared to present this information in your final pitch -- for example "We surveyed 40 students and over 60% said that this was a problem they experienced. Over 70% said that they would use our solution."
Step 5: Details and Features: What special features will your product have? How will your users interact with your product? Answer all of the questions provided in your product submission and do research as you go. While thinking about your product, evaluate your idea and answer the following questions:
- Will people use your app?
- Would you use your app?
- Is there a better solution?
- Is there a better way to phrase your solution?
- Is your solution too simple (or complex)?
Step 6: Wireframes / Sketches and Websites: You will present at least three wireframes or product sketches on the website that you present at the end of the day. Deliverables and details are below:
- Written Descriptions: The most valuable part of your submission is a detailed description of your tech product that answers all of the questions presented to you by DevPost about your product. Please take a lot of time crafting your answers because these will be reviewed in detail by the judges.
- Wireframes or Sketches: Each group must produce, either digitally or by hand, at least three wireframes or sketches of their app or product to show the judges what their tech solution might look like. Take pictures of your wireframes / sketches (if hand drawn) or take screenshots and put these images on your website.
- Website: Each group must produce one website using www.neocities.org, scratch.mit.edu or another hosting site to showcase their problem, solution, and the pictures of their wireframes or sketches. This website link should be included in the final submission of each group's project.
Step 7: Refine and Improve: Keep improving your product until final submission at 2:30pm!
Step 8: Pitch Practice: Practice what you are going to say in front of the judges! You only get 2 minutes to present, so you have to make a good impression and stand out!
Judges
Sabina Bharwani
Managing Director, Innovation Strategy & Partnerships, Teach For America, National
Dr. Nora Comstock
Past President & CEO at Las Comadres Para Las Americas
Amanda Fillip
Fellow, Hack Reactor; CS Teacher, KIPP
John Jannone
Regional Manager, Microsoft
Leo Ramirez, Jr.
CEO and Co-Founder, Encast, Inc
Hugh Forrest
Director, South by Southwest (SXSW) Innovation Festival
Derek Keller
Principal, Techstars Ventures
Judging Criteria
-
Best Overall (HS Prize)
Does the product offer a solution to combating an issue that is negatively impacting our students and their peers? Was the pitch effective? Is the idea original and unique? -
Pitch (HS Prize)
How well did the team present their project? Was the idea well communicated? Were the visuals engaging and appropriate? Did the team share presentation responsibilities? Was there a hook to build audience interest? -
Creative Solution (HS Prize)
Did you choose to focus on a major social issue related to bias? Does your tech product have the potential to solve it? Is the idea original & unique, or a just a copy of something that already exists? -
Best Overall (MS Prize)
Does the product offer a solution to combating an issue that is negatively impacting our students and their peers? Was the pitch effective? Is the idea original and unique? -
Pitch (MS Prize)
How well did the team present their project? Was the idea well communicated? Were the visuals engaging and appropriate? Did the team share presentation responsibilities? Was there a hook to build audience interest? -
Creative Solution (MS Prize)
Did you choose to focus on a major social issue related to bias? Does your tech product have the potential to solve it? Is the idea original & unique, or a just a copy of something that already exists?
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.






