![]() ![]() Hover over one of your images, click on the more options menu (…) icon from the list of actions.First, you need to get all your images uploaded to your Cloudinary Media library. ![]() ![]() Follow the steps below to add tags to your images: Information such as its format, type, dimensions, contextual metadata and structured metadata will be returned for each image. Cloudinary will generate a JSON snippet containing all the images with that specified tag. When you assign tags to assets, you can perform group actions on them. Cloudinary allows us to list resources from the client-side based on their tags, so we need to add resource tags to the assets (images) we want to use in our gallery. We will be using Cloudinary’s list delivery type to generate a JSON listing of the images we will use in this project. Log in after creating your account, and on your dashboard page, you should see all your credentials (cloud name, etc.). If you don’t have a Cloudinary account, you can sign up for a free account. A KendoReact account with a commercial license key or an active trial license key.To follow this article, I recommend you have the following: This post assumes you are familiar with the basics of JavaScript and React. In a nutshell, we will build our Next.js application with components from the KendoReact library and bring in our image assets from Cloudinary. In this post, we will be building an image gallery with Next.js and KendoReact. We will be building this application with UI components from the KendoReact library and bringing in our images from Cloudinary. I prefer not to modify Ghost code (it will be easy to add the automatic upload to cloadinary) because they already have this feature in the dev roadmap and because I'd like to be able to update Ghost easily when a new version is released.In this article, we will build an image gallery with Next.js. The target is: new post, upload all images to cloadinary, update post into the blog. In the next version I'll make the update automatic. Then, for any post, you can replace all local images with a cloudinary version, which will be automatic uploaded: bin/ghost cloudit 289.mdĬ:\Users\mmornati\Documents\projects\ghost-cli\pages\289.mdĪnd now you just need to update your blog post with the new content: all your images will be on cloudinary. You can now check all posts with "local" images: bin/ghost checkcloudĬ:/Users/mmornati/Documents/projects/ghost-cli/pages/288.md: 1Ĭ:/Users/mmornati/Documents/projects/ghost-cli/pages/289.md: 3 cloudid : to upload all post's images to cloudinary and update the (offline) post.īefore you begin you need to dump all blog posts (with your latest extracted file): bin/ghost dump.checkcloud: to get the list of blog posts containings local images.You can find the forked version on my github: /mmornati/ghost-cli I then decided to make some changes to allow an easy way to upload ghost local images to cloudinary and I also updated the script to use the latest Ghost 0.5.2 version. "Offline" just because there is not a real interaction with your blog to use the script you need to export all your blog posts into a file which will be used for all operations. It allows you to make some "offline" operation on your Ghostblog. I recently discovered this project on the net: /jeffdonthemic/ghost-cli ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |