Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Making Drupal Friendli(er) for Content Editors

1,911 views

Published on

Presentation at DrupalCamp Atlanta and DrupalCamp Boone.

Published in: Technology
  • Be the first to comment

Making Drupal Friendli(er) for Content Editors

  1. 1. Making Drupal Friendli(er) for Content Editors Christina Dulude DrupalCamp Atlanta October 2, 2010
  2. 2. Overview <ul><li>Helpful modules and configuration </li></ul><ul><li>Things you can do in your theme </li></ul><ul><li>Tips for training and documentation </li></ul>
  3. 3. Admin module <ul><li>http://drupal.org/project/admin </li></ul><ul><li>Better UI than standard admin menu </li></ul><ul><li>Always there </li></ul><ul><li>But tucks away when not in use </li></ul><ul><li>Can be used with Rubik admin theme </li></ul><ul><li>Or overlaid on your own </li></ul>
  4. 4. Admin module with Rubik
  5. 5. Admin Menu <ul><li>Helpful for developers </li></ul><ul><li>http://drupal.org/project/admin_menu </li></ul>
  6. 6. Vertical Tabs module
  7. 7. Vertical Tabs module <ul><li>http://drupal.org/project/vertical_tabs </li></ul><ul><li>Node forms, content type forms, blocks </li></ul><ul><li>Shortens page </li></ul><ul><li>Limits information overload </li></ul><ul><li>Part of D7 core </li></ul>
  8. 8. Pathauto module <ul><li>http://drupal.org/project/pathauto </li></ul><ul><li>Automatically creates aliased URLs </li></ul><ul><li>“ /node/63” vs. “/about” </li></ul><ul><li>Nodes, users, taxonomy term archives </li></ul><ul><li>But can be overridden </li></ul>
  9. 9. RealName module <ul><li>http://drupal.org/project/realname </li></ul><ul><li>Displays name from profile fields instead of username throughout site </li></ul><ul><ul><li>(most of the time) </li></ul></ul><ul><li>More intuitive for site visitors *and* admins </li></ul>
  10. 10. Editing in place <ul><li>Don’t make users go to content listing, blocks listing, views listing </li></ul><ul><li>Unless they absolutely have to </li></ul>
  11. 11. Editing in place <ul><li>Zen base theme </li></ul><ul><li>Links to edit views and blocks on hover </li></ul><ul><li>Only if logged in and have access </li></ul>
  12. 12. Editing in place <ul><li>Views </li></ul><ul><li>Node: Edit link </li></ul><ul><li>Under “Fields” </li></ul><ul><li>Link to edit view </li></ul><ul><li>Only when user is logged in and has access </li></ul>
  13. 13. Editing in place <ul><li>You can do this in your theme, too. </li></ul><ul><li>Create a block template, and include this snippet: </li></ul>
  14. 14. Editing in place <?php if (user_access('administer blocks')) :?> <div class=&quot;edit&quot;> <?php print l('[edit]', 'admin/build/block/configure/'. $block->module.'/'.$block->delta, array('query' => drupal_get_destination())); ?> </div> <?php endif; ?> http://drupal.org/node/240044#comment-1991312
  15. 15. Zen’s Preprocess Function <ul><li>Use Zen’s preprocess function for Edit links in your non-Zen theme </li></ul><ul><li>Zen’s template.php </li></ul><ul><ul><li>Find function zen_preprocess_block(&$vars, $hook) </li></ul></ul><ul><ul><li>template.block-editing.inc </li></ul></ul><ul><li>Put these in your own theme </li></ul>
  16. 16. WYSIWYG… for real <ul><li>Set your WYSIWYG editor to read CSS of your theme </li></ul><ul><li>Rather than WYSIWYG default styles </li></ul><ul><li>Under admin/settings </li></ul><ul><li>Create your own styles, beyond H1, H2 </li></ul>
  17. 17. IMCE <ul><li>File browser </li></ul><ul><li>http://drupal.org/project/imce </li></ul><ul><li>IMCE Mkdir </li></ul><ul><li>http://drupal.org/project/imce_mkdir </li></ul>
  18. 18. Permissions <ul><li>Grant only on an as-needed basis </li></ul><ul><li>Give new users low level permissions with limited functionality </li></ul><ul><li>Add more functionality later as user becomes more familiar </li></ul>
  19. 19. Use descriptions <ul><li>For content types, fields, views </li></ul><ul><li>Wherever there is an opportunity for contextual help, use it </li></ul>
  20. 20. Training <ul><li>Don’t just train users on Drupal generally </li></ul><ul><li>Train them on their specific site </li></ul><ul><li>Keep in mind skill level, previous experience with Drupal </li></ul><ul><li>Start small, more on demand </li></ul>
  21. 21. Documentation <ul><li>Instructions for their specific site </li></ul><ul><li>“ Quick start” instructions to begin </li></ul><ul><li>More detailed instructions later when they’ve gotten their feet wet </li></ul>
  22. 22. “… And you have my undying gratitude for how EASY this is to use and maintain.” <ul><ul><li>-- Another satisfied customer </li></ul></ul>
  23. 23. Thank you <ul><li>Christina Dulude </li></ul><ul><li>[email_address] </li></ul><ul><li>@cdulude </li></ul>

×