Downloadable slides available from http://deepblue.lib.umich.edu/handle/2027.42/97550
Drupal is a powerful yet flexible tool for managing a library web site. It has an undeserved reputation for being hard for non-programmers to use. In fact, it is easy to set up a Drupal-powered website for your library without knowing any programming languages. In this workshop, the author of "Drupal in Libraries" (ALA TechSource, 2012) will provide a brief introduction to content management software and present the basic steps needed to create a simple web site using Drupal. We will explore the basic content authoring interface for a site and see how easy it is to create content for your library's needs.
Abstract: Drupal is a powerful yet flexible tool for managing a library web site. It has an undeserved reputation for being hard for non-programmers to use. In fact, it is easy to set up a Drupal-powered website for your library without knowing any programming languages. In this workshop, the author of "Drupal in Libraries" (ALA TechSource, 2012) will provide a brief introduction to content management software and present the basic steps needed to create a simple web site using Drupal. We will explore the basic content authoring interface for a site and see how easy it is to create content for your library's needs.
Eliminate redundant interfaces - Makes creating, managing, and *using* content easier for all - Can make granularity of content harder to see - If you can do one function, you can do all - More burden on center to keep everything up; harder to delegate - Parts of your library may feel loss of control; may become data providers without the “pleasure” of maintaining the interfaceTeach one system - Everyone can be [somewhat easily] taught to use the system on the authoring side - Requires training effort. Easier/harder than Dreamweaver/raw HTML?Democratize content creation - Everyone can be an author – yay! - Everyone can be an author – uh oh. Does everyone understand how to speak with the library’s voice? - Editing/review processed may be needed; can increase bureaucracy when anyone can write, do you trust them to do so?One design (with subdesigns) for all - Gives your site an identify - Lowers user burden to understand where they are and how to get where they’re going - Your operating units may perceive a lack of autonomy - Their expertise is probably not server maintenance, graphic design – but content. Let them do that.
Well, some public libraries from a self-identified list.