Embed Size (px)
DESCRIPTION
Content editors are amongst the most important but the most forgotten stakeholders in a CMS project. They are the ones producing all the content years over years. You can help them creating high-quality content, to be efficient and to make them raise improvements for further developments. In this talk I will provide suggestions on how and when to integrate content editors in the development process. We tend to discuss in length about the color of this or that box or the scope of this or that functionality. Mostly we never think how the content gets in the system and is being maintained. But we HAVE to care. Mostly we care when everything is ready, when changes are getting expensive and content editors are already annoyed by the system that has been put in front of them. This needs to change. Be friends with the content editors and deliver a better product. How to get friends with your content editor? The good news is, it will not require days of work, flowers or Swiss chocolate. With the Drupal standards - difficult. But by using Drupal's features wisely and installing some specific modules, you can improve the editor experience already by a lot. Examples are a better admin search, help texts, admin themes, just to mention some. Recorded session: https://www.youtube.com/watch?v=bA_ub6GcZZo
Citation preview
Be friends with your content editor
Agenda 1 Introduction2
3
4
5
What can we do?
Why should we care?
What about Drupal 8?Q&A
Introduction
http://bldn.gr/drupal_gmail
Why should we care?
The circle
Make some new friends!
• Don’t have much web-experience
• Are easily confused and lack of confidence
• Perform tasks very slowly and carefully
• Quick to learn new systems • Understand complex user
interfaces • Perform tasks quickly and
look for efficiencies
• Have a lot of other things to do besides maintaining the website
• Log in once every other month
• They don’t remember how the system works and will give you a call.
• They use the CMS daily • They perform the same
tasks (like writing blogposts) over and over again
• Get frustrated when the system is inefficient or doesn’t work as they expect it
Install contrib modules
#1
• Views bulk operation with Admin views • Administration menu • CKEditor • LinkIt • Admin theme „Shiny“ • Media • Scheduler
Some examples
Admin Views
Core
Can be adapted
Toolbar
Admin Menu
Core
CKEditor
Link field
with LinkIt
Seven
Shiny
Core
Scheduler
Core
Login Destination
Improve the flow and ask questions
#2
apply common sensecreate order
check workflowsgroup
removetrain
Naming
#3
Help Texts
#4
Write good help texts
Good help texts should: • describe where the field output will appear • answer any obvious questions • list any limitations or requirements
!Bad help text:
• is often worse than no help text
Bad
Good
Good
Help texts can reveal issues!
Create integrated manuals
Contextual Links
#5
You built it, you try it!
You built it, your team tests it!
Wrap up#1 Contrib modules
#2 Workflow
#3 Naming
#4 Help texts
#5 Contextual links
What about Drupal 8?
Questions?
@borisbaldinger [email protected]
Thanks to Pamela Barone that I could use her storyline @pameeela
