-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
100DaysOfGatsby - Challenge 2 - Build and Deploy (#20480)
- Loading branch information
1 parent
197f3d1
commit 0360155
Showing
1 changed file
with
38 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--- | ||
title: Challenge - Host Your Gatsby Site for Free | ||
date: 2020-1-8 | ||
author: "Hashim Warren" | ||
tags: ["learning-to-code", "contest", "100-Days-of-Gatsby"] | ||
--- | ||
|
||
_Gatsby was named the [#1 new technology to learn in 2020](https://www.cnbc.com/2019/12/02/10-hottest-tech-skills-that-could-pay-off-most-in-2020-says-new-report.html)!_ | ||
|
||
_To help you learn about Gatsby and our ecosystem, we invite you to take the #100DaysOfGatsby challenge! If you are new to Gatsby, you can follow along with our beginner-friendly weekly prompts. Or if you are familiar with Gatsby and want to go deeper, we invite you to [build your first Gatsby Theme](/docs/themes/building-themes/)._ | ||
|
||
_Learn more about [#100DaysOfGatsby here](/blog/100days)!_ | ||
|
||
## Challenge 2: Build and Deploy Your Gatsby Site (Using Free Tools) | ||
|
||
This week we invite you to deploy your Gatsby project to the web! | ||
|
||
If you’re experienced with launching an all-in-one CMS-powered or database-backed website, then the process of putting a Gatsby site live on the web may feel strange to you. You will be using continuous deployment tools to prepare and publish your site. It’s okay if your site is unfinished, as getting a website deployed will allow you to test on mobile devices and share with your colleagues to get feedback on design and development. | ||
|
||
To complete this challenge, we would like you to: | ||
|
||
1. host your project in a cloud git repository (publicly or privately), | ||
2. then use a “build service” to create a production version of your site | ||
3. and automatically publish your site’s assets directly to a Content Delivery Network (CDN). | ||
|
||
Amazingly, for small projects you can use all of these services for free. There are many Gatsby sites in the wild that pay \$0 for hosting! | ||
|
||
Bonus: Try deploying your site to the free tier of multiple services to see first hand which one you’d like to adopt. You may notice differences in features, developer experience, and build speeds and limits. | ||
|
||
### Challenge Resources | ||
|
||
For your git repo, you can use GitHub, Gitlab, Bitbucket, or many similar services. | ||
|
||
And for your build tool and CDN we see many people have success with [AWS Amplify](/docs/deploying-to-aws-amplify/) and [Netlify](/docs/deploying-to-netlify/). Our documentation has step-by-step tutorials for those services, [and others](/docs/deploying-and-hosting/). | ||
|
||
### What to Do If You Need Help | ||
|
||
If you get stuck during the challenge, you can ask for help from the [Gatsby community](/contributing/community/) and the [ASKGatsbyJS](https://twitter.com/AskGatsbyJS) twitter account.. You can find fellow Gatsby Developers on [Discord](https://discordapp.com/invite/gatsby), [Reddit](https://www.reddit.com/r/gatsbyjs/), [Spectrum](https://spectrum.chat/gatsby-js), and [Dev](https://dev.to/t/gatsby). |