Upgrading and extending VuFind should be easier – especially when it comes time to upgrade to a new version. If we are going to significantly overhaul the VuFind code for a 2.0 release, building a new architecture that makes extensibility cleaner and easier should be a high priority.

VuFind currently has several different types of plug-ins (authentication mechanisms, record drivers, ILS drivers, etc., etc.). The concept of theme inheritance is also somewhat related. Where they exist, these mechanisms are useful and powerful, but different mechanisms do not always work in totally consistent ways, and there is not a strong separation between local custom content/configuration and the distributed VuFind core.

Feel free to add to this section – the idea is currently to list possible solutions and evaluate advantages and disadvantages.

Since VuFind's initial release, many frameworks have appeared which simplify the construction of a web application. We should look at these and see if any would be suitable for VuFind.

Smarty templates are not as popular as they once were, though they may still serve some useful functions within the library environment. We should consider alternatives, especially if it helps make VuFind development less complex and more consistent.