In this post Paul explains how he upgraded paulie.dev to Gatsby 5 and is now experiencing ~47% faster build times!

Let's take a look at all of the exciting features that are packaged in Gatsby 5, notably the Slice API and Partial Hydration!

I know many of you have been waiting for this—it’s time to introduce Valhalla Content Hub. We’ll talk about why Valhalla Content Hub (for the rest of this post, Valhalla) exists, what problems it solves, what it is, how it works, and finally, how you can sign up to start using it.

There’s been a lot of content around Gatsby 5, and we can’t help but be excited. Today I want to deep dive into a beta feature that is new in Gatsby 5, Partial Hydration.  Currently, Gatsby pages are fully hydrated – this means that every component you ship needs to have its JavaScript loaded for the page to run (and be interactive). This can slow down time to first interaction on your Gatsby site. 

When a legacy CMS clogged up a next-generation healthcare platform’s conversion funnel, Gatsby and Contentful were there to help.

We recently patched a high risk security vulnerability in our Gatsby Cloud Image CDN service. Since all affected customers have been informed about the vulnerability, and have been given time to patch their sites, we are now communicating details of the vulnerability and our fix publicly.

Gatsby can build and ship individual pieces (or Slices) of your site and deploy only those that changed. Read how!