User tests: Successful: Unsuccessful:
Cassiopeia ships with two color themes, - standard and alternate. And of course if you edit those you will lose the edits on upgrade. This pull request adds the ability to add as many additional color themes as you wish.
create a least one additional color theme in the folder
media\site\templates\cassiopeia\css\global with a name of
In the template style options for cassiopeia only two color themes are available
Original options are available plus any themes you have created.
|Front End Templates (site)
|Ready to Commit
@brianteeman if child templates are finally part of 4.1 users don't need to create new files, they can create a child and override the existing 2 files.
Also a more generic comment, the approach of customising the template through a SCSS file with contents only the CSS Vars is completely wrong. Why (you might ask)? Well, the process is way more involved than it should be (a form with some colour pickers) but my problem is that it was the wrong call. Bootstrap steadily is converting everything to use CSS Vars and guess what? Once that process is complete you don't need anything more than a form to specify any variable and thus achieve truly customization that anyone can do (no HTML/CSS/SCSS or whatever, pick colours/etc VISUALLY)
Do I like the contents of this file and the methodology- absolutely not - but thats my personal opinion and I am not a designer.
Creating a child template just so you can change these colours is massive overkill. This is a super simple, fully backwards compatible, no effort means to do it. (It has to be or I wouldnt have been able to create it)
I'm in favour of having this addition (beside child templates), but (sorry Brian it's then on your shoulders) I would like to merge the child template PR first when they're done and then update the paths in this PR.
obviously the answer is no.
Then we need an option "none" - the standard is the default colour and why would I load a seperate file if the seperate file does not introduce anything new?
Ok,... then hopefully a PR got accepted where the default colours go into the default file, I do not see any sense in loading a separate file with only 3 definitions when it could be in the main file, thats a waste of performance IMHO - the seperate themes can override the default easily
|Ready to Commit
|Fixed in Code Base