Make the dark mode the default

I know it’s kind of a stupid request, since people can just change it. But the default pink theme doesn’t look all that great in my opinion. Why not make the dark mode the default? People can then still change it to the pink theme if they want to.

How did you manage to mistake pink for purple

@Anonymous #C70D  
I didn’t take a good look at it, since I immediately switched to the dark theme.

I like the pink theme, it helps me differentiate this site from other Philomena-based websites, to be honest.

@Luna  

 
Well, to each their own. I’m just glad I can switch over to the dark theme.

I don’t think the pink colour scheme is bad, but the way the theme is implemented is simply eye-searing. Please make the background dark grey, tone down on making everything different shades of purple, keep it to accent colours. Like Purple Smart said, people can just change it, but I think the default should still look pleasant on the eyes, because it’s the first thing people see when they open the site.
 
I’ve also seen suggestions for an Aryanne-inspired light theme (who is basically the free speech mascot and a big reason why this was created right now) and/or an Angel Wings theme (because Zizzy, and at least it would make sense as a pony-inspired theme, rather than this weird purple which I honestly do not see the symbolism of).

I rather like it, myself

Truth be told, there will be other themes eventually, I cranked this default out to differentiate from other Philomena based sites right away. When I say I put the old theme colors in a pallet tweaker and went ahead and changed everything , I’m still learning what does what really.
 
I haven’t set up my test site yet, but when that’s up that’s when I’ll be testing more code improvements, themes, etc. I’ve already had someone submit an AJ theme. Themes can be found here for the time being: https://github.com/ZizzyDizzyMC/philomena/tree/master/assets/css/themes

@ZizzyDizzyMC  
The reason other Philomena-based websites only have 3 themes is due to the deployment slowdown. If you have more themes, the CSS pipeline must produce more target .css files, which slows down deployments, and at some point it would become unbearable (I’m talking like, deployments taking some ridiculous time like 5 minutes).

@Luna  

 
I know the stuff that has to be edited and what not, deployment slowdowns aren’t really a concern if you’re not adding themes every day. Most would rather have some quality of life improvements vs the site not being online for an extra 5-10 minutes when new features are added. At least that’s what I’d think. Maybe I’m wrong?

@ZizzyDizzyMC  
The way workflow works on our Philomena-based sites causes us to edit parts that cause new .css files to be generated. They will need to be re-generated every time you edit any .scss or .js file, it’s just a sad truth of how our clientside asset deployment works. It’s not even that the site is offline for that duration of time, but due to how annoying it can get to wait so long for deployments and being unable to do anything else with your site in the meantime.