Yii2 VS CraftCMS

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.

The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to update our CMS or some user have a weak password, it can be someone outside of our team. WordPress, Drupal, CraftCMS, or Ghost are perfect examples of such CMSs.

I checked one website in that list, it uses CraftCMS, which apparently has htmx bundled. (https://github.com/craftcms/cms/tree/main/src/web/assets/htm...)

Would be interesting to know which other CMS'es make use of htmx (and to what degree).

PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves Laravel based for marketing.

You're basically looking for any CMS that supports headless mode. E.g. Strapi (https://strapi.io/, NodeJS based), CraftCMS (https://craftcms.com/, PHP based) or countless others.

Craft CMS

It's built on Craft CMS. Makes the relationships between elements (a match and a player, for example) super easy.

Is there a reason you aren’t using an existing CMS? There’s a lot that provide all the UI functionality you are talking about and then expose it via a API to be consumed in your front end. https://craftcms.com is one option I’ve had good success with.