4 ms·

WordPress will continue losing market share for the simplest reason: people fed up with the coercion of Full-Site Editing (FSE) by Automattic. Community's reac

WordPress will continue losing market share for the simplest reason: people fed up with the coercion of Full-Site Editing (FSE) by Automattic. Community's reaction via comments' section [1] for Gutenberg plugin was a clear indication that people will eventually go away, had they not revoke their decision. They haven't which led to the fork [2] of WordPress thus dividing the community, at least for a while. Had they listened to their community to acquire Elementor and make it part of WP core, things would have been a lot better today than they currently are I'm afraid. They have wasted countless resources and valuable time that could be poured in improving Elementor and WordPress in general. I have tried to find tutorials, articles, and books about using FSE and couldn't find anything updated. It's just sad to be honest with you... [1] https://wordpress.org/plugins/gutenberg/ [2] https://www.classicpress.net/

pupppet 4y ago
I used to tell people WP is a solid base to build your website if you know what you're doing, but with Gutenberg and not knowing how much longer the Classic Editor plugin will be supported I keep my WP praise to myself.
- stefanos82 4y ago
  That's the spirit. Currently I'm learning Laravel, because I have dealt with a lot of WordPress custom development and had lots of headaches, especially with multilanguage support. I find it incredible it does not support such a standard feature and you are forced to buy a plugin that is actually a CMS written as a plugin...we are talking about an Inception type of thing, if you think about it with the whole CMS inside a CMS! Madness, complete madness!
- ishjoh 4y ago
  4 years ago my team built out a new CMS website for a large media company that had many different sub brands and multiple language requirements. We did a lengthy comparison against a big range or CMS solutions, we found Django CMS https://www.django-cms.org/en/ https://www.django-cms.org/en/ fulfilled all our requirements the best. After having used it for years I can say it's an excellent product. Easy to setup, easy to learn (any Django dev can pick it up almost instantly), secure, has LTS versions. It's just an excellent CMS. It's the first product I reach for now when needing a CMS system. I am not affiliated with Django CMS in any way, I just really love their product.
lutorm 4y ago
I'm running my own tiny WP server and I hate that block thing. Good to know other people are feeling the same.
kstrauser 4y ago
What’s wrong with Gutenberg? I haven’t been following along with this at all.
- stefanos82 4y ago
  They forced it down to people's throats without listening to anyone's reactions or objections. I have tried to learn how to use it and have lost counting how many times they changed how it works as a whole. You have no idea how excruciatingly painful is for me to use it that I have 22 years of professional experience with computers; imagine how non-tech savvy users feel when they try to use it! Not all people are computer literate or are interested in technology in general, what they don't understand?! Users want a tool to do their job and they want it to be stable, safe, and robust; don't change this concept or you will lose them on the spot, PERIOD! Instead of letting Gutenberg as a plugin it originally were (well, technically it still is offered as a plugin, but that's another story) - so people can choose whether to use it or not - they forced it to the community and on top of that they are working non-stop on implementing new mechanisms or ideas that cancel previous features, thus leading to a mad chaos.
- gibletsingravy 4y ago
  For the non-dev user, Gutenberg takes longer and is more fiddly to do what the old editor used to do, breaks a lot of old themes/plugins, and makes it harder and harder to use the old editor/themes/and similar. For the developer, WordPress used to be really easy to make add-ons for and customize. Now you need to know React to get the most of of WordPress, and if you're going to go through the trouble to get good with React, what are you going to do, use it to maintain WordPress sites or go get paid more to do React development? Gutenberg and the changes associated with it do make a better site — but people didn't want a better site, they wanted a better WordPress.

pupppet 4y ago

I used to tell people WP is a solid base to build your website if you know what you're doing, but with Gutenberg and not knowing how much longer the Classic Editor plugin will be supported I keep my WP praise to myself.

stefanos82 4y ago
That's the spirit. Currently I'm learning Laravel, because I have dealt with a lot of WordPress custom development and had lots of headaches, especially with multilanguage support. I find it incredible it does not support such a standard feature and you are forced to buy a plugin that is actually a CMS written as a plugin...we are talking about an Inception type of thing, if you think about it with the whole CMS inside a CMS! Madness, complete madness!
ishjoh 4y ago
4 years ago my team built out a new CMS website for a large media company that had many different sub brands and multiple language requirements. We did a lengthy comparison against a big range or CMS solutions, we found Django CMS https://www.django-cms.org/en/ https://www.django-cms.org/en/ fulfilled all our requirements the best. After having used it for years I can say it's an excellent product. Easy to setup, easy to learn (any Django dev can pick it up almost instantly), secure, has LTS versions. It's just an excellent CMS. It's the first product I reach for now when needing a CMS system. I am not affiliated with Django CMS in any way, I just really love their product.

lutorm 4y ago

I'm running my own tiny WP server and I hate that block thing. Good to know other people are feeling the same.

kstrauser 4y ago

What’s wrong with Gutenberg? I haven’t been following along with this at all.

stefanos82 4y ago
They forced it down to people's throats without listening to anyone's reactions or objections. I have tried to learn how to use it and have lost counting how many times they changed how it works as a whole. You have no idea how excruciatingly painful is for me to use it that I have 22 years of professional experience with computers; imagine how non-tech savvy users feel when they try to use it! Not all people are computer literate or are interested in technology in general, what they don't understand?! Users want a tool to do their job and they want it to be stable, safe, and robust; don't change this concept or you will lose them on the spot, PERIOD! Instead of letting Gutenberg as a plugin it originally were (well, technically it still is offered as a plugin, but that's another story) - so people can choose whether to use it or not - they forced it to the community and on top of that they are working non-stop on implementing new mechanisms or ideas that cancel previous features, thus leading to a mad chaos.
gibletsingravy 4y ago
For the non-dev user, Gutenberg takes longer and is more fiddly to do what the old editor used to do, breaks a lot of old themes/plugins, and makes it harder and harder to use the old editor/themes/and similar. For the developer, WordPress used to be really easy to make add-ons for and customize. Now you need to know React to get the most of of WordPress, and if you're going to go through the trouble to get good with React, what are you going to do, use it to maintain WordPress sites or go get paid more to do React development? Gutenberg and the changes associated with it do make a better site — but people didn't want a better site, they wanted a better WordPress.