Alexander Haneng
Aug 15, 2013
  6364
(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

Please login to comment.
Latest blogs
Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026

Automating Block Translations in Optimizely

Stop manual block-by-block translations. Learn how to use the TranslateOrCopyContentAreaChildrenBlockForTypes config to automate Optimizely CMS...

Stuart | Apr 1, 2026 |