Symfony, plain PHP, or WordPress: how to pick
Three tools, one question
Every PHP project starts with the same question: what do I build this on? The answer depends on what the project needs, not on which framework is best. Symfony, plain PHP, and WordPress solve different problems, and picking the wrong one makes the whole project harder than it needs to be.
Plain PHP: when the project is small
Plain PHP is the right call more often than people admit. If you need a form that emails its contents, a small API, or a script that processes a file, a framework is overhead you do not need. A single file with a few functions can be the whole solution.
Plain PHP shines when the scope is small and the team is small. There is no learning curve, no build step, no config to maintain. You write the code, you deploy it, you move on.
The line gets crossed when the project grows. Once you need routing, a database layer, authentication, and templates, you are rebuilding a framework by hand. That is when you switch.
Symfony: when the project is serious
Symfony is for applications with real structure. A SaaS product, a custom admin panel, an API that other systems depend on. These projects have many moving parts, and Symfony gives you the pieces to keep them organized: routing, dependency injection, an ORM, security, and a testing setup that works out of the box.
The cost is a learning curve and a heavier setup. You are not going to write a Symfony app in an afternoon. But for a project that will live for years and grow, that investment pays for itself.
Symfony also plays well with others. You can use it as a full framework or as a set of components inside a plain PHP app. That flexibility is one of its best features.
WordPress and WooCommerce: when content and commerce are the point
WordPress is not a framework, it is a platform. You use it when the product is content, or when the product is a shop. If a client wants a blog, a brochure site, or an online store, WordPress and WooCommerce get you there faster than anything you could build by hand.
The trade-off is control. WordPress makes the common cases easy and the unusual cases hard. Custom post types, plugins, and themes give you a lot of room, but you are always working inside someone else's rules. When a client needs something WordPress does not do well, you end up fighting the platform.
WooCommerce is the same story for e-commerce. It handles products, carts, payments, and shipping out of the box. For a typical store, that is a huge head start. For a store with unusual requirements, it can become a constraint.
How to decide
Ask what the project is really about. If it is a small, self-contained task, use plain PHP. If it is a serious application with structure and a long life, use Symfony. If it is content or commerce, use WordPress and WooCommerce.
The tools overlap, and you can mix them. A WordPress site can call a Symfony API. A Symfony app can embed a WordPress blog. But start with the tool that matches the core of the project, and you will save yourself a lot of pain.
Need a hand with a WordPress site that keeps breaking? See what I do and how I work.