This should be the recommended starter for React developers, over create-react-app!
Announcing Gatsby 2.0.0
11–20 of 36 posts
Re: Announcing Gatsby 2.0.0
#12I hadn't heard of this before but it looks really good. Good documentation, lots of plugins and community support, and appears to be in use by some big companies. Anyone here had good or bad experiences with it?
I’ve been using it since the 1.0 timeframe. The SEO went through the roof on my low traffic few post personal blog when I switched to Gatsby.
Re: Announcing Gatsby 2.0.0
#13I tried using Gatsby for a project of mine. The moment I tried to do anything not supported OOTB, it seemed I was fighting the tooling (and webpack) at every corner. It was incredibly difficult just to get a simple tree navigation.
One thing I thankful for though is that it gave me a new-found love for the simple and non-flashy libs/tooling.
In the end, I wound up writing my own static site generator.
https://github.com/pauldotknopf/statik
You may say to yourself "So you just wrote your own Gatsby!?"
No, I didn't. I wrote a thin lib that you can register endpoints and extract them to disk. It does absolutely nothing else. The idea is that I will wrote my own markdown rendering, navigation, html/css, etc for each project. "But what about the time it takes to implement all the features you need!" The time it takes to implement these minor things take far less time in the long run, and I will never have to be in an endless fight with the tooling to get simple tree navigation. Every feature I implement is exactly what I need, no more, no less.
Sure, it isn't as cool as React, webpack, etc. But I'm a lot happier.
Re: Announcing Gatsby 2.0.0
#14I hadn't heard of this before but it looks really good. Good documentation, lots of plugins and community support, and appears to be in use by some big companies. Anyone here had good or bad experiences with it?
See my top-level comment. I've had bad experiences with it. It is a bohemeth, especially considering we are just-ish turning markdown into html.
There is way too much ceremony.
Re: Announcing Gatsby 2.0.0
#15I built https://www.goodlyapp.com using Gatsby the performance has been amazing.
The best things is using data at build time rather than run time. Which make everything so fast for the end user.
Re: Announcing Gatsby 2.0.0
#16Earlier quoted context omitted.
I am starting to do my blog with it and so far it's really good. One thing I love is how it is built to be a Progressive Web App. If you don't know what that is: after downloading your page, your browser will start to download the other pages of your website automatically so they will be able to render instantly. It's also amazing for documentation. You go on one page and the other pages will be preloaded so that mea…
that's pretty cool I'm deep down the Vue.JS rabbit hole and can really appreciate this stuff Out the box reactJS with the best practices already? maybe next project!
Yes I am a React dev myself and so far it has been really cool :)
Re: Announcing Gatsby 2.0.0
#17I hadn't heard of this before but it looks really good. Good documentation, lots of plugins and community support, and appears to be in use by some big companies. Anyone here had good or bad experiences with it?
I am starting to do my blog with it and so far it's really good. One thing I love is how it is built to be a Progressive Web App. If you don't know what that is: after downloading your page, your browser will start to download the other pages of your website automatically so they will be able to render instantly. It's also amazing for documentation. You go on one page and the other pages will be preloaded so that mea…
Progressive Web Apps aren't universally a good idea. I'm sharing a 6Mb/s down link with 5 other people. The absolute last thing I want is every website to pre-cache 40 pages for every page I browse.
Re: Announcing Gatsby 2.0.0
#18Earlier quoted context omitted.
I am starting to do my blog with it and so far it's really good. One thing I love is how it is built to be a Progressive Web App. If you don't know what that is: after downloading your page, your browser will start to download the other pages of your website automatically so they will be able to render instantly. It's also amazing for documentation. You go on one page and the other pages will be preloaded so that mea…
Progressive Web Apps aren't universally a good idea. I'm sharing a 6Mb/s down link with 5 other people. The absolute last thing I want is every website to pre-cache 40 pages for every page I browse.
This is a good point. But I think PWA's are still better than monstrous everything chunks. It would be good to make pwa's configurable to user preferences
Re: Announcing Gatsby 2.0.0
#19Earlier quoted context omitted.
I am starting to do my blog with it and so far it's really good. One thing I love is how it is built to be a Progressive Web App. If you don't know what that is: after downloading your page, your browser will start to download the other pages of your website automatically so they will be able to render instantly. It's also amazing for documentation. You go on one page and the other pages will be preloaded so that mea…
Progressive Web Apps aren't universally a good idea. I'm sharing a 6Mb/s down link with 5 other people. The absolute last thing I want is every website to pre-cache 40 pages for every page I browse.
Absolutely!
Gatsby tries to balance making your site work at some level offline w/ not precaching too much.
By default we cache the front page & then do "run-time" caching as the user visits different pages so ensuring they can at least return to the pages they've visited when offline.
Re: Announcing Gatsby 2.0.0
#20Writing sites with Gatsby is amazing, but is there any way to opt out of JS/PWA completely? It'd be nice to have a setting where Gatsby just called ReactDomServer.renderToStaticMarkup.