Skip to content

Commit

Permalink
removed non existing user at twitter @fernandopoumian - can not find …
Browse files Browse the repository at this point in the history
…a new one :(
  • Loading branch information
Muescha committed Nov 28, 2019
1 parent d10849b commit b0de361
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 2 deletions.
2 changes: 1 addition & 1 deletion docs/blog/2017-12-07-taking-gatsby-for-a-spin/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ export const query = graphql`

After reading some articles on the Gatsby site, I decided to set up my Gatsby hosting on a free plan from [Netlify](https://www.netlify.com/) (which is ridiculously generous by the way, what's the catch?) and that has been a fun experience. Netlify already supports Gatsby out of the box, which means you can configure automatic deploys with `git` in a few clicks. Every time I push to master, the site gets rebuild and uploaded by Netlify. _Magic_. There's also the possibility to configure staging servers based on your branches, so you can always test out your changes before merging to master and deploying.

But wait, there's more. If you use [Contentful](https://www.contentful.com/) as Content Management System and Netlify as your host, you can easily create a Webhook to trigger a rebuild on every content update! I haven't tried this myself yet, but [this posts](https://www.halfelectronic.com/post/setting-up-gatsby-js-contentful-and-netlify/) by [Fernando Poumián](https://twitter.com/fernandopoumian) is a great resource to get you going.
But wait, there's more. If you use [Contentful](https://www.contentful.com/) as Content Management System and Netlify as your host, you can easily create a Webhook to trigger a rebuild on every content update! I haven't tried this myself yet, but [this posts](https://www.halfelectronic.com/post/setting-up-gatsby-js-contentful-and-netlify/) by Fernando Poumián is a great resource to get you going.

Incremental builds aren't yet possible, so every update means a complete rebuild. I'm sure that's no cause for concern on smaller sites, but with larger sites that are updated often it could be a problem. Luckily, incremental builds will be part of Gatsby ['sooner than later'](https://twitter.com/gatsbyjs/status/937053640652611584), which will take care of that problem.

Expand Down
1 change: 0 additions & 1 deletion docs/blog/author.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,6 @@
- id: Fernando Poumian
bio: Full-Stack Web Developer - https://www.halfelectronic.com
avatar: avatars/fernando-poumian.jpeg
twitter: "@fernandopoumian"
- id: Josh Weaver
bio: Developer at By the Book, Inc. Enjoys technology, writing and playing music. Can't turn down a decent board game.
avatar: avatars/josh-weaver.jpg
Expand Down

0 comments on commit b0de361

Please sign in to comment.