+ All Categories
Home > Technology > Making Drupal Friendli(er) for Content Editors

Making Drupal Friendli(er) for Content Editors

Date post: 15-Jan-2015
Category:
Upload: christina-dulude
View: 1,311 times
Download: 1 times
Share this document with a friend
Description:
Presentation at DrupalCamp Atlanta and DrupalCamp Boone.
Popular Tags:
23
Making Drupal Friendli(er) for Content Editors Christina Dulude DrupalCamp Atlanta October 2, 2010
Transcript
Page 1: Making Drupal Friendli(er) for Content Editors

Making Drupal Friendli(er) for Content Editors

Christina Dulude

DrupalCamp Atlanta

October 2, 2010

Page 2: Making Drupal Friendli(er) for Content Editors

Overview

• Helpful modules and configuration

• Things you can do in your theme

• Tips for training and documentation

Page 3: Making Drupal Friendli(er) for Content Editors

Admin module

• http://drupal.org/project/admin

• Better UI than standard admin menu

• Always there

• But tucks away when not in use

• Can be used with Rubik admin theme

• Or overlaid on your own

Page 4: Making Drupal Friendli(er) for Content Editors

Admin module with Rubik

Page 5: Making Drupal Friendli(er) for Content Editors

Admin Menu

• Helpful for developers

• http://drupal.org/project/admin_menu

Page 6: Making Drupal Friendli(er) for Content Editors

Vertical Tabs module

Page 7: Making Drupal Friendli(er) for Content Editors

Vertical Tabs module

• http://drupal.org/project/vertical_tabs

• Node forms, content type forms, blocks

• Shortens page

• Limits information overload

• Part of D7 core

Page 8: Making Drupal Friendli(er) for Content Editors

Pathauto module

• http://drupal.org/project/pathauto

• Automatically creates aliased URLs

• “/node/63” vs. “/about”

• Nodes, users, taxonomy term archives

• But can be overridden

Page 9: Making Drupal Friendli(er) for Content Editors

RealName module

• http://drupal.org/project/realname

• Displays name from profile fields instead of username throughout site– (most of the time)

• More intuitive for site visitors *and* admins

Page 10: Making Drupal Friendli(er) for Content Editors

Editing in place

• Don’t make users go to content listing, blocks listing, views listing

• Unless they absolutely have to

Page 11: Making Drupal Friendli(er) for Content Editors

Editing in place

• Zen base theme• Links to edit views

and blocks on hover• Only if logged in and

have access

Page 12: Making Drupal Friendli(er) for Content Editors

Editing in place

• Views• Node: Edit link• Under “Fields”• Link to edit view• Only when user is

logged in and has access

Page 13: Making Drupal Friendli(er) for Content Editors

Editing in place

• You can do this in your theme, too.

• Create a block template, and include this snippet:

Page 14: Making Drupal Friendli(er) for Content Editors

Editing in place <?php if (user_access('administer blocks')) :?> <div class="edit"> <?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

Page 15: Making Drupal Friendli(er) for Content Editors

Zen’s Preprocess Function

• Use Zen’s preprocess function for Edit links in your non-Zen theme

• Zen’s template.php– Find function

zen_preprocess_block(&$vars, $hook)– template.block-editing.inc

• Put these in your own theme

Page 16: Making Drupal Friendli(er) for Content Editors

WYSIWYG… for real

• Set your WYSIWYG editor to read CSS of your theme

• Rather than WYSIWYG default styles

• Under admin/settings

• Create your own styles, beyond H1, H2

Page 17: Making Drupal Friendli(er) for Content Editors

IMCE

• File browser

• http://drupal.org/project/imce

• IMCE Mkdir

• http://drupal.org/project/imce_mkdir

Page 18: Making Drupal Friendli(er) for Content Editors

Permissions

• Grant only on an as-needed basis

• Give new users low level permissions with limited functionality

• Add more functionality later as user becomes more familiar

Page 19: Making Drupal Friendli(er) for Content Editors

Use descriptions

• For content types, fields, views• Wherever there is an opportunity for

contextual help, use it

Page 20: Making Drupal Friendli(er) for Content Editors

Training

• Don’t just train users on Drupal generally

• Train them on their specific site

• Keep in mind skill level, previous experience with Drupal

• Start small, more on demand

Page 21: Making Drupal Friendli(er) for Content Editors

Documentation

• Instructions for their specific site

• “Quick start” instructions to begin

• More detailed instructions later when they’ve gotten their feet wet

Page 22: Making Drupal Friendli(er) for Content Editors

“…And you have my undying gratitude for how EASY this is to use and maintain.”

-- Another satisfied customer

Page 23: Making Drupal Friendli(er) for Content Editors

Thank you

• Christina Dulude

[email protected]

• @cdulude


Recommended