Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
okay I think I'll get started it's right on 1045 so I hope you're all in the right place this session is for the love of the content editors and my name is Pamela Barone just a quick introduction of myself I work for a Drupal shop that's based
in Sydney and we're called previousnext I've been doing Drupal for about two and a half years and I'm currently working as a client services manager we do a lot of government media nonprofit higher education web sites and I am also a former content
editor so it's not really a conflict of interest that's not the specific reason that I'm interested in this topic but now having done both so having been a content editor and now as a project manager I think it gives me some insight into the value
that this can provide so the concept here is that you can build better websites and get better results by paying a little bit of attention to usability issues I'm so i'll start by explaining why i think this is true and then i'll go through some
specific ways that i found that we can achieve this and just a quick disclaimer I'm not I'm not going to talk about major UX improvements and complex editorial workflows um there's so much complicated stuff you can do in Drupal around usability
but my intention is to get you to start start really small and start paying attention to little things that you can build into your process without really adding too much to the budget so the idea is to start with a foundation and start with a few best practices
and strategies that get you toward a baseline of usability that you can then extend with the complicated stuff but if you're here to learn about complex UX and editorial improvements then you're in the wrong session so just just thought I'd let
you know so the ideas yet just get to get you thinking about these things and then working out little ways that you can find on your projects to improve it as well and I think it's important for us to just talk about who content editors are I think there's
often a wall between project teams and editorial teams so most of our developers absolutely never come in contact with content editors they don't talk to them the client lead doesn't talk about them so nobody really asks and as a result we don't
know very much about them and there's no real answer here who are these people they range on a very wide spectrum from very non-technical to extremely technical and oftentimes these two types of people will be working on the same team so you you can't
really nail it down but i think that concept of your catering to a really wide range of people is really important and the other point to make is that it also ranges in use so some people are using the system maybe once a month sits you know they have ten
other jobs and one thing they do is update the website once a month and then you have people that work in it six hours eight hours a day non-stop that is their job is to work on the website and another important thing about even those people is even people
that work in it all day some of these people are writing their own content some of these people are getting emailed content in 15 different formats from 15 different people so there's no real cookie cutter model that you can say yeah this this would suit
all of them because they range so why the and it doesn't really matter which end of the scale there on if you apply some simple principles you can make their experience a lot better so that's who they are but why are you here why are we talking about
this um quick cautionary tale when I worked as a content editor I think I use probably about five different CMS's in in about four years and every time we had a new one the you know our boss would go off and spend a year building in and I don't know
what he was doing over you know in all these meetings and someone who come in one day and just say okay you're going to be trained now in your CMS so we would sort of hesitantly walk in the room and sit down and it never failed that within 10 minutes they'd
shown us something that completely undermined our workflow it it showed us that they had absolutely no idea what we were doing on a daily basis and they hadn't put any consideration into how we were actually going to use it and it really it was the little
things that drove us crazy that that showed us that they hadn't paid attention and I always thought because most of these systems were very large clunky expensive proprietary CMS's that it was a case of well it's just too hard to change this is
what you get out of the box and so that's what it is so it was never really an option to say well you know maybe if you changed this a little bit would save us a lot of time and when I started working in Drupal I couldn't believe that this was still
the way it was being done and it was the way it was being done on most of even the projects that I managed the client Lee didn't didn't discuss these issues didn't want to let us talk to the content editors just didn't really consider it important
and I think the advantage that we have using Drupal is that there are so many really small things you can do to make it better for these people um and it's not about saying well we just want to improve people's lives you're you're creating
a tool that enables people to publish information to promote some kind of a business goal so the ease of use of that system directly correlates to the value for the client if publishing things is harder annoying or frustrating then your tool is less valuable
to them because it's going to get done slower and it's going to get done less often if it's a nice system that they don't hate to use and they can do things quickly and efficiently it's it's more likely to successfully promote that
goal that they initially came to you for in the first place so it's not it's important not to think of it as you're doing someone a favor or you know this is a little nice thing you that you can add at the end it's it's critical to the
delivery of a successful product that the system is usable so you know it is nice when you make something that people like to use but that's not really the point I mean just put it simply if they'd hate to use it then they won't use it and then
they will say bad things about you which I can assure you we did very very often and for a very extended periods of time so I mean if I feel like that's a pretty kind of obvious point that if it's a nice system then it's a better product but most
people still don't do it they don't they don't focus on us they don't really care about it and I I don't I mean I think there are a lot of reasons why the first one being it's just easier if you don't so there are a lot of other
things to focus on their complex back-end integrations ours you know is it pixel perfect matching the design and and if the client doesn't care then it's really easy for you not to care um if you wait till the end so if you say well the client didn't
ask for it let's just hand it over and then see what happens that is just not going to work because if the client didn't think it was important then um they will be made to know that it was important after like I said we were constantly complaining
and her saying these people and saying you know what why didn't they ask us just the simplest question so at the end it's too late and not because you can't make changes and um you know you've locked yourself in obviously we all know you can
still make changes but the damage is done by that point so if you've delivered something that's very clearly shows no lack of no indication that you gave it any attention then they're their suspicions are validated so we always approach this very
suspiciously if we weren't consulted we'd come in saying it's going to be another one of these ones where nobody asked us nobody knows what we're doing and they're going to just sort of impose this upon us someone someone once put it as
being a victim of a CMS and I I just don't I just don't think that that should be happening with Drupal so um the goal here is to start from the very beginning and build it into the process if you start at the beginning and if you if you do it from
the beginning it's not that much work as you go along so the first tip is don't settle for core and we all know this on a technical level that core doesn't provide everything you need to make a website so we always install country of modules and
[ ... ]
Nota: se han omitido las otras 4.267 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.