├── 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, then you were sent a ticket to the email address provided in your application. 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 an in-person team has remote collaborators, the team will be disqualified. 12 | 13 | ## Can the online and in-person hackers still chat with one another? 14 | Of course. We're all in the same Discord chat group. And since this hackathon is largely about education, the in-person and 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. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 2018 Online freeCodeCamp JAMstack Hackathon 2 | 3 | If you want to succeed at this hackathon, please read this document and its subsequent files in their entirety before you begin. 4 | 5 | ## Checklist 6 | Please read the following carefully, and act on each item that requires your attention: 7 | 8 | - [ ] Fork this repository 9 | - [ ] Make sure that you have a ticket from Tito. Check your email -- Quincy has emailed your ticket to you. 10 | - [ ] 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. 11 | - [ ] Chat with others in the Discord group to brainstorm ideas and form teams. You will also do this after the hackathon has begun. IMPORTANT: Online 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. 12 | - [ ] Review this `README.md` file for further instructions and guidelines 13 | - [ ] Review the [APIs](/apis.md) 14 | - [ ] Ask questions to API sponsors directly on their Discord channel (i.e. `api-netlify`) 15 | - [ ] Review the [Judging Protocol](/judging-protocol.md) 16 | - [ ] Already have a team? List it in the [Teams file](/teams.md). 17 | - [ ] Don't have a team? Review the [Teams](/teams.md) that are seeking teammates. 18 | - [ ] Review the [Schedule](/schedule.md) 19 | - [ ] Review the resources and recommendations for [Getting Started](/getting-started.md) with the JAMstack. This will give you good resources for starting your project. 20 | - [ ] Ensure that you deploy your project with [Netlify](https://www.netlify.com). You should already have an account per the hackathon application instructions 21 | 22 | ## How is this hackathon different? 23 | 24 | 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. 25 | 26 | ### The Process -- what it means 27 | 28 | Building great software isn't just about the code you write. Your planned approach to building it is just as important. So here's what this means for you as a hacker at this hackathon: 29 | * Judges will pose a number of questions for you, and share them with you in the Discord group 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? 30 | * Your answers to these questions will be a small percentage of your overall judging score. 31 | 32 | 33 | ## Code of Conduct 34 | 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 35 | 36 | Note: This code applies to both in-person and online interaction. Violations will not be tolerated. 37 | 38 | ## Purpose 39 | 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! 40 | 41 | ## Team Size 42 | * Max team size: 6 43 | * Recommended team size: 3-5 44 | 45 | ## Join the Hackathon Discord Group 46 | See the link sent to your email 47 | 48 | ##### More info on Discord: 49 | * You can ask API sponsors questions directly in their respective channel, i.e. `#api-netlify` 50 | * Pay special attention to `announcements` channel. 51 | * Ask and answer questions about certain technologies in the `q-and-a-` channel 52 | * Have general communication in the `general` channel 53 | * Find a teammate or a team in the `team-formation-sf-hackathon` channel 54 | 55 | ## Review the APIs 56 | 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. 57 | 58 | ## Team Formation 59 | #### If you have a team 60 | 1. List your team in the [teams.md](/teams.md) file in this repo 61 | 2. Fork the repo and make a PR to list your team 62 | 3. Follow the style guide for listing your team 63 | 4. Tag `dunphyben` in your PR. 64 | 65 | #### If you don't have a team 66 | 1. Browse teams in the [teams.md](/teams.md) file of this repo 67 | 2. Find team members or a team to join using Discord 68 | -------------------------------------------------------------------------------- /apis.md: -------------------------------------------------------------------------------- 1 | # APIs 2 | Listed here are the APIs for your use. 3 | * Browse the APIs here and visit their documentation. 4 | * Communicate with the API sponsors via their dedicated Discord channel. 5 | * Deploy your apps with Netlify. 6 | 7 | # Fauna 8 | #### Quick Description 9 | A cloud database with generous free plan and distributed ACID transactions for global data integrity. Get started easily and scale to worldwide success. 10 | 11 | ### Purpose 12 | Stores transactional data like account balances, user profiles, social media content, shopping cart orders, etc. 13 | 14 | ##### API endpoint: 15 | 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: 16 | 17 | ```js 18 | const client = new faunadb.Client({ 19 | secret: process.env.FAUNADB_SERVER_SECRET 20 | }); 21 | ``` 22 | 23 | ### Challenges 24 | 25 | 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. 26 | 27 | ### Docs 28 | 29 | The [FaunaDB Query API docs](https://app.fauna.com/documentation/reference/queryapi) are a good reference. 30 | 31 | 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) 32 | 33 | ### Video tutorial 34 | 35 | I'll walk through these steps live during the Hackathon keynote. 36 | 37 | ### Presentation slides 38 | 39 | Coming soon. 40 | 41 | ### Prizes 42 | 43 | Coming soon. 44 | 45 | 46 | *** 47 | 48 | 49 | # Formspree 50 | 51 | https://formspree.io 52 | 53 | ### Purpose 54 | 55 | 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. 56 | 57 | ### API endpoint 58 | 59 | To use formspree with an existing HTML form you must: 60 | 61 | 1. change the `action` of your form to point to `https://formspree.io/` 62 | 2. make sure the `method` is `POST`, and 63 | 3. give a `name` attribute to all your `input` tags. 64 | 65 | For example: 66 | 67 | ```html 68 |
69 | 70 | 71 | 72 |
73 | ``` 74 | 75 | Try playing around with formspree in our sandbox at https://testformspree.com 76 | 77 | ### Challenges 78 | 79 | Get a "contact us" form set up on your website! 80 | 81 | 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.... 82 | 83 | ### Docs 84 | Using formspree is as easy as the `API endpoint` instructions. Try playing around with formspree at https://testformspree.com. 85 | 86 | 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. 87 | 88 | https://formspree.io/docs/ 89 | 90 | You can also find answers to common questions on our help site here: 91 | 92 | https://help.formspree.io/ 93 | 94 | Finally, we will be here in the discord `#formspree-api` chat room to help you! Just look for the formspree logo. 95 | 96 | 97 | 98 | ### API (Beta) 99 | 100 | We just launched an API beta. Check out the docs here: https://formspree.io/api. 101 | 102 | We're continuing to add to those docs so check back occasionally. Also check out the Discord `#formspree-api` room for updates. 103 | 104 | Finally we're gonna offer coupons to people who want to test out our Gold / Platinum features (including APIs). Let us know in discord if you want free access. 105 | 106 | ### Video tutorial 107 | Nothing yet, but maybe we'll have one of these posted soon... 108 | 109 | 110 | 111 | ### Prizes 112 | 113 | Off-site participants that use Formspree will be eligible to win an Amazon Gift Card worth $200. If Amazon gift cards aren't available in your country we will work with you to come up with an equivalent prize. 114 | 115 | *** 116 | 117 | # Clarifai 118 | #### Quick Description 119 | Clarifai's API offers image and video recognition capabilities. 120 | 121 | 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. 122 | 123 | ### Purpose 124 | Use the Clarifai API if you want to add image understanding to your JAMstack app. Two common use cases are analyzing what is in an image and visual (image-based) search. 125 | 126 | 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 127 | 128 | ##### API endpoint: 129 | https://api.clarifai.com/v2 130 | 131 | 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/ 132 | 133 | ### Challenges 134 | + Get JSON results from Clarifai's "General" model for an image of your choice. 135 | (Hint: https://clarifai.com/developer/guide/predict#predict) 136 | 137 | ++ Train your model to recognize a new object or concept (using at least 10 images as labeled examples) 138 | (Hint: https://clarifai.com/developer/guide/train#train) 139 | 140 | ### Docs 141 | Developer Guide (start here): https://clarifai.com/developer/guide/ 142 | Technical Reference and Client Libraries: https://clarifai.com/developer/reference/ 143 | JavaScript API endpoint reference: https://sdk.clarifai.com/js/latest/index.html 144 | 145 | ### Video tutorial 146 | 4 minute Intro to Clarifai including an API demo with the Python client: https://youtu.be/YOrrROME2zc 147 | 148 | ### Prizes 149 | 150 | 1st place team: $500 cash 151 | 152 | *** 153 | 154 | 155 | # Hasura 156 | 157 | Hasura 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. 158 | 159 | [![Deploy to Heroku](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/hasura/graphql-engine-heroku) 160 | 161 | You don't need to know how to write a GraphQL schema, resolvers or learn how to use 162 | a database to get started! Head to the deployed app, create a table, and run CRUD + realtime with GraphQL :) 163 | 164 | ![Hasura demo GIF](https://raw.githubusercontent.com/hasura/graphql-engine/master/assets/demo.gif) 165 | 166 | You can also use Hasura to trigger Lambda/Serverless functions such as [Netlify 167 | Functions](https://www.netlify.com/docs/functions/) when an event happens on the 168 | database, for example, send an email when a new user is added. 169 | 170 | ### Purpose 171 | 172 | You should use Hasura if your JAMstack app needs to CRUD data, needs a realtime API, 173 | or if you want to trigger webhooks on data changes. 174 | 175 | Here are some examples of how you can use Hasura: 176 | - CRUD operations with GraphQL ([sample app](https://github.com/hasura/graphql-engine/tree/master/community/examples/todo-auth0-jwt)) 177 | - 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)) 178 | - 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)) 179 | - Triggering browser-based notifications if some data changes ([sample app](https://github.com/hasura/graphql-engine/tree/master/community/examples/serverless-push)) 180 | 181 | ### Learn in 5 minutes (video tutorials) 182 | 183 | Here are a few short videos to help you get started: 184 | 185 | 1. Explore GraphQL queries, mutations and subscriptions with a realtime todo app [(video coming soon)]() 186 | 2. Send an email when a new user is created using Netlify functions [(video coming soon)]() 187 | 3. Integrate authentication/authorization with auth0 [(video coming soon)]() 188 | 189 | ### Support & help 190 | 191 | - 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! 192 | - 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: 193 | 194 | Tanmai 195 | 196 | ### Docs 197 | 198 | Hasura docs are available at [`docs.hasura.io`](https://docs.hasura.io). 199 | 200 | Here are some quick links to get you started: 201 | 202 | - [Deployment guide on Heroku](https://docs.hasura.io/1.0/graphql/manual/getting-started/heroku-simple.html) 203 | - [Making your first GraphQL query](https://docs.hasura.io/1.0/graphql/manual/getting-started/first-graphql-query.html) 204 | - [Creating tables and columns](https://docs.hasura.io/1.0/graphql/manual/schema/index.html) 205 | - [Querying data through GraphQL](https://docs.hasura.io/1.0/graphql/manual/queries/index.html) 206 | - [Modifying data using Mutations](https://docs.hasura.io/1.0/graphql/manual/mutations/index.html) 207 | - [Getting realtime data using Subscriptions](https://docs.hasura.io/1.0/graphql/manual/subscriptions/index.html) 208 | - [Create Gatsby sites using GraphQL and Postgres](https://github.com/hasura/graphql-engine/tree/master/community/boilerplates/gatsby-postgres-graphql) 209 | - [Example applications built using Hasura](https://github.com/hasura/graphql-engine/tree/master/community/examples) 210 | - [Trigger a Lambda function](https://docs.hasura.io/1.0/graphql/manual/getting-started/first-event-trigger.html) 211 | 212 | To query data from frontend applications, you can use the [Apollo 213 | Client](https://www.apollographql.com/docs/react/). Here are some popular clients: 214 | 215 | - [React](https://www.apollographql.com/docs/react/essentials/get-started.html) 216 | - [Angular](https://www.apollographql.com/docs/angular) 217 | - [Vue](https://www.apollographql.com/docs/react/integrations.html#vue) 218 | 219 | 220 | ### Prizes 221 | 222 | Coming soon. 223 | 224 | *** 225 | 226 | Pilon is an **e-commerce platform** designed and built from the ground up for the JAMstack world. 227 | 228 | 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. 229 | 230 | We're **opening** our beta platform to hackathon participants and *we'll be there hacking on Pilon while you're hacking on your projects*. 231 | 232 | ### Purpose 233 | 234 | E-commerce stuff. 235 | 236 | Use Pilon to add any of these elements to your project: 237 | * Customer Auth 238 | * Product Catalog / CMS 239 | * Cart + Checkout 240 | * Taking Orders Online 241 | 242 | ##### API endpoints: 243 | REST 244 | * https://api.pilon.io/v1 245 | 246 | GraphQL 247 | * https://api.pilon.io/v1/graphql 248 | 249 | ### Challenges 250 | Sell something. Use Pilon's new GraphQL API + Gatsby to build a super fast, super easy, super sweet commerce experience. 251 | 252 | To get inspired, [*checkout how fast an e-commerce site can be*](https://rachio.com) when its built with **Gatsby** and a GraphQL API. 253 | 254 | ### Docs 255 | 256 | Pilon's main documentation can be accessed at: 257 | * https://docs.pilon.io/ 258 | 259 | Pilon's API docs are here: 260 | * https://api.pilon.io/v1/docs 261 | 262 | An example project using our REST API can found on GitHub here: 263 | * https://github.com/pilon-io/example-fh 264 | 265 | ### Video tutorial 266 | 267 | ### Support & Help 268 | 269 | 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. 270 | 271 | We'll be there hacking with you the whole time. 272 | 273 | ### Prizes 274 | 275 | Top team using Pilon will receive $150 cash prize. 276 | 277 | *** 278 | 279 | # Overall Winners 280 | 281 | ### Prizes 282 | * Top 3 Teams 283 | * 3rd place: $200 cash prize 284 | * 2nd place: $300 cash prize 285 | * 1st place: $500 cash prize 286 | -------------------------------------------------------------------------------- /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](./apismd) 11 | 12 | # Judging Criteria 13 | 14 | Your project will be judged on: 15 | 16 | 1. Project intrigue/novelty 17 | 2. Product Design & Functionality 18 | 3. Presentation/Pitch 19 | 20 | ## Not competing for prizes? 21 | Build whatever you'd like, of course. 22 | 23 | We will update this document soon with more details about how we will judge your project. 24 | -------------------------------------------------------------------------------- /schedule.md: -------------------------------------------------------------------------------- 1 | # Schedule 2 | 3 | Note: This schedule is a guideline, and is for the San Francisco event. Actual times may vary. Watch for announcements in the Discord channel `announcements`. These times are all in PST. 4 | 5 | You can watch these events on the livestream at youtube.com/freecodecamp if you want. Feel free to work on your project throughout the weekend until Sunday night at 11 p.m. GMT. 6 | 7 | ## Saturday, November 3 8 | 9:00am - Doors open 9 | 9:00 - 10:00 - Check-in, coffee, mingle & form teams 10 | 10:00 - 11:20 - Welcome + Keynote (Main Stage) 11 | 11:20 - 12:30pm - Form teams, discuss projects and procedure 12 | 12:30 - 1:00 - Lunch 13 | 1:00 - 6:00 - Hacking & Procedural Interviews 14 | 6:00 - 6:30 - Light dinner 15 | 6:30 - 8:45 - Hacking 16 | 9:00pm - Doors close 17 | 18 | ## Sunday, November 4 19 | 9:00am - Doors open 20 | 9:00 - 10:00 - Check-in, coffee 21 | 10:00 - 11:00 - Welcome + Keynote (Main Stage) 22 | 10:45 - 12:30 - Hacking 23 | 12:30 - 1:00 - Lunch 24 | 1:00 - 6:00 - Hacking 25 | 3:00 - 5:00 - Teams present their projects to judges (actual time may change depending on number of hackers and teams) 26 | 5:00 - 5:30 - Judges decide top 6 teams, no order 27 | 6:00 - Food arrives 28 | 6:00 - 7:00 - Judges interview top 6 teams for video 29 | 7:30 - 8:00 - Top 3 teams present (Main Stage) 30 | 8:00 - 8:10 - API Awards Announced 31 | 8:10 - 8:15 - Top 3 teams Awards Announced 32 | 8:15 - 9:00 - Mingling 33 | 9:30pm - Doors close 34 | -------------------------------------------------------------------------------- /teams.md: -------------------------------------------------------------------------------- 1 | # Hackathon Teams 2 | 3 | ### Create a Pull Request 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 | # Emote Journal 51 | ### A web application to track your mood. 52 | * Teammates: * Teammates: 53 | - Nicole Provan (@provanni#1363) 54 | - Mariel Martinez (@Mares#3426) 55 | - Ngoc Vuong (@Dragonza#2281) 56 | - C Dharmateja (@dharmateja#2684) 57 | 58 | * Seeking Teammates: No 59 | * [Project URL](https://github.com/provanni/2018-JAMstack-project) 60 | 61 | *** 62 | 63 | # SunCodeFlower 64 | ### We created this team to participate in 2018 Online freeCodeCamp JAMstack Hackathon. Good luck to us! 65 | * **Teammates**: 66 | - Olha (@oshka) 67 | - Itsik (@Itsik) 68 | - Alberto (@Albertoescala) 69 | - John (@johnotu) 70 | 71 | 72 | * **Seeking Teammates**: no 73 | * [GitHub URL](https://github.com/oshka/SunFoodApp) 74 | * **Project Name**: SunFoodApp 75 | 76 | ### Project Q&A: 77 | 78 | 1. **What are you going to build?** 79 | We are going to build an app for helping seekers to find specific dish/food. The app will direct to the local restaurants that have the dish and mentions its price and offer the restaurant menu. Also show directions to the restaurant from the user current location. 80 | 2. **Which APIs do you plan to use?** 81 | Fauna (for call the db and receive data), Clarify (to detect food image), Formspree (for collecting delivery address), Pilon (because it's interesting to try) 82 | 3. **What is your plan to execute this idea?** 83 | * Stage 1: 84 | * create a gallery of food pictures 85 | * create a page to show food details 86 | * create a page to search food 87 | * create food database 88 | 89 | *** 90 | 91 | # CapeCoders 92 | ### This project is going to be a budgeting/expense app to help people manage their finances and track expenses. 93 | * Teammates: 94 | - Christopher Karras (@ckarras) 95 | - Dimo Ivanov (@Dimo) 96 | * Seeking Teammates: No 97 | * [Project URL](https://github.com/ckarras11/fcc-hackathon) 98 | * Project Name SpareChange 99 | ### Project Q&A: 100 | 1. What are you going to build? 101 | We are building an expense tracking app 102 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 103 | We plan on using netlify-identity and hasura 104 | 3. What is your plan to execute this idea? 105 | We are going to use gatsby, react, and material-ui to build out the ui. Then we will use netlify identity to manage users and then make calls to hasura. Our goal is to finish the ui today and spend tomorrow on the logic and connecting the db. 106 | 107 | *** 108 | 109 | # DiseaseDetector 110 | ### An AI app that detects and identifies diseases on skin and plants. 111 | * Teammates: 112 | - Alfred Conlan (@Alfred#6356) 113 | - Dennis Demir (@Demird14#4032) 114 | - Joseph Eton (@etonjoe#5279) 115 | - Juan Garcia (@john#0065) 116 | - imtan007 (@Tanmay#3030) 117 | * Seeking Teammates: No 118 | * [Project URL](https://github.com/AlfredConlan/fccHackathonTeamProject) 119 | * Project Name (Disease Detector) 120 | 121 | *** 122 | 123 | # FindUrFeeling. 124 | ### Using FindYourFeeling, Any human can find their feeling based on Clarifai API mainly focused on facial expression detection. 125 | 126 | * Teammates: 127 | - Monica Pattel (@MonikaPatellT) 128 | - Qasim Hafeez (@Qasim) 129 | - Juan Pablo Yeverino (@JPYeverino) 130 | - Nassim (@Nsdz) 131 | - Rossella Ferrandino (@RosellaFer) 132 | - bvipul (@bvipul) 133 | 134 | * Seeking Teammates: No 135 | * [GitHub URL](https://github.com/your-profile/your-project-name) 136 | * Find Ur Feeling 137 | 138 | *** 139 | 140 | # PawnShopify 141 | ### An online pawn shop 142 | * **Teammates**: 143 | - @Jarrod 144 | - @smakosh 145 | - @kBrew 146 | - @CyberPutty 147 | - @Mo 148 | * **Seeking Teammates**: No 149 | * [Project URL](https://github.com/appleJax/pawn-shopify) 150 | * [Live Site](https://pawn-shopify.netlify.com) 151 | * **Team Name**: Prestige Worldwide 152 | 153 | *** 154 | 155 | # Quizard - swing your knowledge wand 156 | ### An online quiz app where questions would be asked on topics selected by the user. This is a timer-based quiz with four options for every question with only one being correct. Now, after successfully completing the quiz, the user will be mailed with a digital badge and the score reflecting his/her performance! 157 | * Teammates: 158 | - Priyabrata Biswas (@pbiswas101) 159 | - Rajat Kanti Nandi (@rajatkn) 160 | - Daniel Pöhle (@danielp) 161 | * Seeking Teammates: Yes 162 | * [Project URL](https://github.com/pbiswas101/Quizard) 163 | * Project Name - Quizard 164 | 165 | *** 166 | 167 | # CMintS 168 | ### [CMintS](https://cmints.io) is a CMS and static site generator created with the internationalization in mind, but yet it's not deployable to the Netlify, the idea is to during current Hackathon create a Multilanguage websites, Themes and deploy them to the Netlify, meanwhile adapt actual [CMintS package](https://www.npmjs.com/package/cmints) to support Netlify deployment. Also document the deployment process in https://cmints.io. 169 | * Teammates: 170 | - Manvel (@saroyanm) 171 | - @Miss500 172 | - @OdearOgy 173 | - @satyendra 174 | - @nvs16 175 | * Seeking Teammates: Yes 176 | * [Project URL](https://github.com/Manvel/cmints) 177 | 178 | *** 179 | 180 | # MAYN! MAYN! MAYN! 181 | ### An auction where buyers chats 'MINE!', it also has buy and sell cuz reasons. [This video will make this things clearer.](https://www.youtube.com/watch?v=p-3e0EkvIEM) 182 | * Teammates: 183 | - Renz Christen Yeomer A. Pagulayan (@ThatOneNoob) 184 | * Seeking Teammates: No 185 | * [Project Website](https://romantic-euler-651676.netlify.com/) 186 | * [Project Repo](https://github.com/larongbingo/MAYN-MAYN-MAYN) 187 | ### Project Q&A: 188 | 1. What are you going to build? 189 | A buy and sell website with auction. 190 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 191 | Hasura, Pilon, Netlify, more coming I think 192 | 3. What is your plan to execute this idea? 193 | Use Pilon to store product details, Hasura for the user credentials and chat (for the MINE!) 194 | Then use netlify and netlify-lambda for hosting and auth. 195 | Problem is I do not know serverless, gatsby and webpack. 196 | So, this project will be incomplete, 100% guarenteed T_T 197 | 198 | The plan now is to build everything that needs to use the lambda thingy (Pilon & Hasura?) 199 | then build the frontend part. 200 | 201 | *** 202 | # FriendsOverJAM 203 | ### Simple set of JAMStack based games 204 | * Teammates: 205 | - Simon Xiong (@simonxcode) 206 | - Akhil Alluri (@techalien) 207 | - Ion Varsescu (@Ion Varsescu) 208 | - Kopal (@km.) 209 | - Sunday Joe (@pac_admin) 210 | * Seeking Teammates: No 211 | * [GitHub URL](https://github.com/techalien/FccFriendshipTest) 212 | * FriendsOverJAM 213 | ### Project Q&A: 214 | 1. What are you going to build? 215 | Two games to demonstate JAMStack concepts 216 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 217 | We are using FaunaDB, Netlify to AutoDeploy from GitHub 218 | 3. What is your plan to execute this idea? 219 | We have divided the tasks into functional Units [DB APIs, React layout and the games.]. Each person will work on the respective feature branch, which shall be merged into **master** at milestones. 220 | 221 | *** 222 | 223 | # JAKE 224 | ### Undecided, but tentatively a scavenger hunt web app 225 | * **Teammates**: 226 | - Jait Jacob (@jaitjacob) 227 | - Adam Wier (@AdamWier) 228 | - Kelby Baca (@kelby-baca) 229 | - Eunice Park (@eunicode) 230 | * **Seeking Teammates**: Yes, if you're a coding wizard and want to donate your magical skills, or if you're familiar with React basics 231 | * [Project URL](https://github.com/teamjake2018/jake) 232 | * Project Name: coming soon 233 | 234 | *** 235 | # Kids Kata 236 | ### Learning Platform for kids to learn and memorize name of objects, colors and animals with the use of images. It also favours autistic kids. 237 | * Teammates: 238 | - Getty Orawo (@Getty) 239 | - Pollet Obuya (@P.) 240 | - Peter Omondi (@pomosly) 241 | * Seeking Teammates: No 242 | * [Project URL](https://github.com/Podiihq/kids-kata.git) 243 | * Project Name: Kids Kata 244 | 245 | *** 246 | 247 | # Haptreyscorwix 248 | ### An app for finding music matching your video. It uses video recognition to match subjectively the description to a musical genre. 249 | * Teammates: 250 | - Julien Demarque (@HappyPanda) 251 | - Adrian Wix (@AdrianWix) 252 | - Trey Huffine(@trey) 253 | - Ahmed Ihsan Tawfeeq (@scorpion9979) 254 | * Seeking Teammates: No 255 | * [Project URL](https://github.com/JulienDemarque/JAMstack-hackathon-video-audio-matcher) 256 | * Project Name : Video Audio Matcher 257 | 258 | *** 259 | 260 | # Kungara 261 | ### The app helps the tailor or designers to avail different designs and fabrics to their clients. The clients can also send their measurements and images to the tailors. 262 | * Teammates: 263 | - Teammate Name (@MemoryJos) 264 | - Teammate Name (@JackieW) 265 | - Teammate Name (@okothkongo) 266 | * Seeking Teammates: No 267 | * [Project URL](https://github.com/Podiihq/kungara) 268 | *** 269 | 270 | # Mathosaurus X 271 | ### A math RPG - level up and win badges while learning real math skills 272 | * Teammates: 273 | - Ruan Huysen (@Rhman101) 274 | - Regina McGuire (@reginam) 275 | - Devesh Parashar (@dopinder) 276 | - Rein Yee Deocareza (@chi?) 277 | - Emma Margeson (@mawarijo) 278 | * Seeking Teammates: No 279 | * [Project URL](https://github.com/deveshp/jamstack-hackathon) 280 | 281 | # BadCodersBad 282 | ### Get a list of ingredients in your meal, with their nutrition, calorie value. 283 | * Teammates: 284 | - Vipul Dessai (@badgamerbad) 285 | - Kartik Malik (@arrow2406) 286 | * Seeking Teammates: No 287 | * [Project URL](https://github.com/kartik2406/ingredo-fit) 288 | * Project Name: IngredoFit 289 | ### Project Q&A: 290 | 1. What are you going to build? 291 | We are going to build a web app that will allow users to get an idea of what makes up their meal, how much calories they are eating, nutrional value. The meals will be analyzed by Clarifai api, which will give us a list of ingredients. 292 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 293 | Clarifai for identifying ingredients. Firebase storage to store images uploaded by user. 294 | 3. What is your plan to execute this idea? 295 | First we will get upload logic figured out, chose firebase storeage. This uploaded image url is then sent to Clarifai for processing. Next we maintained a list of common food ingredients in our source file (We were supposed to use fauna for this but our data kept on vanishing from the db). With this our MVP would be ready, but it would be ugly. The next step is to beautify it and give it our style. 296 | 297 | 298 | *** 299 | 300 | # Team Barter Hub 301 | ### An E-commerce site for bartering goods 302 | * Teammates: 303 | - @Davido#4076 304 | - @gopikrishna#8032 305 | - @Lonewolf#5690 306 | - @Marifer#8861 307 | - @Ma7eer#3701 308 | * Seeking Teammates: No 309 | * [Project URL](https://github.com/hamiltonbarnes/barter_hub-freecodecamp-jamstackhackathon2018) 310 | * Project Name: Barter Hub 311 | 312 | # Count'em All 313 | ### A simple app to count the number of people attending a gathering 314 | * Teammates: 315 | - Shrey Dabhi (@sdabhi23) 316 | - Sohel Shaikh (@thesohelshaikh) 317 | * Seeking Teammates: No 318 | * [Project URL](https://github.com/sdabhi23/count-em-all) 319 | * Count'em All 320 | 321 | # Thascii 322 | ### A facial recognition authentication SPA 323 | * Teammates: 324 | - Samuel Afolaranmi (@asiidev) 325 | - Ali Nisar Ahmed (@downrightcriminal) 326 | - Pavlos (@pavlos) 327 | - Sarthak (@Sarthak) 328 | * Seeking Teammates: No 329 | * [Project URL](https://github.com/ascii-dev/thascii) 330 | * Project Name Thascii 331 | 332 | *** 333 | 334 | # ALA 335 | ### Trying to decide for the moment 336 | * Teammates: 337 | - Alexandru Vranceanu (@valexander) 338 | - Alina Ivan (@apryllya) 339 | - Leontin Stoea (@discordUserProfileName) 340 | * Seeking Teammates: No 341 | * [Project URL](https://github.com/stl30/ALA) 342 | * Project Name: coming soon 343 | 344 | *** 345 | 346 | # HoustonHacks 347 | ### Reminder service that sends SMS or email renewal reminders to customers based on renewal date. 348 | * Teammates: 349 | - Hector J. Saldana (@electricgnome) 350 | - Biko Allen (@kobi1021) 351 | - Earle Poole (@Emjp4) 352 | - Yetunde Sola-Adebayo (@yetunde79) 353 | - Josh Medeski (@Big_Josh_7) 354 | * Seeking Teammates: No 355 | * [Project URL](https://github.com/electricgnome/smsRenewal) 356 | * Project Name: SMSRenewal 357 | 358 | *** 359 | 360 | # JAMsnack 361 | ### A web app to help making healthy eating decisions. Just take a picture of your food and see if it is healty or not. 362 | * Teammates: 363 | - (@Korhan) 364 | - (@Lexie) 365 | - (@artoo) 366 | - (@Jsifontez) 367 | - (@Han) 368 | * Seeking Teammates: No 369 | * [Project URL](https://github.com/kakcura/JAMsnack) 370 | * Project Name: JAMsnack 371 | ### Project Q&A: 372 | 1. What are you going to build? 373 | A web app to help making healthy eating decisions. Just take a picture of your food and see if it is healty or not. 374 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 375 | Clarifai 376 | 3. What is your plan to execute this idea? 377 | Happy Healty Snack Jamming and coding hard!!! 378 | 379 | *** 380 | 381 | # Farmer Helper 382 | ### Machine Learning powered application that can predict the disease plant is suffering by just using the image and can also provide some suggestions for how to cure it. It scraps the web and immediately provide some good videos to look at and proceed further. Discussion platform that enables farmers to discuss how he has to proceed further to cure that disease as well as how to prevent it in future. This platform enables farmer to directly check the price of different product at nearby Agricultural produce market committee as well as check regular agriculture news like minimum support price declared by government etc. Notifies the user whenever 'kishan TV' youtube channel goes live. 383 | * Teammates: 384 | - Hardik Modi (@hardik) 385 | * Seeking Teammates: No 386 | * [Project URL](https://github.com/hardiked/helper) 387 | * Project Name: Farmerhelper 388 | 389 | *** 390 | 391 | # MagiKart 392 | ### Creating an eCommerce site using the Gatsby modern framework for blazing fast websites, hosted in GitHub, deployed with Netlify an all-in-one workflow that combines global deployment, continuous integration, and automatic HTTPS. This e-portal is including Shopping cart, admin control for viewing the order information product information, New entry of product, edit the specified product, delete the product, User login password, new admin registration, data fetching from database, feedback form/rating, searching items using filters. 393 | * **Teammates of TeamHacky**: 394 | - Ronique Ricketts (@NiQ) 395 | - Harshil Agrawal (@harshil1712) 396 | - Cremona Matei (@cremzoo) 397 | - Abhishek Yadav (@phoenixabhishek) 398 | - Lakshmi Chandana (@chandana) 399 | - Linda Kovacs (@lindakovacs) 400 | * **Seeking Teammates**: No 401 | * [GitHub URL](https://github.com/harshil1712/gatsby-store-hackathon) 402 | * [Live Site](https://magikart-hacky.netlify.com) 403 | 404 | ### Project Q&A: 405 | 1. What are you going to build? 406 | An E-commerce site that will be able to provide product suggestions based on the uploaded image(using the clarifai recognition API) 407 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 408 | Pilon 409 | Clarifai 410 | Netlify 411 | 3. What is your plan to execute this idea? 412 | To have a smart shopping experience where a person can take an image of another person and get the products that appear in the image for shopping 413 | *** 414 | 415 | # MarketGraph 416 | ### Helps you quickly obtain & collect user data on project ideas & campaigns. 417 | * Teammates: 418 | - Andy Cary (@andycary) 419 | - Hays Stanford(@hays) 420 | * Seeking Teammates: Yes 421 | * [Project URL](https://github.com/your-profile/your-project-name) 422 | * Project Name (ok to say tbd and update later) 423 | 424 | *** 425 | 426 | # Extra-Life Donation Leaderboard 427 | ### In the spirit of Extra-Life Game Day raising money for Children's Miracle Network, we are creating a leaderboard to show the donations received from the members of our team and allows you to see live updates using React. 428 | * Teammates: 429 | - Christopher Tse (@Gavlois) 430 | - Joe Matthews 431 | - Hong L 432 | - Natalie Fleming 433 | - Daniel Ashcraft 434 | * Seaking Teammates: No 435 | * [Project URL](https://github.com/chris-tse/extralifeleaderboard) 436 | * Project Name: Extra-Life Donations Leaderboard 437 | 438 | *** 439 | 440 | # 1000 Words 441 | ### A site where people can submit an image and get results based on the general feel of the image. 442 | * Teammates: 443 | - Daniel Ramsayer (@Neko#9307) 444 | - Daniel Evans (@Gate#5312) 445 | - Peter Durham (@funoptimizer#2690) 446 | - Aaron Baker (@Muluul#6162) 447 | - Tony Neuhold (@aneuhold#3384) 448 | * Seeking Teammates: No 449 | * [Project URL](https://1000-words.netlify.com/) 450 | ### Project Q&A: 451 | 1. What are you going to build? 452 | A site that will take in an image and return various results based on the words that the image provides. We will try to get it to return a poem, or some kind of book. We might try to add different kinds of results as well. 453 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 454 | Clarifai, FaunaDB (probably) 455 | 3. What is your plan to execute this idea? 456 | To test the basic idea of getting an image to return results in the form of a poem, or a list of thematically relavant material such as a small list of songs. After that we will try to build out different features. 🙂 457 | 458 | *** 459 | 460 | # HAKO 461 | ### An app where we can choose and put the film we like on watchlist 462 | * Teammates 463 | - Hiraz (@hiraz) 464 | - Ali (@Ali) 465 | - Ann (@kun) 466 | * Seeking teammate: Yes 467 | * [Project URL] (https://github.com/AnnLe4869/HackathonProject) 468 | 469 | *** 470 | 471 | # TIL - Today I Learned 472 | ### An application that accepts user submitted tips and tricks for new programmers 473 | * Teammates: 474 | - Kevin Tan (@Node) 475 | - Joseph Thompson (@Jthomps838) 476 | - Nick Piaskoski (@pieguy) 477 | - Chris Watkin (@DeafDucky) 478 | - Ahmed Belhadj (@Ahmed) 479 | * Seeking Teammates: No 480 | * [Project URL](https://github.com/ktan114/JAMstack-Hackathon) 481 | * [GitHub URL](https://jamstack-hackathon-project.netlify.com/) 482 | 483 | 484 | *** 485 | 486 | # Project Name 487 | ### Less than 240 Characters describing what we're building. Include external links here if desired 488 | * Teammates: 489 | - Rebecca Yip 490 | - Julie Jonak 491 | - Nicky Chen 492 | - Roland Canuto 493 | - Kyran McCann 494 | - Tommy Collison 495 | 496 | * Seeking Teammates: No 497 | * [https://github.com/recipeshopper](https://github.com/recipeshopper) 498 | * Project Name: Recipe Shopper 499 | 500 | ### Project Q&A: 501 | 1. What are you going to build? 502 | A recipe shopper app that pulls in ingredient lists for recipes you'd like to make and returns a shopping list. 503 | 504 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 505 | We're planning on implementing a Fauna API. 506 | 507 | 3. What is your plan to execute this idea? 508 | Our team is split between front- and back-end development, creating and styling the app. 509 | 510 | 511 | *** 512 | 513 | # MeetUb 514 | ### Description: 515 | 516 | - This app will support users for meetup, find places and make new friends 517 | * Teammates: 518 | - Navjeet Kaur (@navjeet) 519 | - Khang Nguyen (@lee) 520 | - Hadjer (@hadjer) 521 | * Seeking Teammates: No 522 | * Livesite: https://meetub.herokuapp.com/ 523 | * Project Name: MeetUb 524 | ### Project Q&A: 525 | 1. What are you going to build? 526 | - An app to support users for meetup, find places and make new friends 527 | 2. Which APIs do you plan to use? (You can use any APIs, not just Hackathon sponsor APIs.) 528 | - Google Map APIs, Github API 529 | 3. What is your plan to execute this idea? 530 | - An app to support users for meetup, find places and make new friends 531 | - 532 | *** 533 | 534 | # GitBit 535 | ### A a game that encourages new developers to create a habit of coding regularly and helping them become better developpers. 536 | * **Teammates**: 537 | - Minh Trinh (@minhat) 538 | - Tatum Alenkov (@Taterz) 539 | - David Tran (@PoutineNinja) 540 | - Catalin Popescu (@DancingCat) 541 | - Maria Tolymbek (@Daffodil509) 542 | * **Seeking Teammates**: No 543 | * [GitHub URL](https://github.com/tatumalenko/fcc-jamstack-hackathon-2018) 544 | * Project Name: GitBit 545 | 546 | *** 547 | --------------------------------------------------------------------------------