|Number of votes:||5|
This version contains a few major bugfixes and improvements that we gathered during the past 3 weeks from both internal and external developers.
Release notes for v0.2.0 can be found here:
This documentation can also be found on our github page
The nuget is available on the EPiServer nuget feed at:
Previously, we did not have much documentation so this time we focus a bit more to describe how it actually works in details.
This project is a set of useful enhancements that may gradually improve the reviewing process in organizations using EPiServer as their CMS.
It solves a few major issues the Authors identified during their journey with EPiServer and after working on a number of EPiServer related enterprise solutions.
Allow editors to preview unpublished and unreviewed content.
As we all know, an EPiServer page is usually not self-contained but rather consists of many other content items like blocks or media files.
In such scenarios it is very hard for reviewers to see the "big picture". Let's say a page consists of several blocks and a few images. Now, in case the page author changed all those blocks and images the reviewer will have to manually go through all of them and approve them individually without, in fact, being able to see those changes in the actual page context.
This project gives the editors a way to generate a unique URL that will present the page exactly as they see it. The preview engine will ignore content status and the content approval process.
In the current workflow, the reviewer can just provide a single comment that has to include all comments for a particular content version. Then, it is the editor's responsibility to match the issues raised by the reviewer with specific parts of the page.
After receiving such comments the author of the content will see all issues raised by the reviewer.
The author can respond to each of them individually by adding a reply message or attaching another screenshot with explanations.
Pin is reviewed it can be marked as
All pins are saved and can be reviewed at any time in a dedicated
Let's say we configure a very basic approval workflow with a single approval step and a single reviewer.
Each pin is in fact a standalone
Thread the can go on until both Reviewer and the Author are satisfied with the end result.
This feature is a combination of the previous ones. It is to allow external reviewers, so the user that may not be a part of your organization, or simply users who are reluctant to learn EPiServer to access unpublished data and provide feedback if needed.
All generated links are token-based. You can generate as many links as needed, each of them can be revoked at any time.
Additionally, all urls are time limited (the TimeSpan can be configured, please look further down) which means that after a specific amount of time such link will no longer work.
You can visually express issues in reviewed content by highlighting or adding screenshots
Once you decide to attach a screenshot then we will automatically determine the dimensions of the EPiServer property that was clicked on and preselect it. The default crop can be changed according to your needs.
The highlighting tool allows you to clear and redraw.
Allow to display draft content version without logging to Episerver.
This is an Edit mode component used to generate external review links. There are two types of links:
Editor can share external review links using share dialog. The [#link#] constant will be replaced with link to content.
Below is an email example: