Pico VS TYPO3

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).

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