{"id":2181,"date":"2010-06-15T06:00:19","date_gmt":"2010-06-14T22:00:19","guid":{"rendered":"https:\/\/librariansmatter.com\/blog\/?p=2181"},"modified":"2010-06-15T06:00:19","modified_gmt":"2010-06-14T22:00:19","slug":"using-wordpress-3-0-for-a-library-website","status":"publish","type":"post","link":"https:\/\/librariansmatter.com\/blog\/2010\/06\/15\/using-wordpress-3-0-for-a-library-website\/","title":{"rendered":"Using WordPress 3.0 for a library website"},"content":{"rendered":"

Our new library building<\/a> requires a newly branded website, with room for information about the sustainability features. Our problem? The current simple and elegant site created by a design firm is a little too simple (no site searchbox, no social features) and if we want to make some pretty fundamental changes (like remove a menu item) the firm charges us each time.<\/p>\n

\"\"<\/a><\/p>\n

The solution? Create our own site using self-hosted WordPress, which long ago stopped being just an excellent blogging platform and now counts as a Content Management System. This is Part One, where we transfer the current site structure and content over to WordPress and have something ready for opening day in the new building. Part Two will be in eight or so months, where we totally restructure the site, re-examine the content and possibly switch over to Drupal.<\/p>\n

Our main motivation for using WordPress is to create a site that, once it is set up, is easy to add to and change – with the skills of a regular librarian and the budget of a regular library.<\/p>\n

I am busy in the next two weeks working full time on the project.<\/p>\n

I am going to use WordPress 3.0 which is due for release today<\/a>. Kind of risky, but this is the release where single-site WordPress and Multi-site WordPressMU become a single entitity. Just one brand of WordPress. No more “does this great plugin work with WordPress MU? or “Oh, I wish I could create more blogs on this URL”.<\/p>\n

There are other advantages. I’ve installed an early release candidate of 3.0 and today I have been playing around with the new option to create custom taxonomies and custom menus. . (There is also an option to\u00a0 expand beyond pages and posts to add new content types – like “book”\u00a0 or “podcast” or “cat photo”, but I won’t go into that here)<\/p>\n

To match the current structure of the old site,\u00a0 I have set up my pages with a simple parent\/child structure. This lets me have six main dropdown menu options, with child pages underneath. But, there is another way that I want to facet my pages.<\/p>\n

I also want a drop-down menu of “How Do I?” questions like How Do I “join the library” or “use the free wifi”. These will point to the pages, but I cannot use categories for this, as they are only allowed for posts. The solution is to create a new heirarchical taxonomy<\/a> (that I called HowTo) and associate it with the content type, page. This means that:<\/p>\n