DEV Community

Discussion on: when should you NOT use a CMS?

Collapse
 
dennisfrijlink profile image
Dennis Frijlink

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

Thread Thread
 
yobretyo profile image
Bret

I’m liking it over Django, DJ you had 3-4 steps, but this is nicer. But, it’s still front end?

Thread Thread
 
dennisfrijlink profile image
Dennis Frijlink

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.

Thread Thread
 
yobretyo profile image
Bret

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