+1 vote
by
web development
by
And WHAT to develop under this CMS?!??

Everything is already worked out.
It's easier to write a plugin for it and sell it through the WP store - who needs it, they will buy it.
by
There is no demand for development on the WP, mostly requests go to pull up the layout, make a landing page, business card, a simple store. No requests for complex stores on it, no requests for complex projects on it. I think this is due to the fact that out of the box GP is empty, so the implementation of the TOR of a custom project on the GP is not inferior from scratch on the framework.

6 Answers

+7 votes
by
Because the web is not just blogs and flea markets.
0 votes
by
I'm going to add something of my own. Writing for wp is not profitable. Lousy code in the output, a lot of fuss and in the end the client does not understand what he is paying for. So in the end those who need something serious do it seriously, while millions of sites are just hanging out. This is generally neither good nor bad, but it is not profitable for the company
+4 votes
by
WP by itself and through a million plugins, allows you to "develop" a class B solution for a specific task in a virtually no-code format. And a person with basic knowledge, a content manager can handle it. And at the level of a business card site, a landing site, a blog site, a product list, it's enough.

Something serious to do on WP makes almost no sense, as either fun with a bunch of conflicting plugins (sooner or later it starts), or to understand and write their own (but why the irrelevant experience, if you can do it on a conditional Laravel + vue immediately ok).
0 votes
by
Because the Vp is a "do-it-yourself" thing.
Everyone as a child loved to play with the constructors. Here, too, even a monkey can bump a dice in the element.

Everyone as a child loved to play with the constructors. Here, too, even a monkey can bump a dice in the element.
by
(I found something to brag about))
by
There are Indians there. Surely they took all the orders. And why do they write that everything on the GP on plugins? Of the plugins I have only CF7 and ACF, the rest myself, even the cart, payment system, etc..
by
Everyone here remembers the circular diagram of quick-quick-cheapf8737cb9aeb93026f635c595dcti.jpg
by
Vladimir Druzhayev It's so inconvenient to rework something to suit the customer. Sometimes it's much easier to write from scratch.
0 votes
by
You are trying to compare the warm and the soft.
You will hardly find any vacancies only on WP, because only web-studios deal with WP. But they have a number of other CMSs in addition to WP: Bitrix, Joomla, OpenCart, Drupal, NetCat, etc. Therefore, if you get a job in a studio, you will have to work with all of these CMSs, and knowing only one WP will not save you.
WP is not needed for continuous support. You set it up once, you have it all set up, and it works. That's the end of the backend. Plus, there are practically no complex projects on WP. After all, it was originally positioned as an engine for blogs.
The frontend (and Vue) is another matter, where the interface and design can change very often. Because this is what the users of your application see. They don't see the backend, they don't even know you have WP. They see the frontend: all those animations, scrolls, sliders, beautiful forms. And that's the versatility of frontenders. They can do anything with Vue, they can do business card site, online store, bank, stock exchange, social network, and so on.

So the answer is simple - it's all about versatility.
0 votes
by
Because most users can use WP without programming
...