The ones I highlighted. (the first two are implemented in terms of custom CSS, no?)
Btw: (me, 2019-10-19)
I’d oppose allowing sites to customize the codebase. That’ll create a maintenance hell at some point. I think we could allow
- custom css
- custom js
- enabling some of a set of extra features that are available for all sites (e.g. MathJax)
This is what I meant by “Commits to individual site branches should be reserved to customizations”, with the exception of “custom js” and “enabling extra features such as mathjax”. Or, in other words: Custom CSS only.
Other features can be implemented in core and enabled/disabled as a config
These are the only considerations we must have clear from day one, in my opinion.
And by that I mean, our architecture will support it, not that we’ll be writing different custom CSS for a dozen websites from the beginning. (obviously.)