We made a new release of the Cloudinary Store plugin for the Ghost platform with some major improvements.

First of all the plugin was aligned with the new storage development specifications to be fully compliant with the Ghost 1.0.x version (it is used on this blog already).
You can find the official documentation here but it is nothing more than a complete refactor of the code.

The second thing, which I discovered on a pull request made on the official plugin repository (the one referenced on the Ghost website), is the usage of the Cloudinary's image manipulation API.
This enhancement was made by @aphe sever weeks ago but it seems the owner of the official repository is not active anymore.

With @aphe we decided to merge his changes in the new branches I created for Ghost 1.0.x (also pull requested to the official repository) and all is now available on this branch: https://github.com/mmornati/ghost-cloudinary-store/tree/update_ghost_1.0.0
You can clone it and install directly on your blog if you want to take advantages to these changes.

What can you do right now?
Essentially there is a little change in the plugin configuration

"storage": {
    "active": "ghost-cloudinary-store",
    "ghost-cloudinary-store": {
        "cloud_name": "yourCloudName",
        "api_key": "yourApiKey",
        "api_secret": "yourApiSecret",
        "configuration": {
            "quality": "auto:good",
            "secure": "true",
            "anything-else": "values"

Inside the configuration part you can put anything you need coming from the Cloudinary Image Transformation API. The configuration will be applied to all the images you will upload to the blog.
You can resize, crop, optimize, change the quality, ... and much more.


On the documentation you will see the name of the property you have to set and all the possible values.
For example, for the quality property:

After the image upload, Cloudinary will send back the image URL that should be integrated into the blog page, with all the configuration you set.

Example of the image url:
Which is following the configuration I put few lines ago: secured with quality good.

If you need any further information on this topic you can contact @aphe and me.