World is now on Opti ID! Learn more

Per Magne Skuseth
Apr 21, 2017
  6585
(0 votes)

Introducing Content Inspector

The Content Inspector is an open source addon for Episerver which helps you get a better overview and improved navigation of complex content structures, such as nested blocks.

Once installed, it will add a new menu item to the content area dropdown menu, which lets you "inspect" the selected content, showing property values. This includes content areas, which means that nested content (blocks in blocks) can be viewed and navigatd with ease. This is demonstrated in the GIF below with a "carousel block" which contains sub blocks.

Image inspector.gif


Name, type, publish status and content area property values are displayed by default in the content inspector view. To display additional properties, use the Inspectable attribute on properties:

[Display(Name = "Carousel image")]
[Inspectable]
public virtual ContentReference CarouselImage { get; set; }

[Inspectable]
public virtual string ImageDescription { get; set; }

[Inspectable]
public virtual string Heading { get; set; }

This can be particularly useful for blocks that contains images:

Image inspect_with_props.png


There is also an option to inspect the entire current content, and not just a single content area item.

Image inspect_current_content.png

By clicking Inspect current content, every content area item will be listed, as well as any properties marked as inspectable.

Image inspect_personalized_and_forms.png

Any kind of IContent can be listed, whether it is pages, blocks, forms, media or commerce content. As shown in the image above, visitor groups are also displayed.

I originally made the addon for Varner Retail, who came up with the idea. When I asked if I could share it as open source, the answer I got was "The Episerver community has given us so much. I don't see why we shouldn't give something back". Thanks, Varner!

Compatible with Episerver 9 & 10.

Git | Nuget

Apr 21, 2017

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |