This document discusses setting up a new website for the MRRL library using Drupal as a content management system. It describes what a CMS is and why Drupal was chosen. It outlines the process of installing Drupal and modules, theming the site, training staff to use it, and populating it with content. Key modules used included Views, CCK, Administration Menu, Webform, Panels and Themekey. The transition was a success, resulting in a 42% increase in website visitors. Lessons learned included the need for training, flexibility, seeking opinions, and being creative with Drupal's capabilities.

1. Web Building With Drupal

2. Objectives What is a CMS? Why Drupal? Is there a learning curve? How did MRRL set up the new site? What modules were used? How did the process work? Was it a success? What lessons were learned?

3. What Is A CMS? Content Management System Database – with a fancy User Interface Separation of content and “look” Lots of ‘em for free Drupal Joomla Wordpress (lots of very expensive options, too)

4. Why Drupal? ‘Cause everybody else is doing it? http://drupalib.interoperating.info/library_sites http://drupalib.interoperating.info/node/88 Lots of library-specific modules? http://drupalib.interoperating.info/library_modules It’s free? It has a very active developer community? http://drupal.org/project/Modules

5. Is there a learning curve? Yes. Lynda.com – online training videos Drupalcon – conference with LOTS of learning opportunities Drupaltrainer.com Drupal handbook – community-created help for every part of Drupal, core to modules

6. How did MRRL set up the new site? LSTA Grant (thank you, State Library!) New server, hands-on training & graphic design Installed Drupal, set up after training Installed modules Themed the site Trained content providers Populated the content Released Nov. 17th, 2009

7. What modules were used? LOTS First – Views, CCK, Administration Menu Next – Webform, Panels, Themekey, Mail Extras – Embedded Media, Nice Menus, Tabs, Twitter, Flickr, etc…. More modules = more functionality + slower response times

8. How did the process work? Training I went to hands-on administrator training I trained content managers both in groups and one-on-one Each subject expert got a user name & password and access to their “role” Content Entered content from old site Created new features possible with Drupal Easy feed aggregation, custom front page, Decisions – blocks, pages, panels or views?

9. How did the process work? Theme Graphic designer gave me HTML/CSS I transferred that to Drupal PHP theme Used Themekey and Taxonomy to determine which pages get Main, Teen or Child themes Maintenance Weekly updates to Drupal & modules Database backups – VERY IMPORTANT Ongoing content training to staff

13. Was it a success? ABSOLUTELY 42% sustained growth in website visitors

14. What lessons were learned? No tech support – you have to find the answers yourself Seek training – there is a learning curve Be flexible – some things work, some don’t; be willing to drop stuff that doesn’t work Seek opinions – get input from staff, patrons, random folks on the street Be creative – Drupal offers a LOT of ways to do things & a lot of things to do!