Backdrop CMS VS TYPO3

https://backdropcms.org was a fork of Drupal before the rewrite. It was pretty decent when I tried it (admittedly several years ago).

I see you decided on Wordpress, if you were going to use a CMS I think Drupal 7 would have been a good choice. Drupal has concept of entities and views. An entity as the name suggests is essentially a table and you can add all sorts of different fields to it. From simple text and number fields to images and fields that lookup other entities thus creating relationships between entities. Views is another construct that lets you choose how to display the entities. As a list of as a table a two possible views. Most of this can be done in Drupal 7 without writing code. I say Drupal 7 because you mentioned Wordpress. Drupal 8 and above is more of a developer framework and requires knowledge of Composer. Backdrop [0] is fork of Drupal 7.

[0]https://backdropcms.org/

I think some smaller biz and nonprofits jumped off to https://backdropcms.org

As a result DO community is not able to delete stuff. For example, they should delete all Drupal 7 stuff on the official website and give the lead to https://backdropcms.org/ regarding support. They should also auto archive issue that are more than a years old without activity.

6. BackdropCMS #

Here is a link to the release history for Backdrop CMS. https://github.com/backdrop/backdrop/tags

Backdrop CMS is a fork of Drupal 7, but with lots of the improvements of Drupal 9. https://backdropcms.org/

Another important alternative is Backdrop CMS. It's essentially an updated fork of Drupal 7, so migrating is really the easiest choice. Remember, even with D8 and D9, more than 50% of Drupal sites are still on D7. https://backdropcms.org/

I doubt that WordPress is in danger. Its multiverse / flexibility and ease of use compared to real content management systems like Typo3, NEOS or Drupal, and the ability to just install it and control your content on your own webserver, try that with Wix, WebFlow, SquareSpace, Shopify and all those "serverless" software as a service servers. Hopefully, the core team will either get their block editor right some day (WordPress 7.0?) or make it completely optional. That would still be better than a fork, but I'd wished they had improved security, performance and internationalization instead of releasing the new editing features in an unstable beta state.

In a more business feature based CMS but still more like traditional CMS are Typo3 and Drupal, both have there usecase and sure a big community around them with a lot of modules and co. And both allow customization and building, installable plugins and themes. But modern version allow give more control from the system to the dev. We also should not forget of Typo3 called Neos CMS, which has its own way and Framework around it.

The official site of TYPO3 https://typo3.org/.

It depends on how you installed your site. Is it composer installation or did you download the files from the typo3.org? If composer based - did you use helhum's secure installation?

Content management products using Statamic and TYPO3

At this point I'll try to show 5 important new tips I've learned myself while working on client projects with the TYPO3 CMS.

Official TYPO3 Repository