hese rules are subject to change. The final rules will be given out on the day of the event.

• All design elements, code, hardware builds, etc. for your project must be created during the event. Third party tools and frameworks are allowed as well as your normal tooling (Gulp, Yeoman, Composer, NPM, Bower, etc.). While you may not begin coding in advance, you can plan and discuss with your team in advance. Written documents and design sketches are allowed.  You may also incorporate pre-existing material that is freely available to the public into your project, such as public domain images, Creative Commons music, open-source libraries, existing APIs and platforms, and the like.
• Projects must involve writing significant software, though hardware may be incorporated.  Note: projects that incorporate peripheral hardware that may need additional space (such as large robotic devices, drones, etc.) must be pre-approved by the Valley Hackathon Planning Committee. For questions or approval, contact info@valleyhackathon.com.
• Teams must be comprised of 1-4 people.
• Only ten of the competing teams will present their projects in the final round of judging at the end of the event.  The presenting teams will be determined by an initial round of judging that will take place during the final 1.5 hours of the event.  Note: we recommend that, prior to the beginning of preliminary judging, teams prepare a short (~2 minute) project pitch to be given to a subset of the judges.