I think the "private website" space is shrinking - despite what adverts for Wix and Squarespace might infer.
The consumer/blog space of geocities, tripod and the like went to social media. Then we went through a period of "businesses putting up 10 pages for a fixed price" through first of all "a local web guy" then by themselves using Wix/WP/SS etc.
I've just had a bathroom fitted by a guy who functions purely on Instagram for his portfolio and Whatsapp for communication. As I'm old and curmudgeonly I wanted an email address, and when I got it, it's the one that came free with his phone.
Even local restaurants seem to be changing - using aggregators as their primary touch-point. Can't really blame them. They can easily submit their static stuff
- opening times, location and menu - and the complex stuff like a booking system, taking deposits, sending calendar reminders is just handled by a single entity who's good at this stuff.
WP seems to occupy this weird middle-ground I don't see as being attractive to anyone. As a light user there are dedicated CMS for your industry - for the hardcore, you hand-build it. WP, paying for packages, and being on the hook when they don't play nice - Who-tf is the target market?
We can make assumptions all day but for me, the worst thing about WordPress is EASILY Plugin Hell.
I can update all plugins this morning and they all want updates by the end of the day.
And then when they break it’s a disaster.
WordPress itself needs to take a chill pill too.
Leave a version out for a year or more, and only small security patches. In the last year, I think we’ve seen block widgets, JQuery migrate nightmares, that new blocks theme thing, and more. I just want them to back off already.
It’s a nightmare keeping hundreds of clients up to date.
The WordPress codebase is a disaster, and the problem is self-compounding. The founders / core have found success writing disastrous code, and as such have no impetus to be aware of the benefits of higher quality - this is largely because (as you point out) the model of development shifts the burden to small individual website makers deploying (& maintaining / firefighting) WordPress.
Since it's open-source, a disastrous codebase could be "fixed" over time if experienced engineers were willing to join and contribute to the project over time, but the culture of QA-ignorance among existing core contributors has a tendency to exasperate experienced engineers.
I'm not saying it's a "toxic" culture per se - it's very open, and especially welcoming of new / inexperienced / beginner contributors, which is certainly cool for learning. But once contributors gain a little knowledge they go one of either two ways: knowledge-stagnation (enough to contribute but not to improve), or exasperation (enough to know how to improve but lacking motivation to make that uphill battle).
The culture from core extends to the plugins, not only because there's overlap in devs, but also because the APIs the plugin community have to use are garbage. This means many of the popular plugins - while they may have high-quality UX and design - have very poor code behind that.
All the above means that WordPress needs constant small fixes contributed by an army of devs to prevent it falling over / getting hacked, which massively increases the update frequency: there's nothing preventative within it's architecture, it's all reactive patches. It also means it'll only be a viable platform as long as its extremely popular: once popularity decreases a little, the maintenance burden will be far too high for the smaller community to sustain, and existing installs are going to be even more vulnerable than ever.
I have been running a few WordPress sites for like 10 years now and never had any of them randomly break, I just use a few core plugins and two premium themes and update them once in a while.
I pay a small amount extra a month for my host to manage upgrades of my own WordPress sites and common plugins, I keep things simple on purpose to minimise the plugin hell you mention.
As much as I can do this myself, I can't guarantee timely updates as a private individual.
I've migrated 2 WP sites (one for work, one for a local club) to github pages to reduce the maintenance pain of WordPress.
Wix and Squarespace are imo infinitely harder to make look good/maintain than Wordpress (at least without Gutenburg). Just some basic tasks are needlessly difficult or impossible. I still think Wordpress is the go-to easy to build/maintain CMS.
IMO, I think Automattic introduced Gutenberg way too soon to Core and introduced it as very half baked. Still to this day it's very half baked to an incredible degree, some pages will just break outright and resort to JSON errors, not to mention the built in blocks are awful and 3rd party blocks often break. That probably turned off a lot of people. It's still easier to just buy a theme that has a built in page builder and you'll get similar Lighthouse scores to Gutenburg (this being for average users, not custom themers, etc).
The only people I know who hate Wordpress are the developers who have had the misfortune of having to manage an instance of Wordpress. All the marketing and content people I have worked with love it.
This. I have a sales person and a designer that maintain our Wordpress instance. I login to the admin panel once every few months. Mostly these people do everything by themselves.
Among the things they've done recently:
- a major web site redesign (custom styling and look)
- added translations (via a plugin)
- updated how we gather analytics
- added a hubspot integration
I don't know many platforms where that can happen without technical people getting involved. All the next best options are SAAS platforms like shopify, squarespace, hubspot, etc.
None of us have any php skills (well, I deny having them and tend to not touch it). It's not perfect. But it's there and it works. For me the main value is that it can do what it does without me needing to be involved. We spend a few days setting it up at some point and making sure it gets updates. That's it.
It's not surprising wordpress market share is declining. I'd actually recommend new companies to pick one of the SAAS options. Even with wordpress, getting somebody else to host it for you is probably wise (there are a few good companies in this space).
WordPress is stupid easy to wrangle into what you want it to. That's the best thing about it and the worst, because you have a bunch of people who have no idea what they're doing doing high-profile things. As a freelancer, WordPress paid for my house. Naysayers are just elitists without a cause.
You can add to that "people who manage web hosting servers".
Across our fleet, disabling hacked instances is a routine event. There is often a marketing person that wants to argue - according to their industry, WordPress is leading the security space. It's incredible how different industries view the product.
Wordpress code base is the best argument for the MVC design pattern specifically because it shows what goes wrong when you toss the idea of encapsulation out the window.
I've done some Wordpress consulting work in the past. I wouldn't say I hate Wordpress. I advocate for it's use in some cases! I think it is a fantastic piece of software for what it natively does.
You want a blogging platform? Wordpress is one of the best, hands down. You want a basic CMS that is so dead simple that anyone that can use a word processor can update the website? Wordpress excels at this, because that is what it was designed to do.
But I do think it is a poor solution in a lot of cases where it has been shoehorned into. People keep grafting so much extra, unnecessary crap onto what is still, at it's core, a blogging platform. Often this is done by low-skill, low-paid "consultants" with very little experience in writing maintainable, secure code. Literally all they know how to do is write Wordpress code. I would often end up having to clean up the mess from these folks, who often still write PHP like it's 2007 and they haven't learned better [0].
Wordpress's architecture has, until relatively recently, encouraged this behavior. Their stubborn refusal to move beyond PHP 5 for many years (and continuing to support absolutely ancient versions of PHP 5 at that!) held their entire ecosystem back from writing better, more secure code for a long, long time. And, more broadly, held PHP as a whole back, as they were among its largest players. It was really hard to make the case for hosts to upgrade PHP when Wordpress still supported whatever ancient version of PHP the host was providing. Their internal architecture can be very messy in places and documentation often contradictory about what the "correct" or even preferred way to do something is because there are multiple ways implemented at different times.
I will give them credit: Wordpress itself doesn't have too many gaping security holes anymore. Most of those has been patched. It's the plugins and themes that provide the attack surface now.
The public plugins themselves (and to a lesser extent the themes) are of such widely variable quality that it is difficult to know what to use and trust. You're probably okay with the "official" plugins and most of the widely-installed third party plugins, but you get too far off the beaten path, you find a lot of garbage (and, to be fair, a few gems as well). And any custom plugin I find is immediately suspect for the reasons above. Building a theme? Which of these multiple ways of user customization do you support? All of them? None of them? Or do you just write your own customization further messing up the UX for writers and editors who have little idea how to manage Wordpress beyond the very basics of writing a post.
Oftentimes when I would come into a Wordpress case, there's 30 or so plugins installed, half of which are disabled and you have no idea what is causing the client's problem. It takes a few hours just to untangle the mess, and you can't ask the last "consultant" because they wrote garbage code, threw it over the wall and disappeared. It's the reason I usually don't take Wordpress cases anymore unless it's someone I know or an installation I did, myself, from scratch that hasn't been messed with by anyone else.
Wordpress is a great blogging platform and basic CMS. It's when people start trying to make it do things beyond this that problems start to accrue. I don't hate Wordpress. I hate what people try to do with it.
When Wordpress is your hammer, everything looks like a custom post type.
I wonder how the code looks like. Back in pre PHP5 days, it was surprisingly painful to read their docs (globals and side effects) and plugins source was just shocking. Angry 17yo levels of dirt loc (and that's insulting to 17yo)
...which is sort of like saying "the only people who hate Wordpress are the people who have to use it."
It's legit AWFUL. It's a reasonable blog engine, sure, but it's been forced into being a general CMS, and it was never built for that. Our corp site is on it, and I fucking HATE it (fortunately I rarely have to deal with it).
My personal blog (21 years old and counting) has been through a bunch of platforms (Blogger, Greymatter, Blosxom) before settling on Wordpress. As I said, as a blogging tool, it's mostly fine. I don't really HATE it there, but it's still too fiddly for my tastes.
The other cohort of people who hate Wordpress are marketing/content people who've had the pleasure of using an install that lacks full-time developer maintenance for long enough for it to break, and being "stuck" with that breakage (or, worse, wading into the freelance market trying to find someone to fix it without a scratch rewrite).
The matches my experience. They can manage whatever web of crazy they want in Wordpress… if they need something from the dev side we can play with some plugins until it works.
Sometimes the answer is “oh god we can’t do that”… and that seemed to be ok if we had some alternatives
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.
Do you have the same impression: Each and every plugin/extension has a commercial pro version that keeps on nagging to buy its extended warrenty ... sorry, no, to subscribe to updates for just 29.99 each, right? So 29.99 for instagram connections, 39.99 for backups pro (i'm making names and prices up, but you know the drill.) and for just 20 dollars more a security/virus check for ... what?!?!
are you f**king kidding me?
I've started to use pelican. It creates a flat file-based website with all I need. (See: https://blog.getpelican.com/)
> If WordPress is shrinking, something else must be growing, this is, after all, a zero sum game. The very clear winners at the moment are Wix and Squarespace.
But the authors conclusion, that WP's loss gives points to Wix and SqSpace for me does not hold: The numbers for "None" still decreases and much more strongly than the two mentioned above.
He conveniently forgets the "None" partition, making is entire argument/criticism (for me) somewhat thin. He could in the same way argue, that Wix and Squarespace are more successful in getting non-CMS websites to switch.
I agree. Given the rounding (43.0 and 42.9 could theoretically just be a 0.01 difference) & measuring bias there might be no declining effect here at all.
A .4% loss in share since February, according to one website? Isn't that a little small and short-term to draw such a firm conclusion? or am I missing something significant?
Especially when, according to that same survey, it's up 1.7% since this time last year...
Is it just me, or is WP's new block-based editor (Gutenberg) easily the worst of its kind? I maintain a small blog for translations on WP, and each time I'm trying to do anything non-trivial it's a massive pain, with obvious and infuriating UI bugs and glitches. I've seriously been considering switching to self-hosted SSG, but many of the people I work with aren't all that familiar with Markdown or Git to be able to do that well enough.
Freelance developers selling WordPress to their clients (and who build custom themes and plugins) are being ignored by WP core and they are regularly broken by changes. It seems like Automatic is optimizing for Wix marketshare and abandoning some of it's key champions.
I think they could have avoided much of this by listening to these devs, having backwards compatible designs, and slowing down to produce higher quality code.
Strange to hear BC breaks are common since its architecture screams procedural and dated. Though some of that could be they still technically support PHP 5.
An alternative explanation: people who use Wordpress are those with personal blogs and they are being visited less, thus less present in top Alexa Rank sites.
There was a ramp up of new WordPress and specifically WooCommerce sites starting in late summer of 2020 and spiking huge in December 2020 & January 2021. These are people that were stuck at home due to lockdown or losing their jobs and they started online businesses. The lot of those signed up for 1 or 2 year hosting plans and those came due around Feburary/March of this year. A large amount of those businesses failed, or the owners went back to work, etc etc, and no longer need their sites.
This is a plausible explanation considering that the drop in market share is not that big. It would be interesting to compare the numbers from the past two years.
Most users of WordPress would be better served by a static site generator system. Unfortunately, it seems most of these are very much "by developers, for developers" in flavor. They're overly complicated and insufficiently developed in the front-end to be useful to most of WordPress' current target market (e.g., businesses with a need to present mostly static content, but with the ability to make changes and deploy/publish them without too much technical know-how required).
WordPress can be used as a static site generator via the Simply Statuc plugin. It needs some thought into the design ( which plugins won't work because it isn't dynamic anymore), but it's a decent way of having the UX for non-developers/other very technical folk while having the security, stability, deployability and maintainability of static hosting.
What's old is new again? Before WordPress started to eat everything, Blogger, Movable Type, and other popular publishing platforms were all static site generators. Dynamic platforms were too complicated and resource intensive for the masses.
It is shrinking because they have decided to pivot to Gutenberg. What they don't realise is that there is a major cottage industry of people developing custom themes for their clients, who use things like WooCommerce for selling. These people know how Wordpress works through the old, classic system of themes but couldn't care less about block themes.
I'd just like to interject for a moment. What you're referring to as Wordpress,
is in fact, Plugin-hell/Wordpress, or as I've recently taken to calling it, Plugins plus Wordpress.
Wordpress is not an ecommerce system unto itself, but rather another free component
of a fully functioning ecommerce system made useful by the freemium plugins, security vulnerabilities and PHP comprising a full CMS as defined by POSIX.
You have confused Operating System with Content Management System here...POSIX has nothing to do with CMS; as its name stands POSIX means "Portable Operating System Interface".
Who's still using Alexa? The quality of data is only as good as the people using the service. I haven't seen a single person who uses Alexa as a plugin or as a service in ages so I don't know how to treat this data. The only companies with a legit data would be search engines and browsers.
A friend of mine has a Wix account for who knows why. We were planning an event and he asked me to make a web page for it. I didn’t have the free cycles to do it at that moment, but he came back to me with a mostly finished Wix website a couple of hours later. I’ve gotta say, while I’m not interested in using it, I was impressed with how quickly someone less technical was able to get something decent up and running.
This isn't really a constructive or useful comment. From what I saw, designers were able to build with Squarespace most of the stuff the devs were doing in wordpress and the sites were more reliable and cost less in the long run.
Gutenberg is not a good product, and while I understand why it exists, it feels absolutely ridiculous that the WordPress team keeps charging ahead with it.
I 100% agree with you here. Clients have an awful time working with Gutenberg.
While the editor UX continues to get more convoluted, so too does the DX. PHP and React interfaces grow further apart in their capabilities and it's really just outrageous to have to master so many things to create a simple block in the editor.
The problem we have is that getting traffic to a website is expensive and difficult compared to 5-10 years ago. This is really problematic for small businesses that just want traffic for search from local visits or in a niche category. Wordpress losing market ins't surprising, hosting costs money - and the choices for WP are pay wordpress dot com or get a shared hosting account like it's 2004. Facebook pages are free. Search isn't delivering traffic. Instagram, Facebook Pages, Google My Business, etc... are all making to cost of maintaining a nice website simply not worth it.
[+] [-] goldcd|3 years ago|reply
The consumer/blog space of geocities, tripod and the like went to social media. Then we went through a period of "businesses putting up 10 pages for a fixed price" through first of all "a local web guy" then by themselves using Wix/WP/SS etc.
I've just had a bathroom fitted by a guy who functions purely on Instagram for his portfolio and Whatsapp for communication. As I'm old and curmudgeonly I wanted an email address, and when I got it, it's the one that came free with his phone.
Even local restaurants seem to be changing - using aggregators as their primary touch-point. Can't really blame them. They can easily submit their static stuff - opening times, location and menu - and the complex stuff like a booking system, taking deposits, sending calendar reminders is just handled by a single entity who's good at this stuff.
WP seems to occupy this weird middle-ground I don't see as being attractive to anyone. As a light user there are dedicated CMS for your industry - for the hardcore, you hand-build it. WP, paying for packages, and being on the hook when they don't play nice - Who-tf is the target market?
[+] [-] dpcan|3 years ago|reply
I can update all plugins this morning and they all want updates by the end of the day.
And then when they break it’s a disaster.
WordPress itself needs to take a chill pill too.
Leave a version out for a year or more, and only small security patches. In the last year, I think we’ve seen block widgets, JQuery migrate nightmares, that new blocks theme thing, and more. I just want them to back off already.
It’s a nightmare keeping hundreds of clients up to date.
[+] [-] lucideer|3 years ago|reply
The WordPress codebase is a disaster, and the problem is self-compounding. The founders / core have found success writing disastrous code, and as such have no impetus to be aware of the benefits of higher quality - this is largely because (as you point out) the model of development shifts the burden to small individual website makers deploying (& maintaining / firefighting) WordPress.
Since it's open-source, a disastrous codebase could be "fixed" over time if experienced engineers were willing to join and contribute to the project over time, but the culture of QA-ignorance among existing core contributors has a tendency to exasperate experienced engineers.
I'm not saying it's a "toxic" culture per se - it's very open, and especially welcoming of new / inexperienced / beginner contributors, which is certainly cool for learning. But once contributors gain a little knowledge they go one of either two ways: knowledge-stagnation (enough to contribute but not to improve), or exasperation (enough to know how to improve but lacking motivation to make that uphill battle).
The culture from core extends to the plugins, not only because there's overlap in devs, but also because the APIs the plugin community have to use are garbage. This means many of the popular plugins - while they may have high-quality UX and design - have very poor code behind that.
All the above means that WordPress needs constant small fixes contributed by an army of devs to prevent it falling over / getting hacked, which massively increases the update frequency: there's nothing preventative within it's architecture, it's all reactive patches. It also means it'll only be a viable platform as long as its extremely popular: once popularity decreases a little, the maintenance burden will be far too high for the smaller community to sustain, and existing installs are going to be even more vulnerable than ever.
[+] [-] billpg|3 years ago|reply
[+] [-] albatrosstrophy|3 years ago|reply
But it's free and I only pay for hosting. Anyone knows what are the alternatives for someone like me?
[+] [-] XCSme|3 years ago|reply
[+] [-] NGRhodes|3 years ago|reply
[+] [-] partiallypro|3 years ago|reply
IMO, I think Automattic introduced Gutenberg way too soon to Core and introduced it as very half baked. Still to this day it's very half baked to an incredible degree, some pages will just break outright and resort to JSON errors, not to mention the built in blocks are awful and 3rd party blocks often break. That probably turned off a lot of people. It's still easier to just buy a theme that has a built in page builder and you'll get similar Lighthouse scores to Gutenburg (this being for average users, not custom themers, etc).
[+] [-] siquick|3 years ago|reply
[+] [-] jillesvangurp|3 years ago|reply
Among the things they've done recently:
- a major web site redesign (custom styling and look)
- added translations (via a plugin)
- updated how we gather analytics
- added a hubspot integration
I don't know many platforms where that can happen without technical people getting involved. All the next best options are SAAS platforms like shopify, squarespace, hubspot, etc.
None of us have any php skills (well, I deny having them and tend to not touch it). It's not perfect. But it's there and it works. For me the main value is that it can do what it does without me needing to be involved. We spend a few days setting it up at some point and making sure it gets updates. That's it.
It's not surprising wordpress market share is declining. I'd actually recommend new companies to pick one of the SAAS options. Even with wordpress, getting somebody else to host it for you is probably wise (there are a few good companies in this space).
[+] [-] pluc|3 years ago|reply
[+] [-] technion|3 years ago|reply
Across our fleet, disabling hacked instances is a routine event. There is often a marketing person that wants to argue - according to their industry, WordPress is leading the security space. It's incredible how different industries view the product.
[+] [-] nr2x|3 years ago|reply
[+] [-] peckrob|3 years ago|reply
You want a blogging platform? Wordpress is one of the best, hands down. You want a basic CMS that is so dead simple that anyone that can use a word processor can update the website? Wordpress excels at this, because that is what it was designed to do.
But I do think it is a poor solution in a lot of cases where it has been shoehorned into. People keep grafting so much extra, unnecessary crap onto what is still, at it's core, a blogging platform. Often this is done by low-skill, low-paid "consultants" with very little experience in writing maintainable, secure code. Literally all they know how to do is write Wordpress code. I would often end up having to clean up the mess from these folks, who often still write PHP like it's 2007 and they haven't learned better [0].
Wordpress's architecture has, until relatively recently, encouraged this behavior. Their stubborn refusal to move beyond PHP 5 for many years (and continuing to support absolutely ancient versions of PHP 5 at that!) held their entire ecosystem back from writing better, more secure code for a long, long time. And, more broadly, held PHP as a whole back, as they were among its largest players. It was really hard to make the case for hosts to upgrade PHP when Wordpress still supported whatever ancient version of PHP the host was providing. Their internal architecture can be very messy in places and documentation often contradictory about what the "correct" or even preferred way to do something is because there are multiple ways implemented at different times.
I will give them credit: Wordpress itself doesn't have too many gaping security holes anymore. Most of those has been patched. It's the plugins and themes that provide the attack surface now.
The public plugins themselves (and to a lesser extent the themes) are of such widely variable quality that it is difficult to know what to use and trust. You're probably okay with the "official" plugins and most of the widely-installed third party plugins, but you get too far off the beaten path, you find a lot of garbage (and, to be fair, a few gems as well). And any custom plugin I find is immediately suspect for the reasons above. Building a theme? Which of these multiple ways of user customization do you support? All of them? None of them? Or do you just write your own customization further messing up the UX for writers and editors who have little idea how to manage Wordpress beyond the very basics of writing a post.
Oftentimes when I would come into a Wordpress case, there's 30 or so plugins installed, half of which are disabled and you have no idea what is causing the client's problem. It takes a few hours just to untangle the mess, and you can't ask the last "consultant" because they wrote garbage code, threw it over the wall and disappeared. It's the reason I usually don't take Wordpress cases anymore unless it's someone I know or an installation I did, myself, from scratch that hasn't been messed with by anyone else.
Wordpress is a great blogging platform and basic CMS. It's when people start trying to make it do things beyond this that problems start to accrue. I don't hate Wordpress. I hate what people try to do with it.
When Wordpress is your hammer, everything looks like a custom post type.
[0] https://phptherightway.com/
[+] [-] rubyist5eva|3 years ago|reply
[+] [-] agumonkey|3 years ago|reply
[+] [-] ubermonkey|3 years ago|reply
It's legit AWFUL. It's a reasonable blog engine, sure, but it's been forced into being a general CMS, and it was never built for that. Our corp site is on it, and I fucking HATE it (fortunately I rarely have to deal with it).
My personal blog (21 years old and counting) has been through a bunch of platforms (Blogger, Greymatter, Blosxom) before settling on Wordpress. As I said, as a blogging tool, it's mostly fine. I don't really HATE it there, but it's still too fiddly for my tastes.
[+] [-] lucideer|3 years ago|reply
[+] [-] code_runner|3 years ago|reply
Sometimes the answer is “oh god we can’t do that”… and that seemed to be ok if we had some alternatives
[+] [-] stefanos82|3 years ago|reply
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...
[+] [-] kappuchino|3 years ago|reply
are you f**king kidding me? I've started to use pelican. It creates a flat file-based website with all I need. (See: https://blog.getpelican.com/)
[+] [-] jokabrink|3 years ago|reply
> If WordPress is shrinking, something else must be growing, this is, after all, a zero sum game. The very clear winners at the moment are Wix and Squarespace.
I disagree with the authors findings: When taking a look at the quaterly data https://w3techs.com/technologies/history_overview/content_ma..., one can clearly see that WP and Shopify at least plateaued which is alright.
But the authors conclusion, that WP's loss gives points to Wix and SqSpace for me does not hold: The numbers for "None" still decreases and much more strongly than the two mentioned above.
He conveniently forgets the "None" partition, making is entire argument/criticism (for me) somewhat thin. He could in the same way argue, that Wix and Squarespace are more successful in getting non-CMS websites to switch.
[+] [-] bombcar|3 years ago|reply
[+] [-] esquire_900|3 years ago|reply
[+] [-] chris_wot|3 years ago|reply
[+] [-] karaterobot|3 years ago|reply
Especially when, according to that same survey, it's up 1.7% since this time last year...
[+] [-] d3nj4l|3 years ago|reply
[+] [-] ozten|3 years ago|reply
I think they could have avoided much of this by listening to these devs, having backwards compatible designs, and slowing down to produce higher quality code.
[+] [-] paulryanrogers|3 years ago|reply
[+] [-] altdataseller|3 years ago|reply
[+] [-] mitchdoogle|3 years ago|reply
[+] [-] rograndom|3 years ago|reply
[+] [-] Yabood|3 years ago|reply
[+] [-] sidlls|3 years ago|reply
[+] [-] sofixa|3 years ago|reply
[+] [-] tbyehl|3 years ago|reply
[+] [-] chris_wot|3 years ago|reply
[+] [-] synicalx|3 years ago|reply
Wordpress is not an ecommerce system unto itself, but rather another free component of a fully functioning ecommerce system made useful by the freemium plugins, security vulnerabilities and PHP comprising a full CMS as defined by POSIX.
[+] [-] stefanos82|3 years ago|reply
[+] [-] chupchap|3 years ago|reply
[+] [-] justinator|3 years ago|reply
[+] [-] haswell|3 years ago|reply
But many creative types I know have used at least one if not both. We are not the intended market.
[+] [-] andybak|3 years ago|reply
But I'm not sure what that adds to the conversation without some background context on our requirements, use-cases or constraints?
[+] [-] kstrauser|3 years ago|reply
[+] [-] Gigachad|3 years ago|reply
[+] [-] etchalon|3 years ago|reply
[+] [-] subtledigital|3 years ago|reply
Unless you're after a custom job (Which most SMB's don't actually need), one of the DIY platforms are more than enough.
WordPresses UX and UI is horrible and confusing for most business owners -- take your developers hat off here.
[+] [-] pineconewarrior|3 years ago|reply
While the editor UX continues to get more convoluted, so too does the DX. PHP and React interfaces grow further apart in their capabilities and it's really just outrageous to have to master so many things to create a simple block in the editor.
It's really just not worth the effort.
[+] [-] indymike|3 years ago|reply