Thanks for sharing this -- it looks like a good start. One question, though -- how are you setting up your institutional themes? This document suggests that they are all copies
of the blueprint theme (or at least that they include copies of the full blueprint theme's styles.css). If that's the case, this could become a maintenance headache for you when upgrading, since it will become difficult to incorporate changes to the base
blueprint theme into your institutional themes whenever you upgrade (basically requiring a three-way merge).
Would it be better if all of your institutional themes simply extended blueprint (using the extends option in theme.ini) and added a local CSS file (local_styles.css) which could be used to override some of the settings in styles.css? This could make your
quick start even easier -- local_styles.css would only include the things that users are most likely to change, so they wouldn't have to search as far in the main styles.css -- and it would greatly simplify upgrades, since the base theme would change and you
would only need to worry about checking backward-compatibility for files that you added or overrode in the extended theme.
From: Mosior, Benjamin [BEMosior@ship.edu]
Sent: Thursday, October 11, 2012 3:32 PM
Subject: [VuFind-Tech] VuFind 2 Theming QuickStart
Shippensburg University’s Savanah Steigen has started taking a look at creating a quick-start guide for theming in VuFind 2. Our goal here is to have something to hand to the members of our consortium that will ease the initial customization
process, while those that have the time and resources can delve into the
user interface customization guide. This guide makes reference to a multi-institutional configuration, but it should still be relevant for single-instance installations. If you think it will be useful, feel free to revise for general consumption.