├── FAQ.md ├── README.md ├── apis.md ├── getting-started.md ├── judging-protocol.md ├── schedule.md └── teams.md /FAQ.md: -------------------------------------------------------------------------------- 1 | # FAQ 2 | Frequently Asked Questions 3 | 4 | ## Where's my ticket to the hackathon? 5 | We had an extensive *application* process that was detailed by Quincy on at https://hackathon.freecodecamp.org/ . If you *successfully* completed this process, and you were *one of the first 300 to do so* (for the in-person event), then you were sent a ticket to the email address provided in your application. If you do not have a ticket then you cannot attend the in-person hackathon. But you are welcome to join the online hackathon. 6 | 7 | ## What is the JAMstack? 8 | The JAMstack is a powerful new approach for deploying fast, highly scalable sites and applications that don't require backend infrastructure. Thanks to recent advancements in the web platform, developers can now run any web property, from simple sites to complex applications, on global CDNs and without a single web server. Learn more about how the JAMstack works [here](https://jamstackconf.com/what-is-jamstack). 9 | 10 | ## Can the online participants and in-person participants be on the same team? 11 | Unfortunately no. This makes things needlessly complicated. Further, there are separate prizes and judging protocol for the online and in-person hackathon. If we discover that your in-person team has online collaborators, you will be disqualified. 12 | 13 | ## Can the online/in-person hackers still chat? 14 | Of course. We're all in the same Discord chat group. And since this hackathon is largely about education, the in-person/online groups should both help each other out by answering questions. 15 | 16 | ## Where is the Discord Channel? 17 | Check your email for the Hackathon Discord Group invite. 18 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 2018 freeCodeCamp JAMstack Hackathon 2 | If you want to succeed at this hackathon, please read this document and its subsequent files in their entirety before you begin. 3 | 4 | ## Checklist 5 | Please read the following carefully, and act on each item that requires your attention: 6 | 7 | - [ ] Fork this repository 8 | - [ ] Make sure that you have a ticket from Tito. Check your email -- Quincy has emailed your ticket to you. 9 | - [ ] Join the freeCodeCamp JAMstack Hackathon Discord Group (Quincy has emailed that link to all ticket holders). Please do not share this link with non-participants. 10 | - [ ] Chat with others in the Discord group to brainstorm ideas and form teams. You will also have time on Saturday morning for this. IMPORTANT: Remote hackathon participants cannot team up with in-person participants. This is to simplify the process and ensure that all teams are starting from the same baseline. 11 | - [ ] Review this `README.md` file for further instructions and guidelines 12 | - [ ] Review the [APIs](/apis.md) 13 | - [ ] Ask questions to API sponsors directly on their Discord channel (i.e. `api-netlify`) 14 | - [ ] Review the [Judging Protocol](/judging-protocol.md) 15 | - [ ] Already have a team? List it in the [Teams file](/teams.md). 16 | - [ ] Don't have a team? Review the [Teams](/teams.md) that are seeking teammates. 17 | - [ ] Review the [Schedule](/schedule.md) 18 | - [ ] Review the resources and recommendations for [Getting Started](/getting-started.md) with the JAMstack. This will give you good resources for starting your project. 19 | - [ ] Ensure that you deploy your project with [Netlify](https://www.netlify.com). You should already have an account per the hackathon application instructions 20 | - [ ] Bring a refillable water bottle 21 | - [ ] BRING A POWER STRIP to use and share with others! We recommend putting tape on it to write your name. 22 | - [ ] If you plan on drinking alcohol on Sunday evening during the awards ceremony, you'll need to bring a valid government-issued photo identification showing that you're at least 21 years of age. 23 | 24 | ## How is this hackathon different? 25 | 26 | Most hackathons focus principally on the end-goal -- the product. While this hackathon places a significant amount of focus on the end-product as well, we are also placing a significant amount of focus in the *process* of how you approach building your project. 27 | 28 | ### The Process -- what it means 29 | 30 | Building great software isn't just about the code you write. Your planned approach to building it just as important. So here's what this means for you as a hacker at this hackathon: 31 | * Judges may pose a number of questions for you, and share them with you in the Discord group 32 | * Judges may visit teams and ask you these questions to see how you are handling your approach to building your app. Do you have a plan of action? Are you organized in your list of responsibilities and dividing tasks? Are the goals realistic given the limited time frame? 33 | * These ad-hoc interviews will take place shortly after lunch on Saturday. We will livestream them. 34 | * Your answers to these questions will be a small percentage of your overall judging score. 35 | 36 | 37 | ## Code of Conduct 38 | By attending the hackathon, or participating remotely, you affirm that you have read and agree to our Code of Conduct, and you will abide by its guidelines laid out here: https://jamstackconf.com/code-of-conduct 39 | 40 | Note: This code applies to both in-person and online interaction. Violations will not be tolerated. 41 | 42 | ## Purpose 43 | The Hackathon is designed to be a fun and educational environment. Of course there will also be competition for prizes -- but our main goal is education, building community, and learning to use some cool APIs and technologies! 44 | 45 | ## Perks 46 | 47 | Thanks to the generosity of GitHub, you will have coffee, breakfast, lunch, and light dinner on both days! 👏*applause for GitHub*👏 48 | 49 | Send them a thank you note for being the most amazing hosts on [Twitter](https://twitter.com/github)! 50 | 51 | Once hacking ends on Sunday, we'll celebrate with some beer, wine, cocktails and mockatails, and watch the top 6 teams get interviewed. The interviews will be broadcast on the many monitors at GitHub's office. Then we'll reconvene to see the top 3 teams present on stage! 52 | 53 | ## Location 54 | GitHub HQ 55 | 88 Colin P Kelly Jr St, 56 | San Francisco, CA 94107 57 | 58 | ## Team Size 59 | * Max team size: 6 60 | * Recommended team size: 3-5 61 | 62 | ## Join the Hackathon Discord Group 63 | See the link sent to your email 64 | 65 | ##### More info on Discord: 66 | * You can ask API sponsors questions directly in their respective channel, i.e. `#api-netlify` 67 | * Pay special attention to `announcements` channel. 68 | * Ask and answer questions about certain technologies in the `q-and-a-` channel 69 | * Have general communication in the `general` channel 70 | * Find a teammate or a team in the `team-formation-sf-hackathon` channel 71 | 72 | ## Review the APIs 73 | Review the APIs in the [apis.md](./apis.md) file in this repository. Mingle with the API sponsors at their tables and in their Discord channels. 74 | 75 | ## Team Formation 76 | #### If you have a team 77 | 1. List your team in the [teams.md](/teams.md) file in this repo 78 | 2. Fork the repo and make a PR to list your team 79 | 3. Follow the style guide for listing your team 80 | 4. Tag `dunphyben` in your PR. 81 | 82 | #### If you don't have a team 83 | 1. Browse teams in the [teams.md](/teams.md) file of this repo 84 | 2. Contact team members via Discord or in-person on Saturday morning 85 | -------------------------------------------------------------------------------- /apis.md: -------------------------------------------------------------------------------- 1 | # APIs 2 | Listed here are the APIs for your use. 3 | * Browse the APIs here. Visit docs etc. 4 | * Meet with the API sponsors at the hackathon, particularly on Saturday morning 5 | * Communicate with the API sponsors via their dedicated Discord channel. 6 | * Deploy your apps with Netlify. 7 | 8 | # Fauna 9 | #### Quick Description 10 | Cloud database with generous free plan and distributed ACID transactions for global data integrity. Get started easily and scale to worldwide success. 11 | 12 | ### Purpose 13 | Stores transactional data like account balances, user profiles, social media content, shopping cart orders, etc. 14 | 15 | ##### API endpoint: 16 | Install with the netlify command line tool after you have linked your checkout to your app, by running `netlify addons:create fauna` and you can access your database with environment variables like this: 17 | 18 | ```js 19 | const client = new faunadb.Client({ 20 | secret: process.env.FAUNADB_SERVER_SECRET 21 | }); 22 | ``` 23 | 24 | ### Challenges 25 | 26 | A common pattern with Single Page Apps is for the browser to query a cloud database directly. FaunaDB access control supports apps like this. A [demo app using the Netlify Identity service and login widget to authenticate with FaunaDB is available here.](https://github.com/fauna/netlify-faunadb-todomvc) Follow the eight steps in the README and you'll be ready to build your own app. 27 | 28 | ### Docs 29 | 30 | The [FaunaDB Query API docs](https://app.fauna.com/documentation/reference/queryapi) are a good reference. 31 | 32 | For [getting started with the data model, this tutorial is good.](https://app.fauna.com/documentation/howto/crud) And when you log into fauna.com (not required to get started) you can [learn more about the Fauna Shell and other tools here.](https://app.fauna.com/account) 33 | 34 | ### Video tutorial 35 | 36 | I'll walk through these steps live during the Hackathon keynote. 37 | 38 | ### Presentation slides 39 | 40 | Coming soon. 41 | 42 | ### Prizes 43 | 44 | 1st: Apple Watch 45 | 2nd: Oculus Go standalone VR headset 46 | 3rd: $100 iTunes Gift card 47 | 48 | 49 | *** 50 | 51 | # Formspree 52 | 53 | https://formspree.io 54 | 55 | ### Purpose 56 | 57 | Formspree is a form backend that emails you when someone submits your forms. It’s the simplest way to add custom contact forms, order forms, or email capture forms to your JAMstack website. Once you connect your form to our endpoint we’ll email you the submissions. No PHP, Javascript or sign up required. 58 | 59 | ### API endpoint 60 | 61 | To use formspree with an existing HTML form you must: 62 | 63 | 1. change the `action` of your form to point to `https://formspree.io/` 64 | 2. make sure the `method` is `POST`, and 65 | 3. give a `name` attribute to all your `input` tags. 66 | 67 | For example: 68 | 69 | ```html 70 |
71 | 72 | 73 | 74 |
75 | ``` 76 | 77 | Try playing around with formspree in our sandbox at https://testformspree.com 78 | 79 | ### Challenges 80 | 81 | Get a "contact us" form set up on your website! 82 | 83 | Set up a serverless function to respond to a webhook each time a user submits the form, then fetch the content and use it to do something coool.... 84 | 85 | ### Docs 86 | Using formspree is as easy as the `API endpoint` instructions. Try playing around with formspree at https://testformspree.com. 87 | 88 | You can have more control of how your forms are handled by formspree by adding special `type="hidden"` inputs. See the docs below for a list of the special input names that you can use. 89 | 90 | https://formspree.io/docs/ 91 | 92 | You can also find answers to common questions on our help site here: 93 | 94 | https://help.formspree.io/ 95 | 96 | Finally, we will be here at the hackathon and available to help you. Just look for this goofy guy near the big Formspree banner: 97 | 98 | 99 | 100 | 101 | ### API (Beta) 102 | 103 | We just launched an API beta. Check out the docs here: https://formspree.io/api. 104 | 105 | We're continuing to add to those docs so check back occasionally. Also check out the Discord `#formspree-api` room for updates. 106 | 107 | Finally we're gonna offer coupons to people who want to test out our Gold / Platinum features (including APIs). Let us know in discrd or at the table if you want free access. 108 | 109 | ### Video tutorial 110 | Nothing yet, but maybe we'll have one of these posted soon... 111 | 112 | 113 | ### Prizes 114 | 115 | In person participants that use Formspree in their hackathon project are eligible to win a DJI Spark drone! 116 | 117 | *** 118 | 119 | # Clarifai 120 | #### Quick Description 121 | Clarifai's API uses deep learning to do image and video recognition. 122 | 123 | The API is built around a simple idea: you send inputs (an image or video) to the service and it returns predictions. The type of prediction is based on what model you choose. For example, if you run your input through the pre-trained 'food' model, the predictions it returns will contain concepts that the 'food' model knows about. If you run your input through the 'color' model, it will return predictions about the dominant colors in your image. The 'General' model covers a broad array of common concepts. A full list of models is available here: https://clarifai.com/models. 124 | 125 | You can also use the Custom Training feature to train your own model: https://clarifai.com/developer/guide/train#train. 126 | 127 | ### Purpose 128 | Use the Clarifai API if you want to add visual understanding to your JAMstack app. Two common use cases are analyzing what is in an image, and visual (image-based) search. 129 | 130 | Clarifai can recognize over 10,000 concepts out-of-the-box with default settings ("General" model). You can also quickly train a model to recognize new concepts based on images you upload and label. You can see a complete list of pre-trained models you can use here: https://clarifai.com/models 131 | 132 | ##### API endpoint: 133 | https://api.clarifai.com/v2 134 | 135 | We recommend using a client library to access the API (makes it easier). There are clients available for most languages, including JavaScript: https://clarifai.com/developer/reference/ 136 | 137 | NOTE: After creating an account at https://clarifai.com/developer/account/login, you can head over to Billing (https://clarifai.com/developer/account/billing) and enter Plan Code: SFHACKS to receive free API credits for 1 week. 138 | 139 | ### Challenges 140 | + Use one or more Clarifai's pre-built models (https://clarifai.com/models) to build an innovative visual recognition application 141 | AND/OR 142 | + Build a Custom Model using at least 10 images as labeled examples (https://clarifai.com/developer/guide/train#train) and use the model in an app to solve a personal annoyance 143 | AND/OR 144 | + Come find us at our table to receive access to a brand new product (currently in private phase), and use that to build a cool application! 145 | 146 | ### Docs 147 | Developer Guide (start here): https://clarifai.com/developer/guide/ 148 | Technical Reference and Client Libraries: https://clarifai.com/developer/reference/ 149 | JavaScript API endpoint reference: https://sdk.clarifai.com/js/latest/index.html 150 | Custom Training walkthrough: http://help.clarifai.com/custom-training 151 | 152 | ### Video tutorial 153 | 4 minute Intro to Clarifai including an API demo with the Python client: https://youtu.be/YOrrROME2zc 154 | 155 | ### Support & Help 156 | We'll have a table at the hackathon, and will provide you with all the guidance you need. Come find Abhishek from our Product team! 157 | 158 | We also have resources available at: http://help.clarifai.com/ 159 | 160 | ### Prizes 161 | The winning team will win a Cozmo Robot! 162 | 163 | https://www.anki.com/en-us/cozmo 164 | 165 | ![Cozmo Robot](https://www.anki.com/on/demandware.static/-/Sites-anki-master-catalog/default/dw3b4502ca/cozmo/cozmo-LE--desktop.jpg) 166 | 167 | Top 5 teams will also have the opportunity to feature their hacks on Clarifai's blog! 168 | 169 | *** 170 | 171 | 172 | # Hasura GraphQL Engine 173 | 174 | [Hasura](https://hasura.io) is an [open-source](https://github.com/hasura/graphql-engine) service that gives you instant, realtime GraphQL APIs for your JAMstack app. With one-click to deploy on Heroku's free tier, you can get started in less than a minute. 175 | 176 | [![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/hasura/graphql-engine-heroku) 177 | 178 | You don't need to know how to write a GraphQL schema, resolvers or learn how to use 179 | a database to get started! Head to the deployed app, create a table, and run CRUD + realtime with GraphQL :) 180 | 181 | ![Hasura demo GIF](https://raw.githubusercontent.com/hasura/graphql-engine/master/assets/demo.gif) 182 | 183 | You can also use Hasura to trigger Lambda/Serverless functions such as [Netlify 184 | Functions](https://www.netlify.com/docs/functions/) when an event happens on the 185 | database, for example, send an email when a new user is added. 186 | 187 | ### Purpose 188 | 189 | You should use Hasura if your JAMstack app needs to CRUD data, needs a realtime API, 190 | or if you want to trigger webhooks on data changes. 191 | 192 | Here are some examples of how you can use Hasura: 193 | - CRUD operations with GraphQL ([sample app](https://github.com/hasura/graphql-engine/tree/master/community/examples/todo-auth0-jwt)) 194 | - Building a realtime app (sample apps: [chat](https://github.com/hasura/graphql-engine/tree/master/community/examples/realtime-chat), [poll](https://github.com/hasura/graphql-engine/tree/master/community/examples/realtime-poll), [location tracking](https://github.com/hasura/graphql-engine/tree/master/community/examples/realtime-location-tracking)) 195 | - Sourcing the data for a gatsby site from a postgres database ([sample app](https://github.com/hasura/graphql-engine/tree/master/community/boilerplates/gatsby-postgres-graphql)) 196 | - Triggering browser-based notifications if some data changes ([sample app](https://github.com/hasura/graphql-engine/tree/master/community/examples/serverless-push)) 197 | 198 | ### Learn in 5 minutes (video tutorials) 199 | 200 | Here are a few short videos to help you get started: 201 | 202 | 1. Get started with Hasura on Heroku [(video)](https://www.youtube.com/watch?v=jUObpSl6dTE) 203 | 2. Explore GraphQL queries, mutations and subscriptions [(video)](https://youtu.be/RjnsY-MG4sk) 204 | 205 | ### Support & help 206 | 207 | - Join the [Hasura discord server](https://discord.gg/vBPpJkS). We're super active and someone from the team or the community will help out any time of the day if you have any questions! 208 | - Tanmai will be hanging around at the hackathon if you're present offline! Do say Hi and ask him as many questions as you'd like: 209 | 210 | Tanmai 211 | 212 | ### Docs 213 | 214 | Hasura docs are available at [`docs.hasura.io`](https://docs.hasura.io). 215 | 216 | Here are some other useful links to get you started: 217 | 218 | - [Create Gatsby sites using GraphQL and Postgres](https://github.com/hasura/graphql-engine/tree/master/community/boilerplates/gatsby-postgres-graphql) 219 | - [Example applications built using Hasura](https://github.com/hasura/graphql-engine/tree/master/community/examples) 220 | - [Trigger a Lambda function](https://docs.hasura.io/1.0/graphql/manual/getting-started/first-event-trigger.html) 221 | 222 | To query data from frontend applications, you can use the [Apollo 223 | Client](https://www.apollographql.com/docs/react/). Here are some popular clients: 224 | 225 | - [React](https://www.apollographql.com/docs/react/essentials/get-started.html) 226 | - [Angular](https://www.apollographql.com/docs/angular) 227 | - [Vue](https://www.apollographql.com/docs/react/integrations.html#vue) 228 | 229 | 230 | ### Prizes 231 | 232 | **Amazon gift voucher worth $200** for the team with the best application using Hasura GraphQL Engine. 233 | 234 | 235 | *** 236 | 237 | 238 | # Pilon 239 | 240 | Pilon is an **e-commerce platform** designed and built from the ground up for the JAMstack world. 241 | 242 | Our collection of lightweight, API-first, commerce micro-services enable you to quickly build and test innovative commerce experiences that your customers will love. Use Pilon’s pre-built components to make your store whatever you want it to be while still having the flexibility to change it any time you want. 243 | 244 | We're **opening** our beta platform to hackathon participants and *we'll be there hacking on Pilon while you're hacking on your projects*. 245 | 246 | ### Purpose 247 | 248 | E-commerce stuff. 249 | 250 | Use Pilon to add any of these elements to your project: 251 | * Customer Auth 252 | * Product Catalog / CMS 253 | * Cart + Checkout 254 | * Taking Orders Online 255 | 256 | ##### API endpoints: 257 | REST 258 | * https://api.pilon.io/v1 259 | 260 | GraphQL 261 | * https://api.pilon.io/v1/graphql 262 | 263 | ### Challenges 264 | Sell something. Use Pilon's new GraphQL API + Gatsby to build a super fast, super easy, super sweet commerce experience. 265 | 266 | To get inspired, [*checkout how fast an e-commerce site can be*](https://rachio.com) when its built with **Gatsby** and a GraphQL API. 267 | 268 | ### Docs 269 | 270 | #### Get Started 271 | 272 | * Register [here](https://merchant.pilon.io/register) and use invitation code `XKC-HACKATHON-JAM` to get connected to Pilon. 273 | * Checkout our docs and get your JAMstack app authenticated. 274 | * Checkout our API docs to see what can be done with the platform. 275 | 276 | #### Links 277 | Pilon's main documentation can be accessed at: 278 | * https://docs.pilon.io/ 279 | 280 | Pilon's API docs are here: 281 | * https://api.pilon.io/v1/docs 282 | 283 | An example project using our REST API can found on GitHub here: 284 | * https://github.com/pilon-io/example-fh 285 | 286 | ### Video tutorial 287 | 288 | ### Support & Help 289 | 290 | We'll be at a table at the hackathon to provide lots of support and help. Hit up Garth at our table or in the Pilon channel on Discord. 291 | 292 | We'll be there hacking with you the whole time. 293 | 294 | ### Prizes 295 | 296 | First prize will be a Parrot BEBOP 2 FPV drone. Pretty sweet! 297 | 298 | https://www.parrot.com/us/drones/parrot-bebop-2-fpv 299 | 300 | ![Parrot BEBOP 2 FPV drone](https://www.parrot.com/files/s3fs-public/styles/product_teaser_display/public/compo_bebop_2_fpv_0.png) 301 | 302 | *** 303 | 304 | # Overall Winners 305 | #### The top 6 teams will present to a panel of judges including representatives from freeCodeCamp, Netlify, Formspree, and Fauna. 306 | Note: "Overall" winners are separate from the "API winners". Each API sponsor will have their own challenges and prizes, which you can see above. 307 | 308 | ### Prizes 309 | * Top 6 teams 310 | * Demo your product for around 10 minutes in the GitHub Video Booth to be displayed to the other hackers on televisions around the office, and to be recorded to be posted on line and shared via the freeCodeCamp blog! 311 | * Top 3 Teams 312 | * Present your product on the GitHub stage in front of your fellow hackers! Get your presentation recorded for the livestream, and also recorded for later publication on the freeCodeCamp blog! 313 | * 3rd place: $200 cash prize 314 | * 2nd place: $300 cash prize 315 | * 1st place: $500 cash prize 316 | -------------------------------------------------------------------------------- /getting-started.md: -------------------------------------------------------------------------------- 1 | # Getting Started 2 | 3 | ### Contents 4 | [The JAMstack](#the-jamstack) 5 | [Front-end](#front-end) 6 | [Cloud Functions aka Serverless](#cloud-functions) 7 | [Pre-rendering your app](#prerendering-your-app) 8 | [Deployment & Continuous Integration](#deployment) 9 | 10 | 11 | # The JAMstack 12 | The JAMstack is a powerful new approach for deploying fast, highly scalable sites and applications that don't require backend infrastructure. Thanks to recent advancements in the web platform, developers can now run any web property, from simple sites to complex applications, on global CDNs and without a single web server. Learn more about how the JAMstack works [here](https://jamstackconf.com/what-is-jamstack). 13 | 14 | # Front-end 15 | The JAMstack really shines when you leverage a modern front-end library or framework such as React, Angular, or Vue. What's more, you can get set up almost instantaneously with the incredible static site generators (SSGs) that are available today. 16 | 17 | You can use whatever framework and SSG you please (or even Vanilla JS if you fancy), but here are a few that we like and recommend: 18 | 19 | ## React 20 | 21 | ### Education 22 | 1. Beginners: [Thinking in React](https://reactjs.org/docs/thinking-in-react.html) 23 | 2. Beginners: [ES6 Guide](https://mrzepinski.gitbooks.io/es6-guide/content/) 24 | 3. Beginner - Advanced: [Official React Docs](https://reactjs.org/docs/hello-world.html) 25 | 4. Intermediate: [Official Redux Docs](http://redux.js.org/) 26 | 27 | ### Static Site Generators 28 | Many of today's static site generators have gone above and beyond the humble "boilerplate" label to establish a platform that, paired with a JAMstack architecture, is taking on the monoliths and behemoths such as Wordpress, Drupal, Ruby on Rails, and more. 29 | 30 | Here are a few static site generators that we like and recommned: 31 | 32 | #### [Gatsby](https://gatsbyjs.org/docs) 33 | ``` 34 | npm install --global gatsby-cli 35 | gatsby new gatsby-site https://github.com/gatsbyjs/gatsby-starter-default 36 | cd gatsby-site 37 | gatsby develop 38 | ``` 39 | 40 | #### [Create-React-Native-App](https://github.com/react-community/create-react-native-app) 41 | ``` 42 | $ npm install -g create-react-native-app 43 | $ create-react-native-app my-app 44 | $ cd my-app/ 45 | $ npm start 46 | ``` 47 | 48 | #### What about create-react-app? 49 | 50 | For JAMstack sites, even the create-react-app maintainers recommend Gatsby: 51 | > If your website is mostly static (for example, a portfolio or a blog), consider using Gatsby instead. Unlike Create React App, it pre-renders the website into HTML at the build time. 52 | 53 | Source: https://github.com/facebook/create-react-app 54 | 55 | 56 | ## Vue 57 | ### Education 58 | 1. Beginners: [Why VueJS](https://vuejs.org/) 59 | 2. Beginners: [Getting Started](https://vuejs.org/v2/guide/) 60 | 3. Beginner - Advanced: [VueJS Cookbook](https://vuejs.org/v2/cookbook/) 61 | 4. Beginner - Advanced: [Reactivity System in Vue](https://www.vuemastery.com/courses/advanced-components/build-a-reactivity-system/) 62 | 5. Beginner - Advanced: [Vue CLI](https://cli.vuejs.org/guide/) 63 | 6. Intermediate - Advanced: [VueJS Router](https://router.vuejs.org/) 64 | 7. Intermediate - Advanced: [Vuex](https://vuex.vuejs.org/) 65 | 8. Intermediate - Advanced: [Vue Testing](https://vue-test-utils.vuejs.org/) 66 | 67 | 68 | ### Static Site Generators 69 | #### Vuepress 70 | A popular static-site generator for Vue. Get started [here](https://vuepress.vuejs.org/). 71 | 72 | 73 | # Cloud Functions 74 | Popularly known as "serverless", this is a clever method of integrating backend infrastructure without serving backend code. Your backend code lives on another service, such as AWS Lambda or Microsoft Azure, and links up with your front-end code via JavaScript functions. This architecture not only makes your websites faster, more secure, and really cool -- it also saves you a substantial amount of money. While traditional server-side code will run indefinitely, Lambda functions will only run when called, and charge you per hundred-millisecond. AWS Lambda is currently the most popular of these providers, and you can see their pricing guide [here](https://aws.amazon.com/lambda/pricing/). 75 | 76 | Despite its popularity, if you've ever interacted with AWS services, you'll probably agree that it's not the most user friendly or intuitive. Fortunately there are plenty of services out there that can help you get started with Lambda functions without ever seeing their GUI. 77 | 78 | ## Netlify Functions 79 | Netlify lets you deploy Lambda functions without an AWS account, and with function management handled directly within Netlify. Your functions are version-controlled, built, and deployed along with the rest of your Netlify site, and we will automatically handle service discovery through our built-in API gateway. This eliminates overhead and brings the power of Deploy Previews and rollbacks to your functions. 80 | 81 | Get set up [here](https://www.netlify.com/docs/functions/). 82 | 83 | ## Serverless 84 | With the Serverless Framework you can define your entire Serverless application, utilizing popular Serverless technologies like AWS Lambda, with a simple yaml configuration file. You can deploy from a simple CLI interface to popular cloud platforms including AWS, Microsoft Azure, Google Cloud Platform and more. 85 | 86 | Get started [here](https://serverless.com/framework/docs/) 87 | 88 | # Prerendering Your App 89 | Prerendering is a process to preload all elements on the page in preparation for a web crawler to see it. A prerender service will intercept a page request to see if the user-agent viewing your site is a bot and if the user-agent is a bot, the prerender middleware will send a cached version of you site to show with all JavaScript, Images, etc are rendered statically. 90 | 91 | ### Prerender Resources 92 | - [Prerender.io](prerender.io) 93 | - [Brombone](https://www.brombone.com/) 94 | - [SEO.js](http://getseojs.com/) 95 | - [SEO4Ajax](http://www.seo4ajax.com/) 96 | - [Prerender.cloud](https://prerender.cloud/) 97 | - [Prerender SPA npm plugin](https://github.com/chrisvfritz/prerender-spa-plugin) 98 | - [Netlify Prerendering docs](https://www.netlify.com/docs/prerendering/) 99 | 100 | 101 | # Deployment 102 | 103 | With the JAMstack, the promise of a truly modern web architecture is not just limited to development, performance, and security. It also extends to the often-frustrating user experience of deployment, hosting, and continuous integration. 104 | 105 | What if you could do all of that with a simple `git push`? What if you didn't have to worry about FTP, https, url configuration, SSL, or dealing with the AWS console for your Lambda functions? 106 | 107 | That is what Netlify does for you and more. You can learn more about how to work and deploy with Netlify here: https://www.netlify.com/docs/ 108 | 109 | For your project to be considered in this hackathon, you must deploy to Netlify. 110 | -------------------------------------------------------------------------------- /judging-protocol.md: -------------------------------------------------------------------------------- 1 | # Judging Protocol & Schedule 2 | *Note: This document is tentative. Times are subject to change* 3 | 4 | # Rules 5 | If you are competing for prizes, you must: 6 | 7 | 1. Use the JAMstack. You must not build a monolithic app or run a web server. 8 | 2. Max team size: 6 (Recommended team size: 3-5) 9 | 3. Abide by our code of conduct 10 | 4. To win API prizes, you must use their API. You can review them in [apis.md](./apis.md) 11 | 12 | # Judging Criteria 13 | 21 | 22 | 23 | ## Qualifying Pitches 24 | **3:00 - 5:00pm Sunday, Main Stage** 25 | You should be present by the main stage at least 5 minutes before your presentation is scheduled to start. 26 | This time may be adjusted depending on the number of hackers and teams present. 27 | 28 | * 1 minute, **hard stop** 29 | * 40 seconds Q + A 30 | 31 | * We recommend practicing your pitch. Cut out any fluff. Format: 32 | * Attention-grabbing headliner 33 | * What the problem is that you're solving 34 | * Why your product is the solution 35 | * Demo of your product 36 | * Remember - you have 1 minute! We will stop you at 60 seconds exactly. 37 | * Arrive to stand in line at least 5 minutes before your scheduled start time. If you are not at the GitHub stage at your designated time, you will be disqualified. 38 | * Ensure that your demo is ready & working; you will not get another chance. 39 | * Got presentation slides but no demo? Sure, that's ok. But it's very likely that only working prototypes will advance you to the next round. 40 | 41 | Review your team's place in the queue for presentations here: **Posted at 2:00pm Sunday in the Discord** 42 | 43 | We are using the US Navy Observatory Master Clock for time. If you're on a Mac, you should be synced to this, but it's worth verifying to make sure: 44 | https://www.time.gov 45 | 46 | **If you are not present for your scheduled presentation, you will be disqualified from overall prizes/presentations.** 47 | 48 | #### The top 6 teams will move on to present on a judging panel, where we will discuss your project on video for around 10 minutes. 49 | 50 | Note that the top 6 teams are contending for the *overall* hackathon winers. API sponsors may opt to select winners outside of this top 6. 51 | 52 | **The top 6 teams will be present and take questions on video, which will be streamed to the televisions throughout the GitHub office. If you do not wish to be on video, you can opt to not join your team in your presentation.** 53 | 54 | ## Top 6 Teams Panel 55 | **5:30 - 6:30** 56 | 57 | Winners will be announced in the Discord channel #announcements around 5:00pm. 58 | 59 | ## Any commits after 6:00pm will disqualify you from overall prizes and presentations 60 | 61 | ## Dinner, Beer, & Wine 62 | **6:00** 63 | 64 | This is your time to stop coding, chill, eat, and watch the top 6 teams show off their projects on video 65 | 66 | 67 | ## Top 3 Teams Presentation 68 | **7:20, Main Stage** 69 | 70 | The top three teams will deliver 7-minute presentations on stage 71 | 72 | ## API Awards 73 | **7:45, Main Stage** 74 | 75 | API Sponsors will announce the winners of their prizes 76 | 77 | ## Overall Awards 78 | **8:00, Main Stage** 79 | 80 | The top 3 teams (presenting top 3) will be awarded their prizes. 81 | 82 | ## Mingling 83 | **8:10 - 9:00** 84 | 85 | Feel free to stick around and mingle for an hour or so 86 | 87 | 88 | # A note on time 89 | 90 | Once we get into the swing of things, actual times such as the API Awards and Presentations may vary. Please note that time for your **Qualifying Pitch** will **not** vary. 91 | 92 | # Top 3 Presentations: Presentation Guideline 93 | This is a guideline only, feel free to deviate as you wish 94 | 95 | ### The Setup (1 Min) 96 | Introduce: 97 | * Yourself 98 | * The Problem 99 | * The Solution 100 | 101 | ### The Demo (4.5 min) 102 | #### Your Product 103 | * Why it solves the problem 104 | * How it solves the problem 105 | * Show off your product 106 | * How you're using specific API's or services 107 | 108 | ### The Tech (1 minute) 109 | * What technologies did you use to build this? 110 | * What challenges did you face while building this? 111 | * How did you overcome those challenges? 112 | 113 | ## The Sign-off 114 | * Briefly: The problem 115 | * Briefly: Why your product solves it 116 | * Who you are and contact info, if desired 117 | -------------------------------------------------------------------------------- /schedule.md: -------------------------------------------------------------------------------- 1 | # Schedule 2 | 3 | Note: This schedule is a guideline. Actual times may vary. Watch for announcements in the Discord channel `announcements`. 4 | 5 | ## Saturday, November 3 6 | 9:00am - Doors open 7 | 9:00 - 10:00 - Check-in, coffee, mingle & form teams 8 | 10:00 - 11:20 - Welcome + Keynote (Main Stage) 9 | 11:20 - 12:30pm - Form teams, discuss projects and procedure 10 | 12:30 - 1:00 - Lunch 11 | 1:00 - 6:00 - Hacking & Procedural Interviews 12 | 6:00 - 6:30 - Light dinner 13 | 6:30 - 8:45 - Hacking 14 | 9:00pm - Doors close 15 | 16 | ## Sunday, November 4 17 | 9:00am - Doors open 18 | 9:00 - 10:00 - Check-in, coffee 19 | 10:00 - 11:00 - Welcome + Keynote (Main Stage) 20 | 10:45 - 12:30 - Hacking 21 | 12:30 - 1:00 - Lunch 22 | 1:00 - 6:00 - Hacking 23 | 3:00 - 5:00 - Teams present their projects to judges (actual time may change depending on number of hackers and teams) 24 | 5:00 - 5:30 - Judges decide top 6 teams, no order 25 | 6:00 - Food arrives 26 | 6:00 - 7:00 - Judges interview top 6 teams for video 27 | 7:30 - 8:00 - Top 3 teams present (Main Stage) 28 | 8:00 - 8:10 - API Awards Announced 29 | 8:10 - 8:15 - Top 3 teams Awards Announced 30 | 8:15 - 9:00 - Mingling 31 | 9:30pm - Doors close 32 | -------------------------------------------------------------------------------- /teams.md: -------------------------------------------------------------------------------- 1 | # Hackathon Teams 2 | 3 | ### Create a PR 4 | 5 | ### STYLE GUIDE: 6 | 7 | ``` 8 | # Project Name 9 | ### Less than 240 Characters describing what we're building. Include external links here if desired 10 | * Teammates: 11 | - Teammate Name (@discordUserProfileName) 12 | - Teammate Name (@discordUserProfileName) 13 | - Teammate Name (@discordUserProfileName) 14 | * Seeking Teammates: Yes/No 15 | * [Project URL](https://github.com/your-profile/your-project-name) 16 | * Project Name (ok to say tbd and update later) 17 | ### Project Q&A: 18 | 1. What are you going to build? 19 | // your answer here 20 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 21 | // your answer here 22 | 3. What is your plan to execute this idea? 23 | // your answer here 24 | 25 | *** 26 | ``` 27 | 28 | Copy the above code snippet in its entirety and add it to the BOTTOM of this document. Then edit with your information. Don't forget the `***` three stars, and don't forget to `git pull origin master` and `git rebase master` into your feature branch before you push to origin! 29 | 30 | *** 31 | 32 | # Hackathon Style Guide Example Entry 33 | ### This project exists solely to show you how to edit this document. Fork this repo and make a PR to add your team at the BOTTOM of this list -- below the last 3 stars! Don't forget to include the 3 stars in your entry. Don't forget to `git pull origin master` and `git rebase master` into your feature branch before you push to origin! 34 | * **Teammates**: 35 | - Benjamin Dunphy (@benghamine) 36 | - Quincy Larson (@QuincyLarson) 37 | - Matt Biilmann (@biilmann) 38 | * **Seeking Teammates**: No 39 | * [GitHub URL](https://github.com/your-profile/your-project-name) 40 | ### Project Q&A: 41 | 1. What are you going to build? 42 | // your answer here 43 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 44 | // your answer here 45 | 3. What is your plan to execute this idea? 46 | // your answer here 47 | 48 | *** 49 | 50 | # QXC 51 | ### Find and discover current art interests and identify local galleries in the area. 52 | - **Teammates**: 53 | - Ian Wilson (@iwilsonq#4979) 54 | - Roman Morozov (@sublimeye#6781) 55 | - Simon Baev (@simon#3299) 56 | - Vadim Dermanovskiy (@noodly#7880) 57 | - Dennis Xing (@dennis#1656) 58 | - **Seeking Teammates**: No 59 | - [Project URL](https://github.com/iwilsonq/qxc) 60 | ### Project Q&A: 61 | 1. What are you going to build? 62 | An app that discovers your artistic preference and shows you local galleries catered to your taste. After swiping on art pieces, you are presented with a navigator to find different galleries in your area. 63 | 64 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 65 | The Fauna API for data storage, Formspree for feedback, Clarifai for recommendation and discovery. 66 | 67 | 3. What is your plan to execute this idea? 68 | We will build a React app using the APIs mentioned. Our designer will prototype the flow and rest of the team will build out the infrastructure. 69 | 70 | *** 71 | 72 | # SmarTea Pants 73 | ### A trivia study app for contestants who are trying to qualify for the TV gameshow Jeopardy 74 | * Teammates: 75 | - Fay Yang (@CodeFay) 76 | - Colin King-Bailey (@ckingbailey) 77 | - Neil Ricci (@iccir919) 78 | - Angela Wang (@awangster) 79 | * Seeking Teammates: No 80 | * [SmarTea Pants repo on Github](https://github.com/CodeFay/smarteapants) 81 | * SmarTea Pants 82 | ### Project Q&A: 83 | 1. What are you going to build? 84 | A mobile-responsive, trivia study app to help contestants qualify for the TV gameshow Jeopoardy. 85 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 86 | Netlify, Fauna, Wikipedia, more to come! 87 | 3. What is your plan to execute this idea? 88 | Track workflow in waffle.io. Using Gastby and Netlify for front end, FaunaDB to host questions, and Wikipedia for more fun facts. 89 | 90 | *** 91 | 92 | # RaffleGator 93 | ### Making giveaway for creators and users easier and more accessible / propaGATING creators 94 | * Teammates: 95 | - Jun Sub Choi (@Stard) 96 | - Andrew Ngo (@AndyNoAwkward) 97 | - David Mai (@2BiK) 98 | - Alan Fu (@BrandHeart) 99 | - Selena Xu (@SelenaX) 100 | - Jacob Castro (@Jacobcastro) 101 | * Seeking Teammates: No 102 | * [Project URL](https://github.com/RaffleGator/RaffleGator) 103 | 104 | ### Project Q&A: 105 | 1. What are you going to build? 106 | Making giveaway for creators and users easier and more accessible / propaGATING creators 107 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 108 | faunaDB, netlify, fromspree, twitter api, instagram api 109 | 3. What is your plan to execute this idea? 110 | Delegate each microservices and api/framework to each team member, helping each other along the way of learning new and exciting tech. 111 | 112 | *** 113 | 114 | # Ingredea 115 | ### With Ingredea Foodies can now explore the ingredients and recipes for their favourite dishes. 116 | * Teammates: 117 | - Abhijeet Saxena (@rockyy) 118 | - Arjun Porwal (@Arjun) 119 | - Paras Arora (@paras594) 120 | - Vishang Soni (@TrekLatte) 121 | * Seeking Teammates: No 122 | * [Project Repo](https://github.com/rocky93/ingredea) 123 | * [Check Out Ingredea](https://ingredea.netlify.com/) 124 | *** 125 | 126 | # Air Quality App 127 | ### we are building a web app using [AirVisualAPI](https://www.airvisual.com) and on PWA with push notifications 128 | * Teammates: 129 | - Teammate Name (@irfanSyed17#9502) 130 | - Teammate Name (@Jiggly Poof#8959) 131 | - Teammate Name (@sammieee#0836) 132 | - Teammate Name (@km.#3850) 133 | * Seeking Teammates: No 134 | * [Project URL](https://github.com/syedirfan7/airqualityApp) 135 | *** 136 | 137 | # Count'em All 138 | ### A simple app to count the number of people attending a gathering 139 | * Teammates: 140 | - Shrey Dabhi (@sdabhi23) 141 | - Sohel Shaikh (@thesohelshaikh) 142 | * Seeking Teammates: No 143 | * [Project URL](https://github.com/sdabhi23/count-em-all) 144 | * Count'em All 145 | 146 | *** 147 | 148 | # Job portal with live video interviewing 149 | ### Me and our team building(on the process) a user-friendly job portal with the live video interviewing. 150 | 151 | # Power Pushers 152 | ### App Description TBD 153 | * Teammates: 154 | - Brian Kilrain (@BK) 155 | - Warren Schrader (@ShadowBoxerGuy) 156 | - Tia Esguerra (@Tia) 157 | - Murrium Zaheer (@murrium123) 158 | - Perry Chow (@perry) 159 | - Seeking Teammates: No 160 | - [Project Repo](https://github.com/PowerPushers/FindMyGetaway) 161 | - Project Name: Find My Getaway 162 | 163 | ### Project Q&A: 164 | 1. What are you going to build? 165 | A webapp allowing users to find vacation options based on their own submitted photos 166 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 167 | - Fauna for DB layer 168 | - Clarafai for image classification 169 | - Formspree for forms 170 | 3. What is your plan to execute this idea? 171 | Project managament through Trello 172 | MVP - display all possible vacations and iterate to incorporate Clarafai and Formspree backed features 173 | 174 | 175 | *** 176 | 177 | # BadCoders 178 | ### tbd 179 | 180 | * Teammates: 181 | - Dinesh (@1532j0004kg) 182 | - Thinnappan (@thinnappan) 183 | - Anush (@Anushkumar06) 184 | * Seeking Teammates: No 185 | * [Project Repo](https://github.com/1532j0004kg/hacks) 186 | * Interactive portal 187 | 188 | *** 189 | 190 | # PB&JAM 191 | ### Real-time blazing-fast, image-recognition, machine-learning picture scavenger hunt 192 | * Teammates: 193 | - Austin (@austintackaberry) 194 | - Reuben (@radotreyes) 195 | - Gin (@wongco) 196 | - Brandon (@brandonstinson) 197 | - Vincent (@vtam2012) 198 | * Seeking Teammates: Sure! 199 | * https://github.com/radotreyes/SICC-PICCS 200 | * __SICC PICCS__ 201 | 202 | *** 203 | 204 | # AMA 205 | ### An app for people to host personalized Q&As! 206 | * Teammates: 207 | - Dhron Joshi (@dhron) 208 | - Mattias Eyram (@mattias) 209 | - Yusuf Khaled (@freeman-cortez) 210 | * Seeking Teammates: No 211 | * [Project URL](https://github.com/mattiaseyram/JAMStack-Hackathon-Team-App) 212 | * AMA 213 | 214 | *** 215 | 216 | # Codelaboration 217 | ### An app to help you find members for your coding projects 218 | * Teammates: 219 | - Roger (@Rawgher) 220 | - Enea (@eneaantonicelli) 221 | - Prash (@prashanthr) 222 | * Seeking Teammates: Yes 223 | * [Project URL](https://github.com/Rawgher/Codelaboration) 224 | * Codelaboration 225 | 1. What are you going to build? 226 | An application that will allow coders to share their projects and look for developers to help them out. 227 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 228 | We currently plan on using Fauna, Formspree and Netlify. We may incorporate more as the project progresses. 229 | 3. What is your plan to execute this idea? 230 | Scope out the tasks, make mocks of the project, then split up components and code. 231 | 232 | *** 233 | 234 | # Roasted 235 | ### TBD 236 | * Teammates: 237 | - Mike Preis (@mikepreis) 238 | - Anwana Ntofon (@antofon) 239 | - Arvin Lin (@chogio) 240 | * Seeking Teammates: No 241 | * [Project repo](https://github.com/mikepreis/roasted) 242 | 243 | *** 244 | 245 | # MakeSquad 246 | ### Business card app to store user information in a central database and make it accessible using image recognition and augmented reality. 247 | * Teammates: 248 | - Faith (@gottaHaveFaith#8156) 249 | - Stephanie (@Zephany#3690) 250 | - Edwin (@ecloud#6259) 251 | - Johnathan (@jachen3#4296) 252 | - Tahshara(@tahshara#3310) 253 | * Seeking Teammates: No 254 | * [Project Repo](https://github.com/Make-Squad/Networq) 255 | * networq 256 | 257 | *** 258 | # Cartogram 259 | ### Create travel itineraries from just a picture and share your travels! 260 | * Teammates: 261 | - Samantha Maclaren (@Samantha M) 262 | * Seeking Teammates: No 263 | * [Project Repo](https://github.com/samantha-m/Cartogram) 264 | * [Check Out Cartogram](https://hopeful-chandrasekhar-ebe6b9.netlify.com/) 265 | 266 | *** 267 | 268 | # Where in the World 269 | ### "Where was that photo taken?" a real world trivia web app identifying the location of photos in real time 270 | * Teammates: 271 | - Jeff Appareti (@Jeff Appareti#4361) 272 | - Tadas Antanavicius (@Tadas Antanavicius#9028) 273 | - Tyler Vick (@TJ Vick#4151) 274 | - Gabe Greenfield (@gabe#4067) 275 | * Seeking Teammates: No 276 | * [Project URL](https://github.com/gaberoo322/where-in-the-world.git) 277 | * Project Name (Where in the World) 278 | 1. What are you going to build? 279 | We’re building a live social game: Where in the World. Players go to the website on their mobile phones and join the “lobby”. We periodically “start a game”, whereupon all the players are presented with an image we have queued up. The image is of something somewhat recognizable. Players drop a pin on the provided map, indicating where they think the picture was taken. The game is over in 30 seconds, and the winners (by smallest distance from the actual location) are displayed on the next screen. 280 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 281 | Hasura, Netlify, Google Maps (stretch goal), Clarifai (far stretch goal), Formspree 282 | 3. What is your plan to execute this idea? 283 | Design data/domain model all together --> Pair 1 works on setting up Create React App w/ Apollo, Netlify deploy --> Pair 2 works on getting model into Hasura, preparing endpoint --> Design screens, mocks all together --> Divvy out the front end development tasks to get to functional MVP --> Time permitting, integrate Maps API for answer. Otherwise, implement multiple choice system --> Final preparation for demo (set up actual data) --> Time permitting, create Clarifai AI 284 | 285 | *** 286 | 287 | # Cocoon 288 | ### A forum that allows for posting of images that can be configured for rejecting NSFW images. Also supports image tagging. 289 | * Teammates: 290 | - Alex Pitzer (@hoop) 291 | - Mandy Trinh (@mandytrinh) 292 | - Billy Le (@billyle) 293 | - Jason Serafica (@teknoformula) 294 | * Seeking Teammates: Yes 295 | * [Project URL](https://github.com/reztip/cocoon) 296 | * Project Name (Cocoon) 297 | 298 | *** 299 | 300 | # Russian Hackers 301 | ### tbd 302 | * Teammates: 303 | - Ron (@vokoshyv) 304 | - Kevin (@jamalthejanitor#1701) 305 | * Seeking Teammates: No 306 | * [Project URL (Subject to change...)](https://github.com/vokoshyv/tea_i_drink_with_JAM_and_bread) 307 | * Project Name - tbd 308 | 309 | 310 | *** 311 | 312 | # Ichi-Go Ichi-E 313 | ### tdb 314 | * Teammate: 315 | - Joey Chung (@jchung05) 316 | - Jose Ramon Aleman (@jraleman) 317 | - Megan Okerlund (@mokerlund) 318 | - Giovani Aguirre (@its-gio) 319 | * Seeking Teammates: No 320 | * [Project URl](https://github.com/jraleman/jamstack-2018) 321 | ###Project Q&A: 322 | 1. What are you going to build? 323 | An application that takes cafeteria data and visualizes customer data trends. 324 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 325 | We currently plan on using Netlify and Hasura. Specifically for our use-case, we need our school's internal API and will need one additional data visualizer API. 326 | 3. What is your plan to execute this idea? 327 | https://github.com/jraleman/jamstack-2018/blob/joey/PFD.pdf 328 | 329 | *** 330 | 331 | # Imposterly 332 | ### We are builing a web app where users (from the tech industry) can post about their imposter syndrome and receive community support. 333 | * Teammates: 334 | - Vikram Raja (@Vik1395) 335 | - Matt Rodigheri (@maaatt) 336 | - Abel Regalado (@abel) 337 | - Martin Vargas Vega (@dev_latino) 338 | - Shane Tajima (@shane) 339 | * Seeking Teammates: No 340 | * [Project URL (Subject to change)](https://github.com/abelrr/imposter_in_tech) 341 | * Imposterly (probably rename later) 342 | ### Project Q&A: 343 | 1. What are you going to build? 344 | A web app where users (from the tech industry) can post about their imposter syndrome and receive community support. 345 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 346 | Formspree, Hasura (maybe), Github (maybe) 347 | 3. What is your plan to execute this idea? 348 | // your answer here 349 | 350 | *** 351 | 352 | # [CaptionThis!](https://captionthis.netlify.com) 353 | ### The project is about an app that displays a random gif. A user can submit a caption to the gif. A user can also upvote the favorite captioned gifs that will be displayed on the sidebar. 354 | * Teammates: 355 | - Vijay Lama (@absurdist) 356 | - Sumit Bagga (@daggerdrone) 357 | - David Carter (@dajocarter) 358 | 359 | * Seeking Teammates: No || 1 mate welcome. :) 360 | * [Project Repo](https://github.com/dajocarter/caption-this) 361 | * CaptionThis! 362 | 363 | # jamhouse 364 | ### Jamhouse is a tool built on top of Google Lighthouse, used to measure your website's performance over time. 365 | 366 | * Teammates: 367 | - Cam (@cambodia87) 368 | - Andres (@Andres) 369 | - Diego (@diegolamanno) 370 | - Henry (@mmonkey) 371 | - Danny (@talonz) 372 | * Seeking Teammates: No 373 | * [Project URL](https://github.com/diegolamanno/jamhouse) 374 | * Jamhouse 375 | 376 | ### Project Q&A: 377 | 1. What are you going to build? 378 | Jamhouse is a tool built on top of Google Lighthouse, used to measure your website's performance over time. 379 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 380 | We plan to use FaunaDB and Formspree 381 | 3. What is your plan to execute this idea? 382 | - We will build a site homepage, where the user can enter their website url, or request a webhook url that they can add to their netlify site. 383 | - Once the user submits, it will trigger a lambda function, which will run the lighthouse CLI tool, and commit the lighthouse results to a FaunaDB. 384 | - When the faunaDB successfully receives a new entry, it will trigger our website to build a page with their ongoing results over time compared against the user's current build. 385 | 386 | *** 387 | 388 | # FiveFeed 389 | ### A daily curated list of trending resources to keep on your radar 390 | * Teammates: 391 | - Justin Kaseman (@Jk) 392 | - Frank Faustino (@frankfaustino) 393 | - Niki Esfandiari (@NEsfendiari37) 394 | - Sumayyah Asgar (@Sumi) 395 | - Hunter Casbeer (@spacexengineer) 396 | - Kohei Arai (@kohei2301) 397 | * Seeking Teammates: No 398 | * [Project URL](https://github.com/FCC-Jamstack-Hackathon/five) 399 | * Project Name: FiveFeed (TBD) 400 | 401 | ### Project Q&A: 402 | 1. What are you going to build? 403 | The solution to newsletter information overload. A curated newsfeed of only 5 of the best links, articles, and events - all in one place. 404 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 405 | Tech Stack: Gatsby harnessing React and GraphQL, Fauna, Formspring 406 | 3. What is your plan to execute this idea? 407 | Split into groups of 3 Front-end developers and 3 Back-end developers. 408 | 409 | *** 410 | 411 | # Hackaform 412 | 413 | ### "The web application which helps you to find and form hackathon dream team." 414 | 415 | - Teammates: 416 | - Scott Iwako (@iwakoscott) 417 | - Miguel Ruiz (@migzruiz) 418 | - Gerardo Fernandez (@gerardofer) 419 | - Lena Ryoo (@lena) 420 | - Sarmishta Burujupalli (@Sarmishta) 421 | - Evghenii Ghimazitdinov(@evgimov) 422 | - Seeking Teammates: No 423 | - [Project URL](https://github.com/evgimov/hackaform) 424 | - Project Name: Hackaform 425 | 426 | ### Project Q&A: 427 | 1. What are you going to build? 428 | We are going to build a web application to help developers attending hackathons find their dream team. 429 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 430 | Formspree, Fauna DB, Netlify 431 | 3. What is your plan to execute this idea? 432 | Divide and conquer! We have one person overseeing the repository, two people working on the back end (FaunaDB), one person setting up the Netlify Identity widget, and two others designing the UI. 433 | 434 | *** 435 | 436 | # Quilt 437 | ### Social News Site 438 | * Teammates: 439 | - Jamarr Edwards (@jamarr#8205) 440 | - Yutam Hacohen (@YotamHa#7378) 441 | - Claudio Bardales (@Chit0) 442 | - Jacqulline Beltran (@jackie#7264) 443 | - Joshua Aguilar (@mrsnuz#6367) 444 | * Seeking Teammates: NO 445 | * [Project Repo](https://github.com/joshuaaguilar20/Quilt) 446 | * Quilt 447 | 448 | # POWPAL 449 | ### TBA 450 | * Teammates: 451 | - Yvette Tran (@trantastic) 452 | - Teammate Jeff (@jcohen120) 453 | - Teammate Du (Dawn) Tram (@du-dawn) 454 | - Andrew Yang (@yzy) 455 | - Anna Khardina-Vaisman (@AnutaK) 456 | - Mariya Mego Vela (@mash-a) 457 | * Seeking Teammates: No 458 | * [Project URL](https://github.com/Trantastic/powpal) 459 | * Project Name: POWPAL 460 | 461 | ### Project Q&A: 462 | 1. What are you going to build? 463 | A web app that empowers voters with information to make informed decisions. 464 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 465 | Formspree, Fuana, Clarifai, Hasura, Pilon, ProPublica, Civic Information API 466 | 3. What is your plan to execute this idea? 467 | Create user story, research APIs, divide roles, and have fun! :) (except for Andrew) 468 | 469 | *** 470 | 471 | # Quiche Friends 472 | ### TBD 473 | * Teammates: 474 | - Kevin(@kvrmd) 475 | - Joshua(@jsadsad) 476 | - Jimmy(@jimmy-guzman) 477 | - Nestor(@nesanime) 478 | - Lele(@lelelew) 479 | - Ian(@ianserlin) 480 | * Seeking Teammates: No 481 | * [Project URL](https://github.com/jimmy-guzman/quiche-friends) 482 | ### Project Q&A: 483 | 1. What are you going to build? 484 | A trusted political action platform. 485 | 486 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 487 | - Formspree 488 | - Clarifai 489 | - FaunaDB 490 | - Possibly IPStack for geolocation information 491 | 492 | 3. What is your plan to execute this idea? 493 | Using Formspree to send emails to representatives. Using Fauna DB for database interaction and database modeling when users are participating in political discussions. We will use Clarifai's Custom Face Recognition to authenticate users (vs. Troll Bots) so that discussions are real and unaffected. 494 | 495 | * Project Name - TBD 496 | 497 | *** 498 | 499 | # Image Recognition Assistant 500 | ### Image Recongition Assistant is a React component that can be used anywhere. The component itself is a widget that takes in an image as an input and computes data related to the image, such as tags for the image. 501 | * Teammates: 502 | - Maximo Macchi (@max.1096) 503 | - Jordan Henderson (@Jman219) 504 | - Nathan Chica (@ch1cachu) 505 | - Shajia Abidi (@abidishaija) 506 | * Seeking Teammates: No 507 | * [Project URL] (https://github.com/maximomacchi/image-recognition-assistant) 508 | 1. What are you going to build? 509 | Widget that will take image as input and return tags related to that image along with other data. We will also be building an app that uses our created widget to show it in action. 510 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 511 | Clarifai. 512 | 3. What is your plan to execute this idea? 513 | Using pure React. Based off of create-react-app-lambda. Will be hosted on Netlify. Components will be written in parallel by team members. Components that will be used so far are: 514 | * Main App - stores state of entire app; handles views 515 | * API handler - handles calls to API and receiving data 516 | * View components that render data in various forms 517 | 518 | *** 519 | 520 | # NU-RD 521 | ### We are building a website tool dedicated to assisting teaching professionals translating a numerical equation into a word equation. 522 | * Teammates: 523 | - Veronica 524 | - Lydia 525 | - Amy 526 | - Rich 527 | - Blake 528 | * Seeking Teammates: No 529 | * [Project URL](https://github.com/amychan331/nu-rd) 530 | * NU-RD 531 | ### Project Q&A: 532 | 1. What are you going to build? 533 | // A website tool dedicated to assisting teaching professionals translating a numerical equation into a word equation. 534 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 535 | // Netlify, Fauna DB, React 536 | 3. What is your plan to execute this idea? 537 | // TBD 538 | 539 | *** 540 | 541 | # VisiJAM 542 | ### An application that visualizes data about participants of the 2018 JAMstack Hackathon 543 | * Teammates: 544 | - Sean Nguyen (@Sea) 545 | - Ilan Kaim (iknowmagic) 546 | - Sarah Kaplan (skaplan) 547 | - Juan Areces (@juanA) 548 | - Zubin Pratap (@Zubin) 549 | - Dave Lau (@doubleUTF) 550 | * Seeking Teammates: Yes/No 551 | * [Project URL](https://github.com/your-profile/your-project-name) 552 | * Project Name (ok to say tbd and update later) 553 | ### Project Q&A: 554 | 1. What are you going to build? 555 | A survey form that visualizes data about the participants of the 2018 Jamstack Hackathon and helps users find compatible group members for future hackathons. 556 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 557 | Formspree, Fauna, Highcharts, React 558 | 3. What is your plan to execute this idea? 559 | Determine the requirements to make the application run, develop a prototype, decide what tools and libraries we are going to use, create a wireframe of what the actual page will look like, delegate tasks and start building the application, finally test it to make sure it works as intended. If we have additional time, we might want to implement more features. 560 | 561 | *** 562 | 563 | # SocialLearn 564 | ### Learn a new language from your social media with the power of machine learning and your friends' selfies. 565 | * Teammates: 566 | - Manuel Moya (@manuelmoya#2014) 567 | - Kyle Smith (@kyle#6166) 568 | - Robert Wolf (@Robert Wolf#6955) 569 | - Ryan Wiemer (@ryanwiemer#1547) 570 | - Anil Kumar Nandamuri (@nandu#6388) 571 | * Seeking Teammates: No 572 | * [Project URL] (https://github.com/ryanwiemer/FCC-Hackathon-2018) 573 | 1. What are you going to build? 574 | An app which helps people learn new languages based on photos in their Instagram feed 575 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 576 | Clarifai and Instagram 577 | 3. What is your plan to execute this idea? 578 | Using pure React. Based off of create-react-app-lambda. Will be hosted on Netlify. Components will be written in parallel by team members. Components that will be used so far are: 579 | * Research APIs 580 | * Divided into two groups: 581 | * API Integration 582 | * Front End / Design 583 | * Whiteboard the user experience flow and identify potential bottlenecks or technical challenges 584 | * Agree on application and data structure 585 | * Front End / Design team to start creating the “dumb” components 586 | * API team to work on authentication and data management 587 | Work together to combine and wire up an MVP 588 | * Polish and look for opportunities to improve visually or otherwise 589 | 590 | *** 591 | 592 | # Rental Scope 593 | ### Rental property review application 594 | * Teammates: 595 | - Kalsang Bhutia (@Avosammy) 596 | - Hannah Lee (@hannah) 597 | - Vy Nguyen (@vynguyen) 598 | - Shoua Chang (@Shoua Chang) 599 | * Seeking Teammates: No 600 | * [Project URL](https://github.com/RunHannah/rental-scope) 601 | * Project Name: Rental Scope 602 | ### Project Q&A: 603 | 1. What are you going to build? 604 | Our team is building an application to allow tenants to review rental properties. 605 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 606 | The APIs that we are using will be: formspree and Fauna 607 | 3. What is your plan to execute this idea? 608 | Our plan to execute this idea is research content, design layout and implement a first iteration of the application. 609 | 610 | *** 611 | 612 | # DreamMakers 613 | ### A website that provides scripts for youtube videos. 614 | * Teammates: 615 | - Nyapal (@fatbellynya) 616 | - Jasmin (@jazzi) 617 | - KJ (@sadboykj) 618 | * Seeking Teammates: No 619 | * [Project Repo](https://github.com/jazz2900/dream-makers) 620 | * Netlify, YouTube 621 | * Project Name - tbd 622 | 623 | # YoTravellers 624 | #### A Webapp to create travel albums in a public/private model. 625 | * **Teammates**: 626 | - Ashwin (@ashwin47#1900) 627 | * **Seeking Teammates**: No 628 | * [GitHub URL](https://github.com/ashwin747/YoTraveller-JAMStack) 629 | ### Project Q&A: 630 | 1. What are you going to build? 631 | A webapp to create travel albums. 632 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 633 | The APIs that I will be using are: Fauna and Hasura GraphQL. 634 | 3. What is your plan to execute this idea? 635 | My plan is to design Data flow diagram, Develop and Deploy. 636 | 637 | *** 638 | 639 | # Lazy Calorie Counter 640 | ### Upload an image of the food and get keep track of what you eat based on ingredients 641 | * Teammate: 642 | - Victor Tsang (@vktr) 643 | - Allen Wong (@artist) 644 | 645 | * Seeking Teammates: No 646 | * [Project URl](https://github.com/victorwltsang/lazyCalorieCounter) 647 | ### Project Q&A: 648 | 1. What are you going to build? 649 | A food dairy app where you upload an image and give an estimate calorie based on ingredients. 650 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 651 | The APIs that we are using will be: clarifai, Fauna 652 | 3. What is your plan to execute this idea? 653 | Our plan to execute this idea is research content, design layout and implement a first iteration of the application. 654 | 655 | *** 656 | 657 | # Tripit 658 | ### Track, save, and rate day trip agendas 659 | * Teammates: 660 | - Patrick San Juan (@pdotsani) 661 | - Adam Guymon (@aguymon) 662 | - Joshua Kang (@guppykang) 663 | - Jingyi Ding (@jingyi) 664 | * Seeking Teammates: No 665 | * [Project Repo](https://github.com/guppykang/TripIt) 666 | * [TripIt!](https://tripit.netlify.com) 667 | 668 | --------------------------------------------------------------------------------