Kassian Wren

Gatsby and TypeScript make a really great pair, with both bringing great features to your tech stack. One of Gatsby’s best features is its GraphQL data layer, and because the GraphQL data is typed, TypeScript’s type checking can make applications much less prone to runtime issues and works well with it

Gatsby 5 is here and Slices are a big part of what makes it great. Today, we’ll walk through creating an internationalized site with Slices. 

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. 

Gatsby 5 is coming soon– the Alpha is live, and we’ve touched on a bunch of new features in Gatsby 5 in Tuesday’s Update Week post. But now I’d like to focus on one feature in particular: partial hydration. We’ll go over what it is, how it is implemented in Gatsby 5, the benefits of partial hydration, and look into how to use it.

Join us on the Gatsby Blog Sep 26-30 for Update Week!