This is a test description.

With the release of Gatsby 5 just over a month ago, hearing praise like this from our users is music to our ears! At Gatsby, we’re extremely proud of what we’ve launched and have been loving seeing the tweets pour in over your excitement  of updating your site to the fastest Gatsby yet. After our blog posts, webinars, and full releases, I figured this would be a great time to recap what you, the community, have thought about the release so far!

Building upon the success of previous Gatsby features, Gatsby 5 boasts impressive, bleeding-edge technology to supercharge your sites. Over the past year (like every other), we have been obsessed with build and site performance. We recently reviewed our most impactful major changes over the past seven quarters in our Gatsby’s Greatest Hits post, and we’re not slowing down as we enter the final stretch of 2022. In this post, we’ll provide a high level overview of all the impressive features we’ve cooked up for Gatsby 5. If you’d like a deeper dive into the details, check out our Gatsby 5 release notes.

Serving fully-rendered, static HTML files has made a few trips in and out of the web development sphere over the past few decades. As content-rich sites continue to get larger and larger, building out an HTML file for every single page can prove to be a difficult and time-consuming task. Since 2015, Gatsby has dedicated itself to solving this problem.

I joined Gatsby in January of 2022. As of the publish time of this blog post, that’s still pretty recent! I had used Gatsby v2 in my previous role and knew it as a neat Javascript framework. We homerolled a deployment process and hosted it in AWS. From my perspective, Gatsby was a simple SSG framework that handled compilation of static assets, and I would handle the publishing of the assets. Prior to working here, I liked using Gatsby as a framework. I decided to research more about Gatsby and found that it has an entire suite of Cloud and Hosting offerings. (Which, seeing how cool it was, led me to apply!) It’s so much more than a framework and the team has been doing some incredible work.

From knocking out high-velocity sprints to successfully delivering key features, everyone on the Endpoint Health team here at Duo really feels like they’ve hit their stride. Handling customer issues quickly and efficiently, and having in-depth, successful technical conversations have become normal, expected occurrences within the team, which provides us with a great sense of accomplishment. Looking at these things together, we asked ourselves why. What have we been doing well that produced successive sprints and left us feeling accomplished and proud of our team’s work?