Do anybody want Cloudinary as a featuredpath option to support 3rd party storage and image transformation?

[blgo]

I have been working on a travel and photography blog using this theme for a few weeks now and I am using Cloudinary as a free service for domestic use and it works great.

I have mashed together some customizations which integrate display photos hosted in Cloudinary using the featuredpath front matter property and fancybox for embedding any image I want in the content markdown.

I am also using some Javascript to make the images responsive from the source if Cloudinary is your choosen "featuredpath".

All my customisations are on my github repo which hosts the website source: blgo/travel-blog

Would it be worth to tydi up my code - for this I might need a bit of help -, make Cloudinary cloud name configurable and create a branch for merging it into the theme?

[pacollins]

I'm not familiar with the service, so I'd have to read up. This might steer too much into the realm of bloat if it isn't a common platform. Lets see what some others say. If not we could (once we get the wiki going) explain how to implement it and leave it up to the user to make the changes (and gladly link to your repo 😄 ).