Earlier quoted context omitted.
Because I've had to install it, maintain it, and produce contents for it, and never enjoyed it.
And you had to ask if it's still written in PHP?
On not choosing WordPress for the W3C redesign project
51–60 of 208 posts
Re: On not choosing WordPress for the W3C redesign project
#52Not choosing and inaccessible platform was the right thing to do. Hopefully this will make Automattic reconsider their priorities regarding web accessibility. Related write-up: https://adrianroselli.com/2020/09/gutenberg-accessibility-co...
I can read it, but it's not pleasant at all.
Re: On not choosing WordPress for the W3C redesign project
#53Re: On not choosing WordPress for the W3C redesign project
#54Earlier quoted context omitted.
These are most of the time not the good questions. Can WordPress be deployed by anybody ? Yes, there's a ton of PHP hosting providers and they all have a one-click install WordPress button. Does WordPress enable authors and owners to update their website content and the design with a WYSIWYG interface ? Yes and yes (see divi, beaver, etc.).
Is that a good fit for w3c against all the other choices?
Please stop, it's going nowhere.
Re: On not choosing WordPress for the W3C redesign project
#55Not choosing and inaccessible platform was the right thing to do. Hopefully this will make Automattic reconsider their priorities regarding web accessibility. Related write-up: https://adrianroselli.com/2020/09/gutenberg-accessibility-co...
Ironic that the link looks kinda... terrible. I can read it, but it's not pleasant at all.
Re: On not choosing WordPress for the W3C redesign project
#56Earlier quoted context omitted.
I don't see how the w3c establishing a rule set would mean they would code it by hand, can you provide more details as to why the should, and not use a CMS that produces compliant code?
Because they edited and published the HTML spec with lots of examples portraying HTML as an authoring language. If W3C actually does intend to publish further HTML specs based on WHATWG (which they haven't done since 2017), they should consider injecting their own navi/styles into the bikeshed-generated WHATWG material as part of their CMS setup (and they have tons of static HTML anyway).
Regardless, to define a language it only makes sense to author the specification from the language perspective. From what I've read, and honestly it's been many years since I have read their stuff, most of the authoring docs have a section in them talking about applications and editors creating the documents.
I don't know, seems consistent to me?
Re: On not choosing WordPress for the W3C redesign project
#57Glad they realized the issues of Wordpress but a shame they went with proprietary nonsense with a faux license. A php based platform has a lot of negatives for scalability. Using a cms to generate static content is much more simple, scalable and cheaper. Keep it simple.
WP is php, and it tends to take a ton of plugins of various quality, vendors and support to get it to where you want it. Last I looked at it, it didn’t even support multi-language out of the box.
Re: On not choosing WordPress for the W3C redesign project
#58Is wp still php? What if you want a cdn outcome which doesn't drive to an sql backend? I've yet to experience wp consciously without it making me wince. I know a lot of former print press is using it, so the for profit sector likes it. That does not axiomatically make it best of breed. Being php is also not axiomatically worst of breed. The questions are decoupled really. 1) is wp still php 2) is wp best of breed. 3)…
You might be surprised to hear that likely a third of the websites you visit run WordPress. [0] So it’s not really constrained to just former print, it’s basically any site that needs to have a lot of content.
I think it can be argued that WordPress is the best CMS out there because you can really make it do just about anything you need if you know PHP. (And the built in extendability systems are pretty powerful.) It’s powerful, fast, flexible, etc.
The real problem with WordPress for most users is that it’s difficult to set up a nice site unless you either have a perfect theme or you take the time to figure everything out.
This is why Gutenberg is so important for WordPress: it’s basically reimagining the site in terms of “blocks” so that we can eventually have a unified editing experience for all parts of the site. Instead of digging through a ton of different settings and customizer and appearance pages, it’ll mostly be in a unified UI. So making that powerful and easy to use is a big project at the moment.
Re: On not choosing WordPress for the W3C redesign project
#59Huge credit to Craft team! A proprietaty product being chosen for so heavily open-source leaning project is a big win. I'm bad at analogies, but it's like a minority person took top position in a big company with strong discrimination culture in the XX century.
Re: On not choosing WordPress for the W3C redesign project
#60It's maddening to see this much latency while typing a bunch of plain text on a machine than can comfortably handle big Android Studio projects without any such latency issues. Modern web really is a dumpster fire.