Alexander Haneng
Jun 14, 2012
(5 votes)

EPiServer 7–The start of a new era

With EPiServer 7, and especially EPiServer 7 CMS EPiServer AB takes a brave and necessary step into the future. As Peter Sunna (the release manager for Falcon) said in Stockholm last week: little have changed UI wise since EPiServer 4 eight years ago.


A brand new UI

With the new UI the actual page is the center of the editing experience and not html forms like in versions 4 to 6, and this can only improve the editor friendliness that EPiServer is already so famous for. During the demo in Stockholm Peter simply dragged a picture from the file manager to the picture area on the page where he wanted it. It can’t be done any simpler. (I know, I have tried Smile)



EPiServer CMS 6 R2




EPiServer 7 CMS


Major update to the core

The new UI is going to get all the attention, but the core of EPiServer has also gone through a revolution. The focus has gone from just pages to also include pieces of content (blocks) that can be reused on different pages, and even on different sites. This also offers a more logical grouping of properties, so instead of adding 5 person related properties to a page, we can now create a person block containing first name, last name, picture, email and phone number, and then add a person property to the page type! This block can of course also be reused on other page types. Page types and blocks can also be defined in code like we are used to from Page Type Builder.


“I need some boxes over here”

In nearly all projects the customer requires some “boxes” on the right hand side of every page that they should be able to select specifically for each page. Up until now this have required a separate product (Composer), web parts or a custom solution, but now this will be built into the CMS. Having this as the standard is going to change the way we think about EPiServer sites and pages.


And a whole lot more…

There is a ton of more features coming with EPiServer 7, and you can read more about it here and here.










What does Making Waves think about EPiServer 7?

As a big (the biggest?) EPiServer partner we have a lot invested in the EPiServer platform, and thus any big stumbles will affect our business*. So what are our feelings about EPiServer 7?

We think it is a gamble to change the editor UI so radically from what EPiServer editors have been used to work with every day for the past 8 years. But knowing how much time and effort EPiServer AB has spent testing and perfecting the concepts behind it, we are confident that they will succeed and end up with a superior product. In addition they have been wise enough to separate the UI from the core into an add on, making it easier to update the UI more often than the yearly release cycle we have been used to with CMS 5 & 6. So if any big snags are found after the release, they can simply push out an update.




It is also nice to see that EPiServer 7 can keep up with the competition. One of the strengths of WordPress is that editors can add new features using plugins, and now EPiServer will match this with the “add-on” store. Also the built in “composer” functionality is a big leap forward.



feedweb screenshot 1

WordPress plugins





EPiServer Find aka Truffler

We are also very happy about EPiServer’s most recent purchase: Truffler. We have used Truffler in projects and it is a premium search engine. Our hope is that they can add a lite version of EPiServer Find in the basic CMS product. This will open up for brand new ways of searching for pages and blocks, and use the results to create navigation, lists, related content etc.



Order form for Tema travels using Truffler.




The start of something great!

To sum it up: we think EPiServer has done the right strategic moves with EPiServer 7 and recent purchases. We are looking forward to an exiting year ahead of us building great digital experiences for our clients with the new EPiServer 7 stack!



*We also deliver on other platforms like SharePoint, Wordpress, eZ Publish etc., but EPiServer is by far our biggest platform as of today.

Jun 14, 2012


Please login to comment.
Latest blogs
Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog

New Optimizely certifications - register for beta testing before November 1st

In January 2023, Optimizely is making updates to the current versions of our certification exams to make sure that each exam covers the necessary...

Jamilia Buzurukova | Sep 28, 2022

Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog

Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog

Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog