burdy VS Strapi

We would appreciate any feedback, suggestions, or questions you may have about the Burdy 2.0! If you'd like to support us, please leave us a star on our GitHub.

If you like what we are doing, please give us a star on GitHub.

Hi RationalMemer69! Yes, we have an internal roadmap that is not yet visible to the public. We will share the roadmap in the upcoming weeks! I can only give you a rough idea (we have not committed to this yet). From minor releases we might have: - Exporting / Importing content types - A/B testing capabilities for Posts / Pages / Fragments - Machine (Automatic) translation/localization of Posts / Pages / Fragments (integration with AWS Translate and Azure Translator). - Azure Blob support for File/Object storage (we currently support uploading files to FileSystem and AWS S3) The Next Major releases will look something like: - Plugins System / Marketplace - from project to plugin with a simple command and publish them on the Marketplace. Developers will be able to set pricing of the plugin (free / paid) - ECommerce (down the road) There might be some enterprise plugins such as "Build your own Netflix" on top of the AWS, where Burdy will utilize many AWS services to achieve transcoding, storage, delivery. Again this is not an official roadmap yet but this is what we would like to achieve :) If you like our project, don't forget to give us a star on a GitHub https://github.com/burdy-io/burdy

GitHub: https://github.com/burdy-io/burdy

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 🚀