What are the advantages of creating a site on a self-written engine over the same Wordpress?

Question

CMS

I want to create a website with a database (for example, recipes) with different search filters. From knowledge only the basics of PHP and MYSQL, good knowledge of Layout/jquery.
What interests you:
1) Will I win in terms of optimization relative to the same Wordpress in technical terms?
2) What problems can I encounter or what should I pay attention to?
3) What needs to be done in a self-written engine so that it is sure to be cooler than CMS (faster, optimized, etc.)?
PS: there is no need to recommend installing Wordpress, because there are a million plugins with everything already ready - I want to make a site on my engine and not write crutches for Wordpress all the time.

Answer 1

What are the advantages of creating a site on a self-written engine over the same Wordpress?

Advantages can only be in the case when the ready-made solution does not suit you, or the cost of finishing the finished solution is higher than making your own.
Depends on the task. If WP is already solving it - most likely not.
This question can only be answered on the basis of the TOR, or product brief.
If purely in technical terms - you can use the following conventions https://github.com/index0h/php-conventions . I don’t recommend chasing speed and optimization right away, spend an order of magnitude more time.
In terms of products, making a mass-produced cms with the same tasks as WP and the same audience coverage is practically unrealistic at the moment.

Answer 2

Are you going to single-handedly do better than what a team of professional developers did? Shtosh, let's break it down point by point:
Absolutely not, unless your site is resurrected from zero, of course.
Time problem.
That's a good question, but it's too bad you're only asking it now.
It will pass.
Do it on a ready-made CMS and don't invent it.

Answer 3

Will I win in terms of optimization relative to the same Wordpress in technical terms?

It still needs to be understood, you can write better or not. But the fact that you will lose fatally over time is unambiguous.
Templating (you will not explicitly write your own), caching, protection against vulnerabilities (you can spend several years)
Assemble a development team and sell the idea to investors who will pay for it all. In principle, it is practically impossible at the current time, because today's top 10-20 CMS appeared more than 10 years ago and each of the systems has acquired a community, a fan base, and, of course, a marketplace in the form of extensions or maintenance
Show a list of your edits accepted into the core of the same Wordpress?
But it's still worth a try. While young-hot, I want to write everything. Well, at least start not from 0 - take any framework (or several at once) and write an admin panel for it. This will be much more useful in the future.

Answer 4

If this is the so-called. Pet project - do it.
1. Win. But spend a lot of time.
2. Is the lack of a plugin and a theme for any sneeze a problem? I don't see others. BUT - if the site is for yourself and you don’t show this framework to anyone (don’t let them use it). If you plan to give it to the community, there will be a lot of problems in the amount of 7 billion.
3. Static on the front and all the tips from, for example, the same google page speed
In general, for a personal site "for the sake of the site" I would choose a static site generator. They are full now. The output is fast sites with not very great functionality (well, there is access restriction, membership, and other goodies for a logged in user). And to issue a series of articles and filter them by recipes is not a difficult task and is purely for the front-end.
You unravel the mess in your head: WordPress was created for millions of people. It is flexible, expandable horizontally and vertically (plugins and servers), and your solution does not claim to be unique. For sole use (development), write your own. They break it (if they notice you) - find it, fix it. But here you will never create a product for the masses outside of WordPress. And if someone suddenly takes your framework, then I sympathize with him. And if you die - who will develop it? ps the last - the realities and a warning to others not to use and get involved in such small projects.
Previously, each studio had its own framework - they did this in order to hook their customers. Make them be on the balance of this desk forever. I'm glad it's gone now. And then try to find a developer for the Uncle Vasya framework

Answer 5

Let's start with the basics - why do you need a site with culinary recipes?
If it’s just for yourself and to be, then you can do whatever you want and what you can do, there are no limiting factors other than your desire and the availability of free time.
If you make money on it, then install WordPress tomorrow and start earning money the day after tomorrow. And if you cut a self-written engine, then you will die of hunger before you finish.