Ah this topic is perfect.
When I started using Wordpress 9 for my blog years ago, it was a lightweight CMS. By the time version 4 came along in 2014 it was getting bloated. TinyMCE has become “heavy-handed” and insists on rewriting your code - I don’t understand why it can’t respect the code that it is given? WP is so bloated now that I had to remove the wp_head() function entirely.
With the switch to CP I’ve also decided to “white-label” the wp_login page. It still loads the original stylesheet, which means it can render with that first before the secondary style-sheet loads. But I shouldn’t need to use functions.php to edit the public-facing login page, there should be some easy simple options from the dashboard to at the very least white-label the login page, perhaps also it should be supported to use one supplied in the theme folder too. If CP is to be “business focused” this should be a logical option - even if the default page will be CP-branded.
What is mentioned by @LinasSimonis in the other thread is true:
I don’t understand the long-term goals and the name “ClassicPress” is misleading, or rather it doesn’t convey the CMS’s primary purpose. Which is OK because it will need time to find its own identity. However this page to me leaves out the meaty problems with Wordpress at present. Which leads me to my last annoyance (well last for this post anyway)…
Security.
The idea that people should use, or be directed to use, “security plugins” is utterly absurd to me. For some people in specific circumstances, perhaps there is a reason, but 99% of people do not need a security plugin if they know the basics of what they’re doing. Which means that Wordpress has been failing in delivering a simple step-by-step guide for setting up a secure Wordpress website. I’ll put this in greater detail separately as a suggestion so it can be properly discussed.