Differences

This shows you the differences between two versions of the page.

--- development:architecture:user_interface [2017/08/02 17:59] – [Mix-ins] demiankatz
+++ development:architecture:user_interface [2018/12/19 14:00] – [User Interface Customization] demiankatz
@@ Line 1: / Line 1: @@
 ====== User Interface Customization ======
-// This page refers to VuFind 2.x and later; for 1.x documentation, see [[legacy:vufind_1.x_developer_manual:user_interface_customization|User Interface Customization (VuFind 1.x)]]. //
+:!: // This page refers to VuFind 2.x and later; use of earlier versions is no longer recommended. //
 VuFind uses a theme system to isolate the user interface from the business logic, and to make it easy to customize the software's look and feel. You can use one of VuFind's built-in themes, or you can design your own. This page provides guidance and background information to help you make the most of VuFind themes.
@@ Line 94: / Line 94: @@
 The average VuFind user will probably not have much need to use mix-ins; however, this feature is useful for sharing functionality between VuFind instances. By creating a Zend Framework module full of custom code and a theme mix-in containing custom templates and assets, it should be possible to isolate entire custom features and share them between institutions without having to significantly change core VuFind code.
+==== Mix-Ins and Inheritance ====
+Note that when you load a mix-in into a custom theme, the custom theme's templates and other files take precedence over the mix-in's. This allows you to load and customize a mix-in. However, it means that you cannot load a mix-in into an existing theme and overwrite that theme's behavior. The expected way of using mix-ins is to create a new custom child theme that extends an existing core theme, adds mix-ins to it, and then locally customizes those mix-ins as needed.
 ===== Icon Libraries =====