Live data from Hacker News

Ask HN: Where After WordPress?

news.ycombinator.com

21–30 of 70 posts

Re: Ask HN: Where After WordPress?

#22
post #4

Recent similar Ask HNs with discussion: https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=fa... I think it'd best to just stay. I see one of two likely things happening: 1. Matt comes to his senses and formally secedes his control of the WordPress Foundation and WordPress OSS to a qualified group of people. 2. He doesn't and the project gets forked to something that gets traction and will be immediately compa…

I think there's a realistic future where Matt steps away and things go back to being okay. As we've learned, the Foundation is intrinsically integrated with himself and Automattic. And the backdoors they have into authentication and plugins and etc are deeper than we expected. Matt would basically have to sell the company and the only buyer would be... cough cough ... private equity!

> the Foundation is intrinsically integrated with himself and Automattic

Don't you think Matt could de-integrate himself[1] with and achieve proper governance[2] of the Foundation, while retaining control of Automattic? I don't see the issue, there.

1. I think having Matt as a part of a properly-governed Foundation would be best.

2. "Proper governance" meaning one person can't go apeshit and single-handedly do crazy stuff like what has been happening.

Re: Ask HN: Where After WordPress?

#23

Thanks for asking this question! I asked this a couple of weeks ago (Ask HN: What's a Good Alternative to WordPress https://news.ycombinator.com/item?id=41731867 ) and I hope people keep the discussion up. I was also hoping that Ghost would become much larger than it has.

In terms of features or users? For the latter, I hope no company can capture as large of a market as WordPress has. For the former, I wish them all the luck in the world

Re: Ask HN: Where After WordPress?

#24

Is Drupal still a thing? I have always considered Drupal to be a pretty industrial-strength system, but quite complex. One of the nice things about Drupal, is that you could customize the backend. I have always hated WP's backend.

Drupal is still a thing. It's actually really great, but it suffers from two things:

1. You need a deep knowledge of Drupal to put together something good. It's not beginner-friendly, you will build a couple clunkers before things click.

2. The mind-share is not there like it was for Drupal 7 - the devs still contributing are great, progress is being made, but if you're used to Wordpress plugins or an NPM package being available for whatever you need, Drupal can be frustrating.

Re: Ask HN: Where After WordPress?

#27
post #22

Earlier quoted context omitted.

I think there's a realistic future where Matt steps away and things go back to being okay. As we've learned, the Foundation is intrinsically integrated with himself and Automattic. And the backdoors they have into authentication and plugins and etc are deeper than we expected. Matt would basically have to sell the company and the only buyer would be... cough cough ... private equity!

> the Foundation is intrinsically integrated with himself and Automattic Don't you think Matt could de-integrate himself[1] with and achieve proper governance[2] of the Foundation, while retaining control of Automattic? I don't see the issue, there. 1. I think having Matt as a part of a properly-governed Foundation would be best. 2. "Proper governance" meaning one person can't go apeshit and single-handedly do crazy…

Again, I can only go from what I have read elsewhere in this mess (and Matt making the governance of the Foundation clear as mud doesn't help), but my understanding is that the Foundation is essentially staffed and directed by Automattic employees.

If they could hand it over to an independent board and reassign leadership duties, maybe?

Re: Ask HN: Where After WordPress?

#28
post #5

http://payloadcms.com -- I'm all in after 12 years on WP.

Payload is tight as hell, but it's tough to recommend a headless CMS as a Wordpress replacement without, you know, a "head."

now that we're built on Next.js (3.0 beta), we now use Next.js as an optional head

you can still use Payload headless of course with any frontend but out of the box you have everything you need. it's pretty nifty

Re: Ask HN: Where After WordPress?

#29
post #4

Recent similar Ask HNs with discussion: https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=fa... I think it'd best to just stay. I see one of two likely things happening: 1. Matt comes to his senses and formally secedes his control of the WordPress Foundation and WordPress OSS to a qualified group of people. 2. He doesn't and the project gets forked to something that gets traction and will be immediately compa…

Forking the code is easy, forking the infrastructure and community not so much. It would be a lot of work and with an apparently capricious founder any splinter project has a high likelihood of getting bogged down in drama. My guess is no code fork gets traction, business continues mostly as usual but the supporting service providers and dev ecosystem start moving to alternatives that have more stable governance. Eventually this means the de facto death of WP as a brand and technology.

This is all avoidable if Matt can restore confidence in WP's governance and give the community a sense of a positive vision for the future. That would probably have the side effect of being financially beneficial to Automattic and bring WPEngine into the major contributor fold.

I'm not sure how likely the good version of this is but for everyone's sake I hope WP ends up with some kind of positive resolution.

Re: Ask HN: Where After WordPress?

#30

Statamic: https://www.statamic.com

I've been using Statamic for a few months now. I've often worked with Laravel, so I tend to really like Statamic. The static content by default feature means you can skip a database altogether if you'd like. Theming and content management is a little bit more of a learning curve, but so much more powerful than something like Wordpress.

I do have one complaint. It can be remarkably difficult to learn how to use Statamic properly. The documentation is a bit lacking. I often struggle to find a solution to a blocker only to find out there's a simple solution that wasn't documented very well. I think this is one of those things that will likely improve as the community continues to grow and mature.

Post reply on HN