In this short blog post series I’m going to look in more detail at removing unnecessary distractions from SDL Web editors. This was also second item from my Five things you can do today to help your content editors talk at the 2015 Tridion Developer Summit.
SDL Web is an enterprise-scale content management system (CMS). However, the drawback of systems this size is that it’s very easy to overwhelm new or occasional content editors.
To prevent this, there are a number of ways of removing unwanted distractions, so that editors can focus on their core task – updating the website content.
This blog post is going to concentrate on removing unwanted publications.
Having separate publications in SDL Web (for content, design, structure, translations, etc.) allows reuse of both the technical and content work within the CMS. However, we need to be careful to ensure that editors only have access to the publications that they need to be able to perform their jobs.
For example, other than in very specific scenarios, editors of the global website probably don’t need access to the design publication.
In other cases, country editors might have access to more content or translation publications than required. For example, even though they need to be aware of the ‘global content’ publication, regional editors may not need access to it within the CMS.
Both of these are easy to rectify by following best practices for inheriting from existing user groups and setting the Membership Scope correctly for each of the groups.
Although any additional publications can be explained in training, this sort of mis-configuration that can leave occasional editors with the impression that Tridion is complicated or difficult to use.
In the next post in this series I’m going to look at further reducing distractions for content editors by minimising the number of content types (i.e. Schemas) that they can choose from when creating new content.