v8-archive VS Cockpit

The version 8 is not maintained anymore: https://github.com/directus/v8-archive Directus 9 has much more features, is more stable and much more performant. If you are running on shared host you can try using some "hacks" to run it like this one: https://github.com/niutech/node.php

You might be able to fork Directus v8 and bend it to your will: https://github.com/directus/v8-archive

Hmm...I just tried https://getcockpit.com/, which looks like a super lightweight CMS and PHP doesn't seem to work.

I am struggling with my instance of cockpit Cockpit (getcockpit.com) that all contact forms on my website keeps going to spam. The SPF record is correct.

https://getcockpit.com/ Recommend using V1, since V2 is a bit new and lags documentation and plugins.

Might be a long shot, and I haven't checked in on the project in years, but maybe cockpit https://getcockpit.com/ ?

Cockpit

Cockpit CMS is a straightforward framework for managing complicated and organized information. Additionally, it makes it possible to control the content adaptably and with few limits. This Open Source Headless CMS also supports a variety of devices on a single platform. It is very simple to install, and it takes little time to finish. As a result, you can begin your job without any problem or difficulty.

I've been using Cockpit (https://getcockpit.com/) for a few internal and personal projects now.

It's lightweight and easy to use. Just upload the folder to your webspace (minimal PHP requirements!) and you are good to go.

Create some collections for you data, link them if needed, and you can immediately use them via the API endpoints AND also via a GUI for CRUD operations.

This is really great because my colleagues are non-technical and I don't need to write some frontend for them to update data and so on and can concentrate on the "real task".

Documentation on the other hand is awful, to the point where you better refer to the "inofficial documentation" (for the interested: https://zeraton.gitlab.io/cockpit-docs/) with no way to improve the official one.

So, while I LOVE the ease of use, I wondered if somebody has a recommendation for a similar solution which might be somewhat more "mature" in regards to the documentation.

Link