With reference to this suggestion it got me thinking that there should one day be less of a distinction between add-ons and styles.
At a more basic level, perhaps it should just be possible to assign some typically add-on exclusive stuff to styles (global options, template modifications, admin templates) or, possibly even better, there is no separate framework for add-ons vs styles and eventually there be something more global. We call them at this very site, "Resources", and perhaps that concept could carry over into the core software.
So instead of creating an add-on or creating a style, instead we create a resource. And that resource could contain a mix of what we know currently as add-ons or styles.
At a more basic level, perhaps it should just be possible to assign some typically add-on exclusive stuff to styles (global options, template modifications, admin templates) or, possibly even better, there is no separate framework for add-ons vs styles and eventually there be something more global. We call them at this very site, "Resources", and perhaps that concept could carry over into the core software.
So instead of creating an add-on or creating a style, instead we create a resource. And that resource could contain a mix of what we know currently as add-ons or styles.
Upvote
4