WordPress Packagist VS Pico

If I have to use WordPress for something, I'll build it as a standard PHP project, requiring WordPress and any themes/plugins as a Composer dependencies from johnpbloch/wordpress and WordPress Packagist (more info here). If I need to do any significant templating, I like to use Timber.

Use it together with https://wpackagist.org/ and you can update all plugins/themes by latest or by version number.

Another option you can look at is Bedrock by Roots - that is sets WP as an app with composer already set up. It allows you to install WP plugins (from official WP repo) via composer (WP Packagist). The structure is set up to allow for git workflow. Also helpful if you want to make use of a bunch of composer packages on your site.

https://wpackagist.org/ in the example you see "repositories", now in that array you can put your plugins github-link and set the other settings. with composer install you install them and with composer update you update them

Side question: I know that the WordPress ecosystem has been moving toward better support for Composer – e.g., with WPackagist. But wouldn't plugins installed/updated via Composer run into the same issue?

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