Contao VS Strapi

Another usecase are Framework based CMS System. Beside Drupal, Typo3 using example Symfony components, still are not Full Stack Symfony and don't use Symfony based folder structure and are so very different then using Symfony Full Stack based CMS. In this area other CMS like Sulu, Bolt, .. are placed which do not hide Symfony Full Stack and are more for the web applications which are not typical just a Website but has application based component in it which can be build with the Symfony components and ecosystem. This CMS are also mostly more version control friendly as most configurations are inside Code and not inside Database and the CMS admin concentrate on Content Management and configure the System itself. Another CMS which is more and more migrating Full Stack Symfony is Contao CMS, which definitly should not be forgotten.

If you're familiar with Symfony, you could also check out Contao. I never really used it, though, because it's a bit too complex for me. But in theory, you can use most libraries for Symfony there.

Maybe you have a look at CMS Conato: https://contao.org/

Strapi provides a centralized data managing platform. This makes it easier to organize, update, and maintain the FAQ data. It also automatically generates a RESTful API for accessing the content stored in its database.

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 🚀