Live data from Hacker News

On not choosing WordPress for the W3C redesign project

w3c.studio24.net

201–208 of 208 posts

Re: On not choosing WordPress for the W3C redesign project

#201

Hey all: we build a ton of websites in Craft and I've presented technical topics at their yearly conferences before. Happy to answer any technical or other questions about Craft here or via email, if anyone is curious to learn more. In my opinion it's a great CMS and a good choice for the W3C site. It's content author-friendly, is also very developer-friendly and supports modern development/SDLC processes. You'll be…

How's Redactor working for you? I have constant issues with it.

Re: On not choosing WordPress for the W3C redesign project

#202

What options do we have in Python world if someone wants to migrate CMS based sites built using WordPress ?

Wagtail - https://wagtail.io - is the most popular Python CMS. It runs sites for NASA, Google, Mozilla, NHS.uk. It's open source and under very active development.

Re: On not choosing WordPress for the W3C redesign project

#203
post #179

Earlier quoted context omitted.

It sure is, and fully open source. https://www.altis-dxp.com/ ( https://www.altis-dxp.com/resources/docs/getting-started/#cr... to jump straight to the download from Composer stuff; https://github.com/humanmade/altis for the repo)

This looks very useful - thanks. The pre-approved plugin list ( https://www.altis-dxp.com/resources/pre-approved-plugins/ ) returns 404 though :(

Thanks for the heads up, fixed!

Re: On not choosing WordPress for the W3C redesign project

#204
Technical director of a LAMP stack creative agency here. This write-up almost exactly mirrors our experiences across Wordpress, Drupal and Craft. I think they've made an excellent choice.

If anyone from studio24 is reading this we've developed a Craft plugin for Varnish purging etc that we're using across multiple production deployments: https://github.com/Whitespacers/Citrus

Re: On not choosing WordPress for the W3C redesign project

#205
post #203

Earlier quoted context omitted.

This looks very useful - thanks. The pre-approved plugin list ( https://www.altis-dxp.com/resources/pre-approved-plugins/ ) returns 404 though :(

Thanks for the heads up, fixed!

Hmm, why Ninja forms? I've found it loads a lot of blocking JavaScript per page.

Re: On not choosing WordPress for the W3C redesign project

#206
post #173

Earlier quoted context omitted.

Also, Statamic is free for personal use now. If you've got some time download a copy and play around with it a bit. It really is the most fun I have had building a site in years. Anecdotally I have heard that many clients prefer Statamic's and CraftCMS' editing experience over WP.

Never heard of Statamic, but that's a really cool landing page!

Thanks!

Re: On not choosing WordPress for the W3C redesign project

#207
post #193

Earlier quoted context omitted.

Those don't belong in core either. Core should focus strictly on the being a rock solid foundation. Plugins are there to supplement that. That's the beauty of the architecture. Or at least, is supposed to be. WordPress should not have the same mindset as Jetpack. Oops? Did I just say that?? ;)

WP is useless without CDN and caching.

It depends on how you're using it. It depends on the resources you have for such things. WP can and will work without them.

Re: On not choosing WordPress for the W3C redesign project

#208
post #201

Hey all: we build a ton of websites in Craft and I've presented technical topics at their yearly conferences before. Happy to answer any technical or other questions about Craft here or via email, if anyone is curious to learn more. In my opinion it's a great CMS and a good choice for the W3C site. It's content author-friendly, is also very developer-friendly and supports modern development/SDLC processes. You'll be…

How's Redactor working for you? I have constant issues with it.

It’s been good for our clients! WYSIWYG is a required feature for many of them and I’ve found Redactor better than a lot of alternatives we’ve tried. What issues do you have?

One thing that’s helped us is making heavy use of Craft’s matrix blocks. That keeps a lot of styling and inline elements out of the WYSIWYG itself. Then we can turn off a lot of the WYSIWYG buttons/features and keep it simple.

Post reply on HN