next-wordpress-starter VS Strapi

Colby Fayock has also created some interesting content with demos and creating a starter kit. Next.js with WordPress Starter Kit

This is a similar pattern we've seen in a few popular WordPress starters such as Colby Fayock's and WebDevStudios. While this pattern feels intuitive, it can actually be problematic.

Next-wordpress-starter

While you can’t do this out of the box with Next.js, there are plugins to help, such as the Next.js Sitemap Generator or a custom approach like the one I added to my Next.js WordPress Starter.

We'll be using Colby Fayock's Next.js WordPress Starter in this walkthrough (https://github.com/colbyfayock/next-wordpress-starter/). This Next.js WordPress Starter project aims to "take WordPress as a headless CMS and use Next.js to create a static experience that can be deployed anywhere."

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 🚀