It would be great if we could have a dark mode for the staff interface. While in the OPAC we can assume that libraries have done heavy customizations to the color scheme, this might be easier, assuming that most libraries stick to our standard design/color scheme.
Created attachment 175028 [details] Example of what it would look like
(In reply to Katrin Fischer from comment #0) > While in the OPAC we can assume that libraries have done heavy > customizations to the color scheme, this might be easier, assuming that most > libraries stick to our standard design/color scheme. That's a good point! Most of my libraries don't style their staff interfaces, and the ones that do only do to a minor degree.
I wonder if it makes sense to think of this as kind of backend theme pairs. This might allow for easily adopting existing pairs for light/dark. Blue sky thinking: usually I feel bright white pages with black text have way to much contrast for long working hours, and I got rid of this stuff it on my desktop almost everywhere - except web pages... OTOH black pages with white text have a similar issue, and are IMHO even harder to read, so dark dark is probably not ideal either and just "inverting" never worked well to my experience. I usually prefer Solarized (https://ethanschoonover.com/solarized/) which comes in a light and dark shade. One does not have to like the "off" colours, but IMHO it's a light/dark mode "done right". Selenized, Gruvbox or Monokai go in this direction as well. BTW: while I _have to_ stick to CD for the outside world, I'd be quite free for something internal. Maybe that's a reason why the staff interface does not get that much effort in theming. (I also like to see immediately: it's green this is STAFF, its bright white blue, this is OPAC.)
Bootstrap has a built in color modes/themes option now https://getbootstrap.com/docs/5.3/customize/color-modes/ It doesn't have a built in theme picker, but they do share some java script they use for the documentation. I see that the dark mode on their documentation/the built in is really nice. I'm not sure if it's one of the color palettes Alexander shared, but it's definitely a similar idea. It would also be easy to force light mode in printing We could potentially add a default dark theme and the switcher to the staff interface. It also documents how to add additional ones, which we could do if we wanted or if down the line we wanted to make a way for folks to add custom ones it could be an option. I'd love to be able to do this, especially since it has an option to follow the browser setting and do it automatically.
I did some tinkering with this last week. The color modes option is really only relevant for Bootstrap components, so whether or not we use those modes, a lot of custom CSS will have to be written. I'm not saying that to discourage anyone, but to say that we don't necessarily need to figure out the Bootstrap way of doing things.
(In reply to Owen Leonard from comment #5) > I did some tinkering with this last week. The color modes option is really > only relevant for Bootstrap components, so whether or not we use those > modes, a lot of custom CSS will have to be written. I'm not saying that to > discourage anyone, but to say that we don't necessarily need to figure out > the Bootstrap way of doing things. On a different project, I've been converting a site from jQueryUI to Bootstrap 5, and I hear what you're saying here. We don't use Bootstrap components everywhere, and even if we did, we still customize the CSS beyond the default themes. (I've been working on figuring out how to take advantage of Bootstrap defaults while providing a minimal amount of custom styling on my other project. I'm loving using the CSS variables.)
(In reply to David Cook from comment #2) > (In reply to Katrin Fischer from comment #0) > > While in the OPAC we can assume that libraries have done heavy > > customizations to the color scheme, this might be easier, assuming that most > > libraries stick to our standard design/color scheme. > > That's a good point! Most of my libraries don't style their staff > interfaces, and the ones that do only do to a minor degree. This was an assumption that is causing me a headache right now.
While I don't know how to do it and what is involved (and there is a lot of discussion on the internet about how and why), maybe we make sure Koha respects a person's system-wide choices, instead of more code to maintain (if that is possible). Whatever choice is made, please please make it optional and not turned on by default - I personally find dark mode websites VERY hard to read (I actively dislike them, and will only read if I really really have to, and have no other choice). I realise this is the opposite to others preferences 8-) It is also sometimes "sold" as an accessibility solution, which it can be in some situations. But more often than not, it is a matter of personal preference. Some links and articles that provide a (hopefully) balanced view: - Nielsen Norman Group article: Dark Mode: How Users Think About It and Issues to Avoid (2023) https://www.nngroup.com/articles/dark-mode-users-issues/ - Dark mode & accessibility myth (2024) https://stephaniewalter.design/blog/dark-mode-accessibility-myth-debunked/
(In reply to David Nind from comment #8) > While I don't know how to do it and what is involved (and there is a lot of > discussion on the internet about how and why), maybe we make sure Koha > respects a person's system-wide choices, instead of more code to maintain > (if that is possible). > > Whatever choice is made, please please make it optional and not turned on by > default - I personally find dark mode websites VERY hard to read (I actively > dislike them, and will only read if I really really have to, and have no > other choice). > > I realise this is the opposite to others preferences 8-) > > It is also sometimes "sold" as an accessibility solution, which it can be in > some situations. > > But more often than not, it is a matter of personal preference. > > Some links and articles that provide a (hopefully) balanced view: > - Nielsen Norman Group article: Dark Mode: How Users Think About It and > Issues to Avoid (2023) > https://www.nngroup.com/articles/dark-mode-users-issues/ > - Dark mode & accessibility myth (2024) > https://stephaniewalter.design/blog/dark-mode-accessibility-myth-debunked/ Very good points and very good resources. Thank you, David!
David, you are not the only one - I know a lot of people would like to have a dark mode and that's perfectly fine and I would like for Koha to have the feature, but I am unlikely to be using it :)
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme It looks like the css prefers-color-scheme media feature can follow browser default, but having a toggle would be good so if someone wants to switch it back to the non-dark mode they can. Also I totally agree that dark mode shouldn't be the default. I think following the browser default (which can be set to follow the system) makes the most sense and always makes me happiest when I start using a new site and it just follows my settings.
(In reply to Lisette Scheer from comment #11) > https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme That's pretty cool. (In reply to Katrin Fischer from comment #0) > While in the OPAC we can assume that libraries have done heavy > customizations to the color scheme, this might be easier, assuming that most > libraries stick to our standard design/color scheme. Looking at the comments and ideas behind bug 37054, I wonder if we're assuming too much. Admittedly, I do have a few libraries that customize their staff interfaces, but then they would be styling the light mode, and if we have an option to disable the dark mode... maybe it would all work...
I was not aware of this bug. It looks like a duplicate of bug 31327, where a patch is waiting for feedback...
The other bug says "Add color scheme picker to the OPAC", but the patch was written for the staff interface it seems (i just tested in a sandbox, the staff interface is partially black). So i'm a little confused
(In reply to Christian Stelzenmüller from comment #14) > The other bug says "Add color scheme picker to the OPAC", but the patch was > written for the staff interface it seems (i just tested in a sandbox, the > staff interface is partially black). So i'm a little confused Both discussion and identical: we want a dark-theme. No matter the interface, we need to discuss how to do and implement it. Yes the bug title is saying "OPAC", but the patch is only touching the staff interface. Yes it's confusing, sorry about that. I think the dark-them discussion should stay on a a single bug report, especially when 2 days ago we are talking here about prefers-color-scheme and the patch on the other bug used it 3 months ago... Good to see the discussion moving on though!
Agreed, good to see this moving. What about we merge the bugs and make one "Implement dark mode". Alternative: start a new omnibus and attach both.