forked from freeCodeCamp/2018-jamstack-hackathon
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update most files to reflect 2018 fcc jamstack hackathon. still a wor…
…k in progress. see pr comments
- Loading branch information
Showing
10 changed files
with
265 additions
and
328 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# FAQ | ||
Frequently Asked Questions | ||
|
||
## Where's my ticket to the hackathon? | ||
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 I'm sorry, but you cannot participate. | ||
|
||
## What is the JAMstack? | ||
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). | ||
|
||
## Can the online participants and in-person participants be on the same team? | ||
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 remote collaborators, you will be disqualified. | ||
|
||
## Can the online/in-person hackers still chat? | ||
Of course. We're all in the same Discord chat group. And since this hackathon is largely about education, the in-person/remote groups should both help each other out by answering questions. | ||
|
||
## Where is the Discord Channel? | ||
Check your email for the Hackathon Discord Group invite. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,10 @@ | ||
# Hackathon Checklist | ||
|
||
- [ ] Make sure that you have a Universe ticket (from reactathon.com/hackathon) | ||
- [ ] Sign up for the [Reactathon Slack Group](https://join.slack.com/t/hack-reactathon2018/shared_invite/enQtMzMyMTQyODIyODAzLTJkNzFkMjY5ZjJlMzgxNmUyM2U4YmU4NDVkZTU3MzVhYjFmZTVjMDgwY2Y1OTZiODk3YmVlNTllMTFjMGFiOTE) | ||
- [ ] Make sure that you have a ticket from Tito. Check your email -- Quincy will have sent you an invite link. | ||
- [ ] Join the freeCodeCamp JAMstack Hackathon Discord Group (invite link sent to your email for ticket holders) | ||
- [ ] If applicable, add your team to the list at `teams.md` in this repo | ||
- [ ] Review the `README.md` file for further instructions and guidelines | ||
- [ ] Review the APIs on `apis.md` in this repo | ||
- [ ] Ask questions to API sponsors directly on their slack channel (i.e. `_api_eventbrite`) | ||
- [ ] Ask questions to API sponsors directly on their Discord channel (i.e. `api-netlify`) | ||
- [ ] Bring a refillable water bottle | ||
- [ ] **IMPORTANT: BRING A POWER STRIP** to use and share with others! We recommend putting tape on it to write your name |
Oops, something went wrong.