frontity VS Strapi

Honestly I wish they just offered an officially supported framework-agnostic headless solution on par with Block Themes. I was kinda hopeful when Automattic bought Frontify[1] some time ago, but for some reason apparently that went nowhere.

[1]https://frontity.org

You may want to start with frontity, the headless solution from...automattic. https://frontity.org/

I've done a bit of googling around, it seems there's a framework called Frontity which was used for this. Apparently it's no longer being maintained, so I was wondering if this is still the gold standard or if there's a better way?

Wordpress recently bought this company. That should indicate the direction WP is heading: https://frontity.org/

Check here - https://frontity.org/

(for more info https://github.com/frontity/frontity)

have you played with https://frontity.org/ at all?

Frotinity

Frontity is an open-source framework based on React. It uses your WordPress site as a headless CMS and renders it in a React framework. It enables you to build a fast headless WordPress static website quickly.

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 🚀