If you have to pay a little more to have someone fiddle with squarespace for twice as long as they would wordpress, that's ok because its now set and forget.
If you have to pay a little more to have someone fiddle with squarespace for twice as long as they would wordpress, that's ok because its now set and forget.
Also agree with GP that gutenberg has been ruining WP since it was shoved into core, for many reasons.
If the classic-press fork of WP is still a thing it'd be better for most people.
Glad to see they are working with a performance team now.
Currently I find it best use one of the wordpress-to-static plugins to have a design spit out into static html and use that. (which then you can zip/archive and delete all the php / gutenberg / logins etc) It's safer and faster.
of course you would lose comments and easy client updates going static, and may need a contact form chunk of code to add after the fact in some cases - but it's my current suggestion.
I don't understand your certs expiring, etc comment. That is because of your host if anything, and even the worst host now offer with Cloudflare or Let's Encrypt.
I've never heard of Wordpress eating up disk space due to a log file, sounds fairly made up tbh. I've had a log file eat up disk space from a poorly built custom CMS though, because it presented so many errors in the Apache logs. Hosts now maintain and update the Linux/Windows distros fairly regularly, and even when I ran dev/web ops you could automate this type of thing easily.