Enhancing Content Author Experience – Layouts level
This is the second post as part of Sitecore Enhancing Content Author Experience series.
In previous post, we had explored how can we enhance content author experience from template perspective, in this post, let’s explore at layouts level.
1. Data source Location
In Sitecore, each page is a collection of components. We can add any number of components to a page, and some of the components we add to the page, have their own associated content. Content authors can select the associated content using data source. If we are not restricting data source location, then full content tree is shown in the selectable items list, then content authors have a tough time to navigate and select the associated content.
Giving proper Datasource location helps in this situation, we can set selectable items location, while creating sub-layout/rendering using Datasource Location field.
without data source location (full content tree is listed as bel)
with data source location (items shown, based on the location)
Here you can read more information about data source location.
2. Data source Template
Once we specify data source location, still content author has to know, What’s the associated content item to choose. If there are only similar content items present in the location, then it becomes easier. But what if there are different variety of content items are present, then it is our job to guide them, to select proper items.
We can achieve this by using Datasource template, which can be set on sub-layout/rendering Datasource Template field.
Without Data source Template:
- Any content item can be selected.
- Create New Content option is grayed out, because, Sitecore does not know, using which template it has to create new item. (I remember in Sitecore certification exam, there was a question on when does Create New Content is grayed out)
With Data source template:
- Sitecore prompts with a message, when other template item is selected.
- Create New Item option is available, using which Content authors can create new content directly from here.
3. Placeholder Settings
We can empower the Experience Editor using placeholder settings (Allowed Controls). It is very important to set allowed controls for each placeholder, otherwise it would be difficult for content authors to know, What are all components can be placed on particular placeholder.
Without allowed controls being set, content authors have to navigate from root and find exact component to add.
Without Allowed controls being set
With Allowed controls being set
After allowed controls is being set, now content authors can see the list of renderings in Select a Rendering window. But there is no visual clue, about what design they see on page, by selecting a particular component. Thumbnail is useful for this purpose.
Thumbnail can be set at Rendering/sub-layout items. We have an option to take screen shot as well, or select an image from media library.
Below, we can observe that “Article module” is having thumbnail view, but Product module is not having any thumbnail view.
Thank you for reading, in next post, will explore the tips from content level.
Happy Learning 🙂