Developers often argue about frameworks. Many believe that WordPress is not a framework. But is that really the case?

A framework (sometimes framework; an Anglicism, a neologism from framework — skeleton, carcass, frame, structure) is a software platform that defines the structure of a software system; software that facilitates the development and integration of different components of a large software project.

In general, this should be enough for 50% of people. From the definition, we understand that yes, WP is a framework.

But why do 99% of PHP coders think that this is not the case?

WordPress is not a framework, but a CMS

In general, this statement is also true. Yes, we can use WordPress as a constructor.

We don’t even have to write code. We can use NoCode, ZeroCode & LowCode strategies. These are so-called configuration-based approaches, where you can manage the entire project online without changing the code.

Discover the most exciting things in the world of excitement – Las Atlantis live casino

Is this good or bad?

For business, it’s good — costs are reduced by a factor of 10. In 99% of cases.

For programmers, it’s bad — first, they are left without work, and second, such a system is much more difficult to manage; you need to be able to think, and not many people can do that.

And from this it becomes clear why programmers hate WordPress — it’s a normal primitive survival reflex. You have to be against those who take away your bread and butter. WP takes away programmers’ bread and butter, and therefore it must be reviled.

One might think so, but there are nuances…

However, there is also some truth to it

Frameworks are inherently tailored to code and are driven by the desires of programmers — to make the code beautiful, to be able to write auto tests in a couple of clicks, to make migrations easy to build, to make queues in the background work clearly, and so on.

In WP, all of this can also be done, it is practiced in one form or another, but there are no clear, understandable solutions. And every large project invents its own solutions here.

However, this is not a reason to say that WordPress is not a framework. It is more correct to say that it is a framework tailored to the needs of a CMS without code, and it does not have any ready-made tools for narrow tasks. You will have to invent them yourself. For many, this is a problem. That’s why there are many cases when it’s really better to use something like Laravel or Symfony, because those frameworks have a number of tools for narrow-neck tasks.

Conclusion

In general, whether it’s a framework or not is not a question about WordPress. It’s a question of who uses it and how.

You can use it as a constructor and not worry about it. You don’t need to know architecture, code patterns, and other fancy words — just click and work.

You can use it as a framework, but then you need to know what the three types of OOP are, what AOP is, what EDA is, and how SOLID differs from GRASP.