Live data from Hacker News

On not choosing WordPress for the W3C redesign project

w3c.studio24.net

31–40 of 208 posts

Re: On not choosing WordPress for the W3C redesign project

#31
post #15

The 'eat your own dog food' principle would dictate that the W3C writes their site in plain html + css. The fact that this is not even considered proves the these languages are so incredibly non ergonomic. I know.... it is an often reiterated point, but when it is the site of the W3C it really is very hard not to notice this....

IMO they are doing only HTML+CSS.

Using a generator to build the HTML+CSS from a headless CMS is exactly how a content-rich site should be build today.

That is because writing content is a different task to structuring and styling a page.

And the end result is still only HTML+CSS.

Re: On not choosing WordPress for the W3C redesign project

#33
Not a WP fan (although I've built large scale sites professionally) but the arguments regarding the frontend are kinda BS. What does Gutenberg have to do with the entire frontend layout? Gutenberg can still be used just for the main content region, not surrounding blocks. Not really a "talented" team after all.

Plus, UK dev companies tend to be biased towards Craft these days cause (guess why) it's also UK based.

I also wonder how they got Statamic in the list (probably to dilute the argument for the need for a commercial CMS) and not the 2nd largest CMS in the world (Joomla).

All in all a pointless marketing article.

Re: On not choosing WordPress for the W3C redesign project

#34
post #2

Shameful. As someone that has worked with Craft it has a ton of awful edge cases once you get deep into a project. Craft absolutely does not scale.

Not sure why you are being downvoted.

We've done two migrations from Craft for clients. WordPress isn't great, but Craft isn't a panacea either.

Re: On not choosing WordPress for the W3C redesign project

#35

Not a WP fan (although I've built large scale sites professionally) but the arguments regarding the frontend are kinda BS. What does Gutenberg have to do with the entire frontend layout? Gutenberg can still be used just for the main content region, not surrounding blocks. Not really a "talented" team after all. Plus, UK dev companies tend to be biased towards Craft these days cause (guess why) it's also UK based. I a…

I started my web development career with Joomla, around 2008. At that time it seemed somewhat convoluted -- having arbitrary levels of hierarchy to define a basic content model and redundant concepts for extending core functionality (i.e. what WordPress calls plugins and Drupal calls modules). Has Joomla managed to simplify it's architecture in the past 12-or-so years?

Also, open-source CMSs are lacking for non-proprietary drag-and-drop layout builders (such as can be seen in Wix). Does Joomla have core or a fully open-source extension for drag-and-drop page building?

Re: On not choosing WordPress for the W3C redesign project

#36

Not a WP fan (although I've built large scale sites professionally) but the arguments regarding the frontend are kinda BS. What does Gutenberg have to do with the entire frontend layout? Gutenberg can still be used just for the main content region, not surrounding blocks. Not really a "talented" team after all. Plus, UK dev companies tend to be biased towards Craft these days cause (guess why) it's also UK based. I a…

Just to correct one of your points: Craft was created by Pixel & Tonic who are a US company, not UK based.

Re: On not choosing WordPress for the W3C redesign project

#37
post #29

Never mind - their contributing.md document makes clear it isn't a FOSS project. --------------- I wasn't familiar with Craft. Looking at it they seem to have their own license and it seems pretty restrictive. Can anyone point to any existing discussions about the implications of the license and if it is truly open source? I understand FOSS projects that have some kind of payment option, but I don't understand how th…

> Never mind - their contributing.md document makes clear it isn't a FOSS project. Where did you end up finding this information? How did you not see the "pricing" link in the navigation at their website? Or did you not look at their website? If you're having to pay for the software, then you probably don't need to dig much further to see that it's not FOSS. You seem to be making this more complicated than it actuall…

I'm not sure it's so cut and dry. We tend to reduce things down to binary thinking, perhaps by training.

There do exist several prominent FOSS projects that also have pricing pages. They usually charge for hosted/managed deployments of their project or binary distributions (e.g. compile it yourself for free). While I believe it poses a conflict-of-interest, there are also a number of FOSS projects with pricing pages for "enterprise" features.

Re: On not choosing WordPress for the W3C redesign project

#38
post #27

> The use of React complicates front-end build. We have very talented front-end developers, however, they are not React experts - nor should they need to be. > I believe front-end should be built as standards-compliant HTML/CSS with JavaScript used to enrich functionality where necessary and appropriate. This is what worries me about React (and with other front end frameworks in general). I'm writing this as someone…

I use Wordpress extensively and I find the whole Gutenberg switch to be absolutely atrocious. From the design to the technical implementation. And it is also received as such. The classic editor has been downloaded millions of times. What worries me most is that the developers haven’t responded one bit to these issues (if I read the relevant issues) and it solves no problems. It feels a lot like the technology du jou…

I have a self-hosted blog with Wordpress and the change from classic editor to Gutenberg was like re-educating yourself to writing with your weak hand. Yuck.

In the meantime, I got used to it, because I did not want to fight the development direction that was seemingly set in stone. And, to be just, Gutenberg got better. Nowadays you can pull most things off in it without thinking twice.

But once you start horsing around with something untypical in mind, woe is you.

Re: On not choosing WordPress for the W3C redesign project

#39
post #28
post #8

Is 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)…

How can you comment so negatively on WP when you know so little about it?

Because I've had to install it, maintain it, and produce contents for it, and never enjoyed it.

Re: On not choosing WordPress for the W3C redesign project

#40
post #8

Is 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)…

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?
Post reply on HN