Your SlideShare is downloading. ×
0
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Therapy for your CMS: Improving the User Experience
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Therapy for your CMS: Improving the User Experience

1,928

Published on

In web design, much of user experience design is focused on the needs and expectations of end-users. However, when developing within an open-source content management system (CMS), it becomes …

In web design, much of user experience design is focused on the needs and expectations of end-users. However, when developing within an open-source content management system (CMS), it becomes essential to also consider those who will be using the CMS.At the University of Houston Libraries, the Web Services department learned how essential it is to balance usability and functionality when developing a CMS after they really started using and getting feedback on their over-engineered intranet implementation in Drupal.This talk will include lessons learned from our initial mistakes, but focus primarily on the challenges and successes of the CMS built for the Libraries’ website and the methods we used for engaging users to help determine the initial direction for the development of the CMS. Attendees will leave with ideas on how to simultaneously provide flexibility and advanced tools to improve the user experience and apply “therapy” to their own CMS implementations. Background article: Improving the Drupal User Experience, http://journal.code4lib.org/articles/4578

Published in: Education
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total Views
1,928
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
1
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Therapy for your CMS:Improving the User Experience<br />Rachel Vacek<br />University of Houston Libraries<br />J. Boye Conference<br />Philadelphia <br />May 4, 2011<br />
  • 2. About the University of Houston<br />Established 1927<br />3rd largest university in Texas<br />12 colleges, 320 degree programs<br />38k FTE<br />Carnegie-designated Tier One public research university<br />Located in Houston, TX<br />
  • 3. About the UH Libraries<br />Member of Association of Research Libraries<br />201 library staff<br />Multiple libraries on campus<br />Multiple CMSs<br />50+ content editors on intranet<br />30+ content editors on main website<br />Varied familiarity with technology<br />
  • 4. OLD Intranet<br />
  • 5. Intranet Redesign - 2008<br />Chose Drupal<br />Powerful<br />Modular<br />Flexible<br />Active user community<br />Peer institutions using Drupal<br />
  • 6. Planning & Development<br />Had clear goals<br />Conducted surveys<br />Utilized focus groups<br />Added needed functionality<br />Built what users wanted<br />
  • 7.
  • 8. It improved communication throughout the Libraries.<br />Users could collect data via webforms.<br />It was visually more appealing.<br />Many processes and workflows were automated.<br />There was much more info about departments and committees.<br />
  • 9. But issues began to surface<br />
  • 10. For example, users had to choose between 24 content types.<br />
  • 11. Some modules, such as Panels, were too confusing.<br />
  • 12. Web Services spending too much time helping people.<br />Drupal terminology was unfamiliar.<br />The search functionality was miserable.<br />The Blocks page took 3 minutes to load.<br />Too many modules!<br />Users needed ongoing training for the advanced as well as simple stuff.<br />Took too long to do simple tasks.<br />
  • 13. Web Services spending too much time helping people.<br />Drupal terminology was unfamiliar.<br />CMS UX FAIL<br />The search functionality was miserable.<br />The Blocks page took 3 minutes to load.<br />Too many modules!<br />Users needed ongoing training for the advanced as well as simple stuff.<br />Took too long to do simple tasks.<br />
  • 14. Don’t the users of a CMS deserve a good user experience too?<br />
  • 15. CMS UX Therapy<br />Do research on modules FIRST<br />Pay attention to your peers<br />Follow the “use only what you need” philosophy<br />Find balance between usability and functionality<br />Don’t give users toomany options<br />
  • 16. CMS UX Therapy<br />“Remove” the extraneous stuff<br />Create templates for multiple page layouts<br />Create roles for basic users as well as advanced users<br />Documentation<br />How certain tools work<br />Reasoning for choices<br />Create and embed self-help within CMS<br />Use Google Analytics on your Intranet<br />
  • 17.
  • 18. CMS UX Therapy<br />An investment in CMS simplification and respect for the user experience can yield an extremely powerful system run by satisfied, happy users.<br />
  • 19. Main Website Redesign – 2010<br />Applied lessons learned from Intranet CMS failure<br />Created help video tutorials<br />Picked more appropriate modules to help with creating a good UX<br />Admin module<br />Content locking module<br />Workflow module<br />Pathauto module<br />Custom modules<br />WYSIWYG editor<br />
  • 20. Main Website Redesign – 2010<br />Conducted continuous usability testing with content editors on the new CMS during development<br />Today, content editors are more eager to use the CMS and are more interested in keeping their content current<br />
  • 21. For example, we limited content types to six.<br />
  • 22. Editing pages is now simpler, and extraneous fields are hidden.<br />
  • 23. We also buit custom tools to make it easy for content editors to maintain their resources.<br />
  • 24. Whether developing a website or a CMS, always consider the user experience!<br />
  • 25. Thank You!<br />Email: vacekrae@gmail.com<br />Twitter: @vacekrae<br />Presentation available: http://slideshare.net/vacekrae<br />Background article: Improving the Drupal User Experience, http://journal.code4lib.org/articles/4578<br />

×