Some preferences are immutable, but others change (things like Site Title might change for SEO reasons, but a google analytics code is unlikely to). Spina::Setting should provide a serialised preferences object to house arbitrary preferences for both core and plugins.
Some preferences are immutable, but others change (things like Site Title might change for SEO reasons, but a google analytics code is unlikely to).
Spina::Setting
should provide a serialised preferences object to house arbitrary preferences for both core and plugins.My personal use case is a key value pairing to house things like editable email templates in https://github.com/initforthe/spina-jobs