Alexander Haneng
Aug 15, 2013
visibility 6466
star star star star star
(0 votes)

EPiImage is moving to the cloud in EPiServer CMS 7.5

5 years ago, when the first lines of code for EPiImage was written, the online world was very different from now, and so was EPiServer CMS. A lot has changed since version 5 including a radically new editor UI, and in the next release (7.5) we will also see files becoming pieces of content just like pages and blocks.

 

The time has come to start fresh and look at what  EPiImage would have been if it was created from scratch today:

 

Speed

One of the big changes since 2008 is speed. We are expected to deliver more data to the end user in less time than ever, and more and more often we are suppose to do so over a slow, unreliable radio link aka a mobile network. (3G network request latency can be 1000+ms)

Using a CDN (Content Delivery Network) has just in the last year become a must even for smaller sites, and is a cheap and efficient way to increase the speed of your site.

 

image

Image from internap

 

The cloud

Another change is the growth of the cloud and cloud based services. One such service that we have used with great success is Cloudinary.com, a service that provides image scaling and manipulation on the fly. It also has cool features like face detection based cropping!

It is a paid service, but they also offer a free version(500MB storage, 1GB monthly bandwidth).

 

image

 

New Editor UI

One of the main features of EPiImage for CMS 5 was the ability for editors to preview images without having to click publish first. In version 7 this functionality comes out of the box in the new UI and is no longer needed. But how do you best handle a image gallery property in the new UI? As a fly out?

 

Files as IContent

In the upcoming version of EPiServer CMS files gets some much needed love and are crowned IContent on the same level as pages and blocks. This means files now can have properties opening up many new exiting possibilities!

 

The way forward

I have started work on a brand new module that will leverage Cloudinary.com both for image transformations and CDN, and use the new file system that will come in EPiServer CMS 7.5. I will share more information as the project progresses.

If you want to contribute or have ideas on what this new module could do, please leave a comment below.

 

What about EPiImage?

EPiImage is still available and open source. There are still a few people in the community that develop new features and fixes bugs, but I will focus my efforts on this new project.

Aug 15, 2013

Comments

error Please login to comment.
Latest blogs
Exploring Asset Lifecycle Management Approaches for Bynder and Optimizely SaaS CMS

Note: This is Part 3 of our Bynder integration series. For setup and filtering prerequisites, see Part 1  and  Part 2 . Introduction In my previous...

Vipin Banka | Jul 5, 2026

Unlock AI-Ready Experiences with Optimizely

Over the past few months, almost every customer conversation has shifted from SEO to AI readiness. The questions are no longer just: “How do we......

Madhu | Jul 5, 2026 |

Planning Your Bynder DAM and Optimizely SaaS CMS Integration the Right Way: Avoiding Asset Sprawl and Unnecessary Synchronization

Note: This is Part 2 of our Bynder integration series. If you missed the Part 1, check out " Implementing the Bynder DAM Connector with Optimizely...

Vipin Banka | Jul 4, 2026

Implementing the Bynder DAM Connector with Optimizely SaaS CMS: Lessons Learned

What I learned while integrating Bynder DAM with Optimizely SaaS CMS, exploring Optimizely Graph, and building a headless frontend experience....

Vipin Banka | Jul 3, 2026