Skip to content

Instantly share code, notes, and snippets.

@DjjimmyHD
Last active March 2, 2019 00:56
Show Gist options
  • Save DjjimmyHD/7a2b8ef47175d8e1cb9d7cdff594572f to your computer and use it in GitHub Desktop.
Save DjjimmyHD/7a2b8ef47175d8e1cb9d7cdff594572f to your computer and use it in GitHub Desktop.
Hack-a-thon Extavaganza

Hack - A - Thon Extravaganza

Description

You and four other teammates from various other cohorts will have 7 hours to come together and create an amazing website/app. After said time, you and your co-workers will then present your idea to the rest of the competition and a panel of very discerning judges. The website must meet ALL the success criteria outlined below.


Standards

Each groups' project must meet the following requirements:

  • Use data through a fetch request from at least one of the API's below

  • The site or app must be deployed

  • Project must be located on one central github repo

    • Judges will be asking for links to the repo and will be taking commit history into consideration while judging the projects
  • Project must use at least one component from a CSS Framework

  • Project must have a brochure page that has information about what your app does and who it's for

  • Project must have an about the team page that includes pics of members and some info about them

  • Project must have a Header

  • Project must have a Nav

  • Project must have a Main

  • Project must have a Footer

  • Presentations must not go over 3 minutes

    • note groups who go over will be cut off
  • Everybody in the group must talk about the website/app

  • Everybody in the group must spend some time writing or driving


"Arrgh, They Be More Like Guidelines"

  • Your site should use semantic html
  • Your site should have a clear theme
  • Your group should choose a PM this person must also code
  • Your group should spend equal time planning and coding
  • You group should build in full features
  • You group should always be moving towards MVP
  • Your site/app should work...

Suggested Schedule

   915 - 10 planning/idea generation
   10 - 11 wireframing/assigning
   roles/establishing git work flow
   11 - 12 pairing/coding
   12 - 1 lunch
   1 - 115 confirm expectations
   115 - 2 pairing/coding
   2 - 330 check ins and pairing
   330 - 4 practice presentations
   4 begin presentations

Resources

https://galvanize-cors.herokuapp.com

Expectations

It will probably be a hectic day, and may be a little stressful as a result. Take some breaks if you need to. Keep in mind, you are the masters' of your own destiny. You will get out of this what you put in.

While each group will be competing to be the best, at the end of the day we are all on the same team and all want the same thing... to learn and have fun. Inclusion is an active word, meaning we must all make an effort to seek out then include, then respect, all view points and ideas. Everybody has something to learn from everyone if we just take the time to listen, or more importantly ask.

Remember: process over product. Focus on working well with your teammates, practicing what you've learned, and maybe exploring some new stuff. You can do this. I promise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment