chore(doc): Add using cloudinary plugin for images to reference guide…

…s. (#22798)

* Add guide to using cloudinary plugins

* chore: format

* Update link to using-gatsby-image

* Add guide to using cloudinary plugins

* Corrected my awful mistakes 😳 and updated this doc

* Remove extra Cloudinary link

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update doc on cloudinary plugins

* few fixes

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Updated Doc

* chore: format

* Updated doc

* Update docs/docs/using-cloudinary-image-service.md

Co-Authored-By: LB <laurie@gatsbyjs.com>

* Add additional information on parameters

* Update docs/docs/using-cloudinary-image-service.md

* chore: format

Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>
Co-authored-by: LB <laurie@gatsbyjs.com>

docs/docs/using-cloudinary-image-service.md

@@ -0,0 +1,156 @@
+---
+title: Using Cloudinary image service for media optimization
+---
+
+Cloudinary is a cloud-based end-to-end media management platform that provides solutions to help site creators serve optimized media files (images and videos) to their audiences. It also provides a lot of optional transformations that can be carried out on these media assets.
+
+In this guide you will take a look at the [gatsby-source-cloudinary](/packages/gatsby-source-cloudinary/) and [gatsby-transformer-cloudinary](/packages/gatsby-transformer-cloudinary/) plugins which you can use to improve the experience of handling images on Gatsby sites.
+
+Plugins are generally used to abstract functionality in Gatsby. In this case, the `gatsby-source-cloudinary` plugin is a [source plugin](/docs/creating-a-source-plugin/) which helps to connect Cloudinary media storage capabilities to your site.
+
+> Here's a [demo site that uses the gatsby-source-cloudinary](https://gsc-sample.netlify.com) showcasing optimized images in a masonry grid, served from Cloudinary.
+
+## The problem with handling images on the web
+
+Dealing with images on the web has always been a problem as unoptimized images can slow down your site. The processes put in place to create the best media experience can take a lot of time to implement.
+
+## Solutions Cloudinary provides
+
+Cloudinary provides a couple of amazing solutions to this problem, namely:
+
+- Remote storage and delivery of images via CDN
+- Offers a wider range of transformations than [gatsby-image](/docs/using-gatsby-image/).
+- [Digital Asset Management](https://cloudinary.com/documentation/digital_asset_management_overview) for enterprise assets
+
+## Gatsby-source-cloudinary
+
+This plugin fetches media assets from Cloudinary that are specified in a folder. It then transforms these images into Cloudinary file nodes, which can be queried with GraphQL in a Gatsby project.
+`gatsby-source-cloudinary` applies [f_auto and q_auto](https://cloudinary.com/documentation/image_transformations) transformation parameters which aid in automatic optimisation of format and quality for media assets by over 70 percent.
+
+### Prerequisites
+
+Before using the `gatsby-source-cloudinary` plugin you should do the following:
+
+- Upload your images to a folder on Cloudinary. This folder can have any name of your choosing.
+- Obtain your API key and API secret from your Cloudinary dashboard.
+- Have the [dotenv](https://www.npmjs.com/package/dotenv) module installed for loading environment variables from a `.env` file.
+
+### Using gatsby-source-cloudinary
+
+Add the plugin to your project.
+
+1. Install `gatsby-source-cloudinary`
+
+```shell
+  npm install gatsby-source-cloudinary
+```
+
+2. In the root of your project, create an environment file called `.env` and add your Cloudinary credentials and their values
+
+```
+CLOUDINARY_API_KEY=xxxxxxxxxxxxxx
+CLOUDINARY_API_SECRET=xxxxxxxxxxxxxxxxxxxx
+CLOUDINARY_CLOUD_NAME=xxxxx
+```
+
+3. Configure `gatsby-config.js`
+
+```js:title=gatsby-config.js
+require('dotenv').config(); // highlight-line
+module.exports = {
+  ...
+  plugins:[
+  ...
+  {
+      resolve: `gatsby-source-cloudinary`,
+      options: {
+        cloudName: process.env.CLOUDINARY_CLOUD_NAME,
+        apiKey: process.env.CLOUDINARY_API_KEY,
+        apiSecret: process.env.CLOUDINARY_API_SECRET,
+        resourceType: `image`,
+        prefix: `gatsby-source-cloudinary/`
+      }
+    }
+  ]
+}
+```
+
+Note that `gatsby-source-cloudinary` takes the following options:
+
+- **`cloudName`** , **`apiKey`** , and **`apiSecret`** **:** These are credentials from your Cloudinary console, stored as three separate environment variables for security.
+- **`resourceType`** **:** This is the resource type of the media assets - either an image or a video.
+- **`prefix`** **:** This is the folder (in your Cloudinary account) in which the files reside. In the example above, the folder is called `gatsby-source-cloudinary`. Assign a name of your choice.
+  Other optional options are `type`, `tags`, and `maxResult`.
+
+Here's a [link to the README](https://github.com/Chuloo/gatsby-source-cloudinary#query-parameters) for more information.
+
+## Gatsby-transformer-cloudinary
+
+After sourcing media files from Cloudinary, you will be able to leverage Cloudinary’s media transformation capabilities. To do so, use `gatsby-transformer-cloudinary` which is a type of [transformer plugin](/docs/creating-a-transformer-plugin/) that is used to change image formats, styles and dimensions. It also optimizes images for minimal file size alongside high visual quality for an improved user experience and minimal bandwidth.
+
+Here's a [demo site that uses the gatsby-transformer-plugin](https://gatsby-transformer-cloudinary.netlify.com/fluid/)
+
+### Prerequisites
+
+Before using the `gatsby-transformer-cloudinary` plugin you should do the following:
+
+- Upload your images to a folder on Cloudinary. This folder can have any name of your choosing.
+- Have the `gatsby-source-cloudinary` plugin installed and configured.
+- Obtain your API key and API secret from your Cloudinary dashboard.
+- Have the [dotenv](https://www.npmjs.com/package/dotenv) module installed for loading environment variables from a `.env` file.
+
+### Using gatsby-transformer-cloudinary
+
+1. Install `gatsby-transformer-cloudinary` and `gatsby-source-filesystem` which creates the File nodes that the Cloudinary transformer plugin works on.
+
+```shell
+ npm install gatsby-transformer-cloudinary gatsby-source-filesystem
+```
+
+2. In the root of your project, create an environment file called `.env` to which to add your Cloudinary credentials and their values.
+
+```
+CLOUDINARY_API_KEY=xxxxxxxxxxxxxx
+CLOUDINARY_API_SECRET=xxxxxxxxxxxxxxxxxxxx
+CLOUDINARY_CLOUD_NAME=xxxxx
+```
+
+3. Configure `gatsby-config.js`
+
+```js:title=gatsby-config.js
+require('dotenv').config({
+  path: `.env.${process.env.NODE_ENV}`,
+});
+
+module.exports = {
+  plugins: [
+    {
+      resolve: `gatsby-source-filesystem`,
+      options: {
+        name: `images`,
+        path: `${__dirname}/src/images`,
+      },
+    },
+    {
+      resolve: 'gatsby-transformer-cloudinary',
+      options: {
+        cloudName: process.env.CLOUDINARY_CLOUD_NAME,
+        apiKey: process.env.CLOUDINARY_API_KEY,
+        apiSecret: process.env.CLOUDINARY_API_SECRET,
+
+        // This folder will be created if it doesn’t exist.
+        uploadFolder: 'gatsby-cloudinary',
+
+    },
+  ],
+};
+```
+
+> In `gatsby-config.js`, responsive breakpoints can be created for each image, use the `fluidMaxWidth` and `fluidMinWidth` options to set them. Take a look at the [plugin documentation](https://www.npmjs.com/package/gatsby-transformer-cloudinary#api) for more information on how these parameters can be set.
+
+## Additional resources
+
+- [Faster Sites with Optimized Media Assets by William Imoh](/blog/2020-01-12-faster-sites-with-optimized-media-assets/)
+- [Gatsby Transformer Cloudinary](https://www.npmjs.com/package/gatsby-transformer-cloudinary)
+- [Gatsby Source Cloudinary](/packages/gatsby-source-cloudinary/)
+- [Aspect ratio parameter ](https://cloudinary.com/documentation/image_transformation_reference#aspect_ratio_parameter)

www/src/data/sidebars/doc-links.yaml

@@ -150,6 +150,8 @@
               breadcrumbTitle: Static Folder
             - title: Using gatsby-image
               link: /docs/using-gatsby-image/
+            - title: Using Cloudinary Image service
+              link: /docs/using-cloudinary-image-service/
             - title: Working with Images in Gatsby
               link: /docs/working-with-images/
               breadcrumbTitle: Images in Gatsby