About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:architecture:user_interface

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
development:architecture:user_interface [2020/03/04 13:40] – [CSS Inheritance] demiankatzdevelopment:architecture:user_interface [2020/03/04 13:40] – [Why Use Mix-Ins?] demiankatz
Line 93: Line 93:
 ==== Why Use Mix-Ins? ==== ==== Why Use Mix-Ins? ====
  
-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.+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 [[development:architecture:laminas|Laminas]] 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 ==== ==== Mix-Ins and Inheritance ====
development/architecture/user_interface.txt · Last modified: 2023/11/09 19:32 by demiankatz