- #Gatsby image carousel how to#
- #Gatsby image carousel install#
- #Gatsby image carousel update#
- #Gatsby image carousel upgrade#
If you want an even faster way to get started with Strapi and Gatsby, you can check out our starters: We love working with Gatsby and are happy to make it easier to use for you. # All its contents will be queried as JSON # contentSections is a Strapi dynamic zone Instead, you can rewrite them to only query the dynamic zone field as a scalar: 1 If you have tried using dynamic zones with Gatsby before, you may have written GraphQL queries that involved complex fragments. So you will need to make a small change in your gatsby-config.js file: 1ĪpiURL: ` // Instead of contentTypes: To avoid any confusion, we renamed the contentTypes option to collectionTypes, since it doesn't handle single types. Strapi offers two content types: collection types and single types.
#Gatsby image carousel install#
Npm install should now see the 1.0.0 version in your package.json. Inside your Gatsby frontend, open a terminal and run either of these commands: Using Yarn 1
#Gatsby image carousel update#
Now that we're done with Gatsby and Strapi versions, it's time to update the actual source plugin.
#Gatsby image carousel how to#
If your Strapi version is older, follow our docs on how to update Strapi. You want to have at least version 3.6, where we introduced internationalization. Then, make sure that your Strapi application is up to date as well. If you're coming from the v2 version, you can follow Gatsby's official migration guide. We recommend that you start by upgrading your frontend to Gatsby v3. Update your app to the new versionĪs this is a major release, there are a few breaking changes you need to make to enjoy the new version. It now features more examples for advanced configurations, like custom endpoints or authenticated requests. The source plugin's documentation was rewritten. This means you can use the gatsby-plugin-image in even more places, and build more performant image-heavy pages. Gatsby will now parse image fields, even if they come from an array of media fields, like a carousel.
#Gatsby image carousel upgrade#
You can safely upgrade your Gatsby version and enjoy the speed boost. The internal code of the plugin has been updated to work with Gatsby's latest major version. No need to write complex GraphQL fragments anymore :) We have now changed their behavior to rely on the JSON type. You can finally build websites that are translated for all your audiences!ĭynamic zones had become a common pain point when using Gatsby with Strapi. Now you can specify which locales you want to fetch for every content type. Before this release, our Gatsby source plugin only fetched content in the default locale. Strapi supports Internationalization since v3.6. We have updated the plugin to let you benefit from the best and latest features of both products. What's new?īoth Strapi and Gatsby move fast and have recently released new versions and features.
That's why we're happy to release our work in a new major version. So after 250.000 downloads, 65 closed issues, and 55 code contributions, it was time for a change. It helps you query Strapi content in Gatsby, and lets you benefit from all the Gatsby goodness, like their automatic image optimization.īut our plugin was built in 2018, which, in the Jamstack world, is ages ago. That's why we created the gatsby-source-strapi plugin.
It's a great match! Strapi can handle all your content workflows, and Gatsby makes that content shine by building super fast (dare I say blazing?) websites. We know that many of you love using Strapi with Gatsby. The updated version of this plugin supporting Strapi v4 and Gatsby Cloud has been released.
0 kommentar(er)
