Backdrop CMS VS Drupal

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/

You won't find common examples of scaffolding for the XAMPP technology stack, because technology stacks in general do not follow such rigid styles that frontend frameworks like React do. For example if you compare two popular PHP projects like WordPress and Drupal they have completely different folder structures despite both being CMSs. Rigid or "recommended" folder structures only apply to any particular backend frameworks, design patterns or CI/CD methodologies you choose to follow, not the stack itself.