3 ms·

I've had a lot of good experiences with Jekyll, and I'm fairly sure that the problem you've described would have worked nicely with it. Extending it is also rea

I've had a lot of good experiences with Jekyll, and I'm fairly sure that the problem you've described would have worked nicely with it. Extending it is also really straightforward, you just put a few lines of Ruby in a file in the right place. I've moved my site from Jekyll to Gatsby, and while there are some nice things, it's not been a clear win. My site is very significantly slower for first load, but slightly faster for all subsequent loads. The build is far less stable with Gatsby, there are ~5 dependency updates per day, things like Sass don't "just work" anymore, but on the other hand, there are a few more packages that do useful things that I didn't get in the Jekyll community.

misterxi 7y ago
> My site is very significantly slower for first load, but slightly faster for all subsequent loads. This can be easily accomplished with Jekyll as well using Service Workers. What Gatsby has done is to take all the good practices and optimisations that can be done to a static site(like image optimisation, asset minification, prefetching) and bundled them all together. A lot of these can be done using any static site generator. For example, Gatsby prefetches links on hover/entering the viewport. This[1] ~1kb JS is sufficient for that. [1] https://instant.page/ https://instant.page/.