Native API Module on OctoberCMS (Like Strapi)

#1

Lately, I’ve had to work with NodeJS (:nauseated_face:) and their famous CMS called Strapi. Honestly, under the hood, when it comes to customization and new plugins, it’s kind of restrictive, disorganized, and unpleasant to work with. OctoberCMS is light-years ahead in these areas, not to mention practicality and ease of use. However, I have to admit I was really impressed with the API, permissions, API authentication, and documentation. Man, I wish October had something like that. I know, I know, it could be a plugin… But nobody wants to make it, and we wouldn’t have the same cleverness to make everything better and easier like the October creators do haha. Just like we’ve always had to rely on third-party plugins for e-commerce and will soon have native e-commerce in the future, why not have something like this too? :wink: modules/api :heart:

At the very least, it’s worth considering for the roadmap portal.

1 Like
#2

+1, I would love to see octobercms to propose a headless cms version that generate full and flexible automatic for, at least, tailor created content.

1 Like
#3

Hey @kallef,

You’re right that Strapi’s API layer is impressive — it’s their whole identity as a headless CMS, so they invest heavily in making it automatic. OctoberCMS, on the other hand, is a traditional CMS with headless options: it can serve Twig-rendered pages or act as a backend for APIs.

Right now, October gives you:

What October doesn’t offer is the “zero-config, automatic API” you get in Strapi. Still, the idea of a native modules/api is interesting — it could give October a more headless flavor for projects where that makes sense. Definitely worth suggesting on the roadmap portal for discussion! https://portal.octobercms.com

2 Likes