When building a website, it’s obviously important to create an easy and enjoyable experience for the end-user. Often forgotten however, but just as important, is the content editor’s user experience.
Content editors will be logging into the backend of a site regularly – everyday even – for as long as the site lasts (which can be years). So, you have to create an interface that they won’t dread working with every time they have to create a new page, edit an article or moderate user content.
Since a project’s success depends on the content editor’s happiness just as much as the end-user’s, we have tips on where to start and what to consider in making their job easy.
Who exactly are you building for? Before any planning or building begins, get to know your content editor's level of expertise and experience. The user-interface should reflect a content editor's skill and comfort working within a content management system. For example, if they're totally new to managing online content, the user-interface should be configured to be as simple as possible to accommodate their beginner mentality.
Getting to know your content editors will help you make decisions like choosing to use rich text areas versus a module with properties that lays out the content depending on its associated logic. While one option is more flexible, the other is easier to update.
If you find out that your editor will be consistently updating content that is shared across the site, you should make that task as easy as you can; a module that lays out the content differently in each area makes the most sense.
The more you can gather about an editor’s experience, abilities, their learning-curve and habits, the easier you can make their job.
Once you understand who you’re building for, the next step is to create use cases for your editors – and then make them part of your development plans.
For example, editor use cases include:
Now it’s time to set up a workflow for the use cases that you came up with. As an example, let’s use placing an Image Slider on a page and then linking photos and thumbnails. A basic workflow is as follows:
The workflow for each use case should be intuitive for your content editor, and each one should be planned out before any development begins.
Content organization is key at this stage. Within a couple of years into a site’s life cycle, files and folders can start to get messy, which can be very frustrating for anyone trying to navigate through it or manage it. By setting content editors up with an organization structure (uniform naming conventions, folder structures, etc.) it will be hard for them to deviate in the future.
Build modules that are reusable to make future expandability easy. Your content editors will definitely thank you when it’s time to expand and grow their site. It lessens the learning curve of having to adapt to a completely new functionality.
Examples of ways to make a module reusable include:
It’s also important to plan for new people that will join the online content team down the road. Whether it’s adding new content editors to a growing team or replacing ones that have left, new hires should be able to pick up the workflow easily.
A great way to prepare for new hires is to create a training guide that is easy to follow. The training guide should be very detailed, and it should outline how to use different modules and functionality step-by-step.
Content editors should also be able to quickly reference it on-the-go as they’re using the CMS and get stuck. A training guide is a great resource to have in every content editor’s arsenal.
To make your content editor’s experience as streamlined as possible, automate whatever you can.
This includes things like URL generation and thumbnail generation. Implementing automation for small tasks like this will save your editors a lot of time down the road.
The final step in ensuring your content editor’s happiness is to give them plenty of time – during development – to get familiar with the new interface.
Getting your editors to enter content during the development stage is important because it allows them to get comfortable with the system well before the site goes live. It also allows time to get their feedback and to make adjustments accordingly. This will help avoid hiccups or frustration after launch.
[dropshadowbox align=”none” effect=”lifted-both” width=”auto” height=”” background_color=”#ffffff” border_width=”1″ border_color=”#dddddd” ]Agility is a cloud-based, agile and powerful content management system equipped with tools and features that make building and managing your online properties easy and stress-free. To learn more, visit agilitycms.com.[/dropshadowbox]