faustjs VS Strapi

Yeah, in hindsight, we would have used Next/Vercel. So we're tactically moving over to that. There are many new frameworks, like Astro, that are really exciting, but it seems like Next is the best choice if you have a data-heavy app that has a dynamic mix of SSR and static pages. For Wordpress in particular, I'd recommend that you check out Faust.js. It's build with Next and I'm amazed by how well it works with Wordpress without much effort: https://faustjs.org/

https://faustjs.org is a great headless Wordpress solution for Nextjs. I've tried several CMS solutions and ultimately WordPress is invariably the friendliest option from a client perspective.

I'm working through a large project where we're leveraging WordPress and Next.js. Check out Faust.js (https://faustjs.org/) which works as a layer to handle a lot of the query/template/routing stuff that maybe isn't super-intuitive when trying to hook WordPress up headlessly...

- FaustJS (built for headless WP on NextJS w/ full site editing capabilities)

Faust.js is the front-end JavaScript framework built on top of Next.js, created to make developing headless WordPress sites easier. The idea of this new version is to make a parity between the WordPress world that a developer might be used to but replicate it as much as possible in the JavaScript front-end world.

This is where it started. Then there is also Faustjs started by WPEngine. https://faustjs.org/

https://faustjs.org/ built specifically for headless WP

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 🚀