PsySH VS CraftCMS

PHP is great, but you need to be a pretty decent developer to use it effectively.

It has a rather nice interactive shell, https://psysh.org/ . I've built non-trivial, non-web systems in it.

Concurrency 'within' the language isn't as nice as some alternatives, but the FCGI-style deployment is quite reliable and convenient in practice.

psysh is an interactive shell that enables developers to explore and experiment with PHP code without the need to write the source code for an entire application. It provides a simple and user-friendly shell interface where you can enter PHP code and instantly observe the results. Also, psysh is a configurable tool equipped with various plugins and modules. Therefore, you can customize it the way you want.

Tinker is a REPL built over psysh which is a general-purpose REPL for PHP. Since a Laravel application is not plain PHP and has states, databases, caches, events, and many more complex resources specific to the framework, it's not possible to interact with the application the way one would expect just using psysh.

Why choose when you can have both in one https://psysh.org/ lol... I testdrove it once, but not convinced (I think the "merged" 2-languages-in-1 is pretty funny but maybe it works for some people).

Would love to see https://psysh.org incorporated in core.

It does! Or rather it used to (and still does for some things) but looks like it broke for stdout and return value dumping a couple of years ago.

PsySH offers a dev console and interactive debugger for PHP projects. In effect, this repo creates a REPL platform for PHP developers.

psysh is a killer tool in situations like this.

And detail more on executing it: https://github.com/bobthecow/psysh/wiki/Usage

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.