Bryan Braun (@bryanebraun) gave a refreshingly opinionated talk Empowering Content Creators with Drupal. Coming directly from the Ruby and Rails communities where a core value is to articulate best practices, it is great to see this kind of guidance from a member of the Drupal community. (slides here)
Bryan referred to a blog post by Dilbert creator Scott Adams on the Botched Interface Market, where sites like Orbit and Travelocity had such poor user experiences that they inadvertently created a market opportunity for new sites like Hipmunk. Bryan’s goal is that Drupal should not become a botched interface market.
He organized his advice into two categories:
Bryan highlights borrowed techniqes from other platforms (mostly WordPress), and points out lots of “low-hanging fruit” techniques.
Example: the default layout for a node has a lot of labels and whitespace which doesn’t contribute to understanding the page. The default UI for a file attachment is not concise. Compare Gmail’s message compose interface vs. what it would be in Drupal (~1/3 of your screen vs. a page that is two screens high!) Having a very long page can contribute to confusion, since you have to scroll to get to some of the functionality.
Larry Garfiled’s blog post Drupal is not a CMS points out that Drupal is something you use to build a CMS. Perhaps we should think of it as a CMF, a Content Management Framework. In this case, we are designing the workflow and user experience of a new custom CMS that we build with Drupal.
Myth: I am not a designer
Fact: um.. you actually are. Whether you identify as a designer or not. The decision you make when you are building a site has an effect on the end user — these are design decisions!
We can make our content creators more productive by giving them “power tools” while at the same time, reducing risk that they will make mistakes will give them confidence to move faster.
It’s not really an option anymore to tell people to edit HTML. [My personal perspective is that even though I am perfectly capable of HTML markup, why should you make me type extra characters? why should I have to learn the markup that works with your stylesheet? Though I do like the option of editing HTML when the rich text editors fail me.]
The following modules are good for WYSIWYG and File Upload:
- wysiwyg or ckeditor which both appear to be rich text, WYSIWYG editors
- media or imce for uploading and managing file (also seems to be an either/or choice
Node Editing Power
Always check “Add to Menu” on the Node Edit page — for most content creators, if a menu isn’t there, the feature doesn’t exist.
With context, use a module with Context Node which can pull out just a few context options and put it on the Node Edit page.
As a themer, you can make a bunch of templates and the content creator can pick with template -picker module.
Use Short Codes
Short code are a best practice from WordPress and can accelerate content creation:
- Caption Filter
- Video Filter works with the wysiwyg module or with TinyMCE or CKEditor (not sure why those are in a different category).
- Insert View lets content editors add views without editing PHP
- Make your own
In Drupal we tend to expose this kind of functionality as a block, but that gives the power to the site builder, rather than the content creator. In Drupal, the modules that do this tend to be called filters.
Always put description text when you are creating new fields (you probably won’t come back later). If you are going to come back later, you can improve it then — at least put something in.
- Revisions: just enable it by default
- Preview — poor experiences with the preview button, not always what you expext
- Turn off preview button on content types page, use use view_unpublished module instead
Granting Appropriate Access is not an easy fix. You need to understand how your organization works, know the users, watch them work, etc. Once you do know those things, you can set up good workflows for them with clear options for the different roles in the organization.
- Use the “shortcut menu” that comes with Drupal7
- Admin Menu Source lets different roles have different menus
- Menu Item Visibility module — remember the menus are their interface
Admin Themes can help
Group things according to how your content creators think about them, not how you built them. Consider grouping admin menu items into safe vs. risky like WordPress does. Bury advanced and less-frequently used functionality.
- Fields into fieldsets & field collections
- Admin Menus for content creators
- Permissions into Roles
- WYSIWYG Icons
Default to expanded for highly recommended options, collapse for optional, and hide anything that is unnecessary.
- Use conditional fields (never show someone an option that does nothing
- Simplify hides fields
- Jammer hide many other things)
- Hide Submit Button avoids double submissions and just an importantly communicates to the creator or editor that the site is actually doing something
- Preview Button (see above)
There are lots of great dashboard modules. Consider what your creator or editor wants to see the most — make that their default homepage.
“the best tool of them all… …is the one that works best for your users”
It looks like I’ll still have to do quite a bit of experimentation, since Bryan often points to multiple modules to solve the same challenge — still a great reference to address common concerns and highlight best practices.