Lektor VS Strapi

Guess I'm one of the annoying users who complained when armin's Lektor (https://github.com/lektor/lektor) started going dormant back when, but I loved it for a while. I'm on Astro now, but a big thanks for helping a younger version for me.

Lektor is a modern and flexible static content management system that utilizes Python as its core language. It comes with an intuitive web-based admin interface, making it easy for content creators to manage and update the site. Lektor supports a variety of content types and has an active community that contributes to its continuous improvement.

Lektor CMS is sort of a prototype-ish thing doing this: https://www.getlektor.com/

It has (used to have? Can't find them on the site now) pre-packaged binaries that you would drop into a folder structure generated by the technically-minded person, and the content editor can simply click on that binary, which opens the backend of the CMS in the web browser, make changes and click deploy.

There have been several Flask-based CMS's but I don't remember most of them. IIRC Lektor is based on Flask.

Static hosting could be enough for many sites and one could combine the technical and UX advantages of your dynamic interface with the advantages of static sites for security and distribution.

I found that useful when i worked with https://www.getlektor.com/ years ago. In lektor the dynamic part runs on a users desktop machine, but it of course wouldn't need to.

Lektor is Python based and Just Works, but it is far off the beaten track… https://www.getlektor.com/

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/