Given DigitalOcean's recent claims about being devoted to user experience and accessibility (https://www.digitalocean.com/blog/introducing-walrus-digitaloceans-reimagined-design), I'm surprised that they still seem to be ignoring this.
Users of DO's web properties should have a choice between light and dark modes as well as support for automatically switching between them where the operating + browser support it.
At the least, macOS 10.13+ and Windows 10 support light and dark modes as well as automatic switching between them based on a schedule. Most native apps respect this preference. Modern browsers (Chrome, Safari, Firefox, Edge, Opera, etc) also support this (https://css-tricks.com/dark-modes-with-css/). Unfortunately, many websites have ignored this wonderful feature.
Some users just prefer dark mode. Some users are light sensitive, and being forced to use light-mode-only websites is actually physically uncomfortable. As an example, let's say you're light sensitive. You have macOS set to dark mode so all your native apps are dark now. You code all day in VS Code using a dark theme. You sit in a low light room all day. Now you need to go to DO's website for some reason, it's like someone turned a spotlight on in your face or like you just walked out of a movie theater on a sunny day after sitting in the dark for two hours. It is physically uncomfortable.
As part of your the new design initiative you are touting, you should make dark mode support a priority along with all the other accessibility related features you're focused on supporting.
There are obviously plenty of other offenders, but DO doesn't have to be one of them.
There are also browser plugins and some browser support for forcing dark mode, but they all create performance issues and are a poor substitute for first class support by the website author.