I’d actually prefer to have a true dark mode, which probably won’t be coming anytime soon… (unless the team steals the dark/light mode stuff from Gwern maybe?)
Luckily, user style sheets are a thing! There’s a dark mode style sheet from 2018 on userstyles.org and thanks to its extreme simplicity, I’m happy to report that it still works on the new site design. (Unfortunately, that simplicity also means that it’s not very good… c’est la vie. Maybe I’ll make a better one when some urgent deadline approaches some day in the following months, maybe not.)
If you prefer white, setting this as your user style sheet might get you 80%-95% of the way there:
(You may want to fiddle some more with the post / comment borders, other than that I noticed no problems.)
Of course, I’m not sure how stable those names are… So here’s some actual feedback / questions on that side of the design:
Some CSS classes do seemingly unnecessary things (e.g..PostsItem2-isRead overrides the background color of the normal .PostsItem2-background but applies the exact same value, same for .Layout-main / body), which makes it potentially harder to customize. (Because !important in the user style overrides both classes it actually still works fine for PostsItem2-isRead, but .Layout-main needs an explicit extra rule and just deleting that background color override in the original CSS doesn’t seem to break anything.) Do you want a list of weird spots like that? (If yes, I’ll make a crazy style in 1-2 weeks and see what breaks when modding / what can (probably) safely go away.)
stable names for most things would be really useful, but PostsItem2 looks fairly unstable / generated? How stable will those names be?
Jim’s actually been interested in a dark mode, and better theme support in general. It’s a bit tricky because we do expect to change nontrivial bits of the site around sometimes. The actual effort for initial theme support isn’t too high, but then committing to keeping various themes working is a pain. (Different team members have different opinions on how to prioritize those issues)
PostsItem-isRead is a sort of hacky thing I added so I could experiment with changing the styling of read posts, with a superfluous style change so that JSS didn’t ignore the class. Currently, a post’s read-status only displays on it’s title, but I wanted to experiment with changing the background color, further up the component hierarchy.
PostsItem2 isn’t deliberately unstable but it’ll undergo some changes in month’s redesign.
I’d actually prefer to have a true dark mode, which probably won’t be coming anytime soon… (unless the team steals the dark/light mode stuff from Gwern maybe?)
Luckily, user style sheets are a thing! There’s a dark mode style sheet from 2018 on userstyles.org and thanks to its extreme simplicity, I’m happy to report that it still works on the new site design. (Unfortunately, that simplicity also means that it’s not very good… c’est la vie. Maybe I’ll make a better one when some urgent deadline approaches some day in the following months, maybe not.)
If you prefer white, setting this as your user style sheet might get you 80%-95% of the way there:
(You may want to fiddle some more with the post / comment borders, other than that I noticed no problems.)
Of course, I’m not sure how stable those names are… So here’s some actual feedback / questions on that side of the design:
Some CSS classes do seemingly unnecessary things (e.g.
.PostsItem2-isReadoverrides the background color of the normal.PostsItem2-backgroundbut applies the exact same value, same for.Layout-main/body), which makes it potentially harder to customize. (Because!importantin the user style overrides both classes it actually still works fine forPostsItem2-isRead, but.Layout-mainneeds an explicit extra rule and just deleting that background color override in the original CSS doesn’t seem to break anything.) Do you want a list of weird spots like that? (If yes, I’ll make a crazy style in 1-2 weeks and see what breaks when modding / what can (probably) safely go away.)stable names for most things would be really useful, but
PostsItem2looks fairly unstable / generated? How stable will those names be?Other than that, I agree with the “looks good”!
Jim’s actually been interested in a dark mode, and better theme support in general. It’s a bit tricky because we do expect to change nontrivial bits of the site around sometimes. The actual effort for initial theme support isn’t too high, but then committing to keeping various themes working is a pain. (Different team members have different opinions on how to prioritize those issues)
PostsItem-isRead is a sort of hacky thing I added so I could experiment with changing the styling of read posts, with a superfluous style change so that JSS didn’t ignore the class. Currently, a post’s read-status only displays on it’s title, but I wanted to experiment with changing the background color, further up the component hierarchy.
PostsItem2 isn’t deliberately unstable but it’ll undergo some changes in month’s redesign.