Chore/2.6.0

.stackblitz/package.json

@@ -11,6 +11,6 @@
     "nuxt": "^3.8.0"
   },
   "dependencies": {
-    "@nuxtjs/cloudinary": "^2.5.2"
+    "@nuxtjs/cloudinary": "^2.6.0"
   }
 }

docs/app.vue

@@ -87,6 +87,11 @@ provide("navigation", navigation);
     </template>
   </UHeader>
 
+  <CldOgImage
+    src="images/nuxt-cloudinary-social-background"
+    twitter-title="Nuxt Cloudinary Documentation"
+  />
+
   <NuxtLayout>
     <NuxtPage />
   </NuxtLayout>

docs/content/1.getting-started.md

@@ -71,3 +71,13 @@ export default {
 - Default: `process.env.CLOUDINARY_CLOUD_NAME`
 
 Your unique Cloudinary Cloud Name. You can find it in the Cloudinary dashboard.
+
+## NuxtCloudinary vs Nuxt Image
+
+You may be wondering what is the reason to have both Nuxt Cloudinary and Nuxt Image modules if they both have integration with Cloudinary and they tackle the aspect of optimized images.
+
+This is a good question that should be answered by showing examples when one module is better than the other:
+
+If you need just an optimized image/picture component with ability to connect to various providers (including Cloudinary) you may use `Nuxt Image`.
+
+However, if you are looking for a solution that would allow you to use advanced AI powered image transformations, optimized videos, OG Images, and prebuilt components like ProductGallery, MediaLibrary, or UploadWidget, `Nuxt Cloudinary` will be a better solution for you.

docs/package.json

@@ -17,6 +17,6 @@
     "typescript": "^5.3.3"
   },
   "dependencies": {
-    "@nuxtjs/cloudinary": "^2.5.2"
+    "@nuxtjs/cloudinary": "^2.6.0"
   }
 }