DrupalCon Barcelona 2015: Site building great editorial experience
If you ask what all Drupal projects have in common, chances are high to agree it’s about content creation and management. Often shiny features are implemented without considering the main audience of the website: the content authors themselves. Drupal’s purpose is making content management easy and doable by people who write text and not code.
Often content editors struggle with interfaces that don’t meet their needs. Huge lists of items or not really searchable lists of content, internal links that are impossible to handle or fields with weird names and no indication of their purpose affect experience with Drupal in a negative way. Also plenty of items in the admin menu, 2/3 of which you don’t need, and actually needed items missing doesn't help much. These are just some of the problems editors encounter and not particularly love Drupal for. However, all these problems have nothing to do with Drupal itself. Because it’s a matter of configuration.
In this session we will share our approach to making content editors happy. Starting with basics, like modules that we use for each our project, we will continue with features and tricks that allow us to design great infrastructure for editors independent of content type complexity. We will also discuss how you can extract necessary information to understand needs of editors. Finally, we’ll tackle which cases need to be specified and implemented from the very beginning and what can easily be implemented in later phases of a project.
At last but not least we will have a look into the future also known as D8, and talk about made and needed steps for the great editorial experience in Drupal 8.
This session will be presented by Anna Hanchar, User Experience Specialist of Amazee Labs and Claudine Braendle, Amazee Labs Developer, and is interesting for site builders, project managers and all people who want to create solid working solutions.
Often content editors struggle with interfaces that don’t meet their needs. Huge lists of items or not really searchable lists of content, internal links that are impossible to handle or fields with weird names and no indication of their purpose affect experience with Drupal in a negative way. Also plenty of items in the admin menu, 2/3 of which you don’t need, and actually needed items missing doesn't help much. These are just some of the problems editors encounter and not particularly love Drupal for. However, all these problems have nothing to do with Drupal itself. Because it’s a matter of configuration.
In this session we will share our approach to making content editors happy. Starting with basics, like modules that we use for each our project, we will continue with features and tricks that allow us to design great infrastructure for editors independent of content type complexity. We will also discuss how you can extract necessary information to understand needs of editors. Finally, we’ll tackle which cases need to be specified and implemented from the very beginning and what can easily be implemented in later phases of a project.
At last but not least we will have a look into the future also known as D8, and talk about made and needed steps for the great editorial experience in Drupal 8.
This session will be presented by Anna Hanchar, User Experience Specialist of Amazee Labs and Claudine Braendle, Amazee Labs Developer, and is interesting for site builders, project managers and all people who want to create solid working solutions.