Contao VS Yii2

Another usecase are Framework based CMS System. Beside Drupal, Typo3 using example Symfony components, still are not Full Stack Symfony and don't use Symfony based folder structure and are so very different then using Symfony Full Stack based CMS. In this area other CMS like Sulu, Bolt, .. are placed which do not hide Symfony Full Stack and are more for the web applications which are not typical just a Website but has application based component in it which can be build with the Symfony components and ecosystem. This CMS are also mostly more version control friendly as most configurations are inside Code and not inside Database and the CMS admin concentrate on Content Management and configure the System itself. Another CMS which is more and more migrating Full Stack Symfony is Contao CMS, which definitly should not be forgotten.

If you're familiar with Symfony, you could also check out Contao. I never really used it, though, because it's a bit too complex for me. But in theory, you can use most libraries for Symfony there.

Maybe you have a look at CMS Conato: https://contao.org/

Yii is one of the oldest PHP frameworks, acronym as Yes It Is! It has 14.2k stars and 7k forks on GitHub. It is a fast, secure, and flexible PHP framework for web development, especially for building MVC architecture websites. It is an Object-Oriented PHP framework that requires knowledge of inheritance, polymorphism, etc.

In Yii Framework we have a middleware that will allow us to access our applications without the need to point the web server to the public directory of each template, so we will use the middleware SubFolder::class.

asset-packagist: This is the traditional Yii2 way, here we will add the following to our composer.json.

It is often preferable to manage Yii Assets programmatically. For example, when you use the widget in a page, it will automatically include the required css and javascript files, instead of asking you to manually find these files and include them. And when you upgrade the widget to a new version, it will automatically use the new version of the Yii Assets. In this tutorial, we will describe the powerful Yii Assets management capability provided in Yii Framework .

As we can see in the example above, we have defined the configuration of our packages in files .php (it doesn’t matter if they are YiiFramework packages or not), this allows us to define the configuration of each component in a very simple way to understand.

Now if we want to create an extension, under the code standard used in the Yii Framework v.3 packages, we can use yiisoft/template, provides us the tools necessary for our code to comply with good coding standards they are:

Now we understand how to do any configuration of any YiiFramework package or external, it is not necessary to have a single long and complex configuration file, we can organize it according to the group of configurations and Yii config will do the work for you, as well as the container it applies the definitions for you, with the automatic wiring facility in controllers, which makes it easy to access any container dependency without the need to use static access to it, or depend on the container itself.