Backdrop CMS VS Pico

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'm cooking up a really cheap publishing solution using Pico CMS ("stupidly simple") and rsync or something from my Obsidian Vault to my PHP server.

I'm using https://picocms.org/.

It is PHP based, works on a cheap limited web hoster.

The concept is: Upload a markdown file plus associated media, and it does the rest for you.

For customisation, you can use Twig and CSS, or a predefined theme (I didn't look into these, I wanted a custom appearance).

For feeds there are plugins, for comments I use a "mail me at [email protected]" approach.

I like PicoCMS a lot.

Have you tried Pico? No database required and. You can either use Markdown or plain text for posting. Each post is just a file... https://picocms.org/

Ever since version 2.0, Les Pas has been able to share albums with other Nextcloud users, you can even co-edit the same album with others if you publish the album as 'Joint Album'. But how about people not in your Nextcloud server, like those friends who attended your wedding? Create temporary guest accounts for them is just not feasible. Photo blog is here to help! And luckily, we have Pico, the stupidly simple & blazing fast, flat file CMS, which happens to have a very good Nextcloud [app]((https://apps.nextcloud.com/apps/cms_pico), enable us to publish our own blogs.

You can try Pico CMS. But if you have the time, try Hugo. The latter has a learning curve, and the docs are frustratingly non-beginner friendly, but once you get the basics, there is no going back!

Pico

For a blog, Pico can do the trick, and it's really handy to use (it uses Twig as template engine that's one of the best part for me).