It depends on what you mean with "use it for an API". If you only need the CMS to manage the data (e.g. for a blog) and you build the frontend by yourself I recommend using Headless CMS's. "Headless CMS" means that the CMS provides your content as data over an API and you can access in whatever you want. Instead of CMS tools like Wordpress, Ghost, Joomla etc. that deliver the whole package (frontend + backend).
When using a headless CMS I recommend Directus or Strapi. Beside that, the popular CMS tools like Wordpress have most of the time also the possibility to use it headless and turn off the frontend.
I just started with Strapi, I like it. I feel like using it mainly for the API instead of components. I was told if I was using it for components, I would be limited?
Yes that's the benefit of Headless CMS's like Strapi. The data and the frontend are splitted. So you can make anything you wan't without limits of what the CMS offers
If you use a traditional CMS the frontend and backend depent on each other. In other words you manage the data (backend) by building the website (frontend). Most of the time this is easy for people who don't wanna use HTML and just wanna make the page with a site builder (think of Wordpress).
A headless CMS provides the data over an API. So you manage the data in Strapi with the benefit you don't have to use your own API (in this case based on Node.js). The frontend is on your own. You can build whatever you want and use every framework you like (e.g. Vue.js, React.js , Angular, Svelte....). With the API + endpoints of Strapi you can access the data wherever you want.
Great!, I have seen that python is moving up tho, but is that more of what you “need” college for? I like front end, but I don’t like so much the styling, but “connecting” making things function
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It depends on what you mean with "use it for an API". If you only need the CMS to manage the data (e.g. for a blog) and you build the frontend by yourself I recommend using Headless CMS's. "Headless CMS" means that the CMS provides your content as data over an API and you can access in whatever you want. Instead of CMS tools like Wordpress, Ghost, Joomla etc. that deliver the whole package (frontend + backend).
When using a headless CMS I recommend Directus or Strapi. Beside that, the popular CMS tools like Wordpress have most of the time also the possibility to use it headless and turn off the frontend.
I just started with Strapi, I like it. I feel like using it mainly for the API instead of components. I was told if I was using it for components, I would be limited?
Yes that's the benefit of Headless CMS's like Strapi. The data and the frontend are splitted. So you can make anything you wan't without limits of what the CMS offers
I’m liking it over Django, DJ you had 3-4 steps, but this is nicer. But, it’s still front end?
If you use a traditional CMS the frontend and backend depent on each other. In other words you manage the data (backend) by building the website (frontend). Most of the time this is easy for people who don't wanna use HTML and just wanna make the page with a site builder (think of Wordpress).
A headless CMS provides the data over an API. So you manage the data in Strapi with the benefit you don't have to use your own API (in this case based on Node.js). The frontend is on your own. You can build whatever you want and use every framework you like (e.g. Vue.js, React.js , Angular, Svelte....). With the API + endpoints of Strapi you can access the data wherever you want.
Great!, I have seen that python is moving up tho, but is that more of what you “need” college for? I like front end, but I don’t like so much the styling, but “connecting” making things function