[calebhailey]

Thanks for this feedback!

I agree with your analysis re: good/better/best approaches – or more like unacceptable/acceptable/good – and I shipped a website in the unacceptable state.

Let me see if I can fix that today.

I personally prefer the Safari browser, and I use an extension (Noir) for forcing dark mode. So where you rely Chromium's "force dark mode", Noir detects if a website has a built-in dark mode available and uses that, otherwise it just applies its own dark mode. This has been working well on hypertemplates.net, and that was acceptable during my documentation sprint over these past few weeks, but I'd rather not leave my visitors UX up individual browser configurations (via extensions or chrome flags).

[atmanactive]

Thank you for understanding.

I don't use extensions as I don't trust them.

I use about 10 different browsers on my desktop and about 5 different browsers on my mobile, and, on both platforms only one of those browsers is set with the force-dark-mode, and that one is set as the default browser. Like a decontamination chamber of sorts. All interesting and well behaved sites continue on to other browsers, some even find their permanent place. Sites that do not cooperate with force-dark-mode are extremely rare, and if they happen to be of utmost importance then I can enable a desktop utility which inverts the colors for the whole screen, but this happens maybe two or three times a year.

Thanks.

[calebhailey]

I deployed an initial implementation of dark mode earlier this afternoon. It should respect the system dark mode toggle without requiring a page reload. I'm not a designer so it took me longer to tweak/choose colors than actually implement support for prefers-color-scheme. I hope this helps!