Netlify announces the next evolution of Gatsby Cloud. Learn more
When website teams are transitioning toward Gatsby, one common challenge we hear is that working in the modern web ecosystem means you have to know a lot of different technologies. To help, we’ve curated a list of our favorite resources.
With Gatsby and Contentstack, the SAP Community team has been able to increase content velocity, community satisfaction, SEO and increased feature velocity.
When the Elevar team set out to migrate StriVectin from Magento to Shopify, they started with Storybook, a tool for developing UI components in isolation for React. Using Storybook with Gatsby enabled the team to delay decisions about hosting and content management, focusing on one decision at a time.
A design system is more than a component library. IBM, Capital One, and Thumbtack have all used Gatsby to document not just their component libraries but the design system in which they're used. Teams valued the great content composability experience, ability to pull in data from third party systems, rich experience for internal users, and ability to solicit feedback from non-developers they got with Gatsby.
As Gatsby continues to be used for building larger and more complex sites, we are constantly asking our users and the community how we could improve. Among professional Gatsby developers, we tend to hear less about specific bugs and feature requests and more about qualities they want and need in their site -- faster load times, shorter publish times, and so on.
Kathleen McMahon, a software engineer at O’Reilly Media, tells the Gatsby Days LA 2020 audience how her team facilitated contributions and improved accessibility for her company’s component library documentation using Gatsby and MDX.
