Pico VS Strapi

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

https://prisma.io is popular as I understand it. I've been trying out https://strapi.io the last week and am thoroughly impressed.

They both do much more than build queries. One big thing both do is automate database migration calculations. Strapi goes further and gives you a CMS and admin UI on top, as well as doing a lot more of the complex query building from a json object. Both still require a fundamental understanding of the data model and SQL

As of April 2024, Strapi's GitHub repository has garnered 59.7k stars and 7.5k forks, showcasing its widespread adoption. The project has also secured a substantial $45+ million in funding, cementing its position as a prominent player in the headless CMS space.

const pages = await client.GET("/pages", { params: { query: { filters: { // @ts-ignore - openapi generated from strapi results in Record // https://github.com/strapi/strapi/issues/19644 path: { $eq: path, }, }, // @ts-ignore populate: { blocks: { populate: "*" }, }, }, }, });

On a side note. Where do all these endpoints come from? Strapi is open source. We can read the source code. All these endpoint come from the Users and permissions plugin. So, if we go to Strapi on github and browse around the files a bit eventually you will find the auth.js file that contains all of the routes. You can also find the Strapi controllers in there if you're interested.

Strapi

Strapi: The Code Anarchist

Strapi - Open source Node.js Headless CMS 🚀

https://strapi.io/ https://prismic.io/ https://bubble.io/ https://hygraph.com/ https://www.sanity.io/