DEV Community

Discussion on: You don’t always need a CMS

Collapse
 
dailydevtips1 profile image
Chris Bongers

Yeah it all depends on your needs, and the needs for the project.

I've build some amazing, simple CMS's that do one particular thing really well, like uploading house information, and nothing more.
But like you said, there is always that "oh just add this as well" factor.

Collapse
 
spaceninja151 profile image
Christian Knoll • Edited

Tell us more about this use case and maybe the stack? I seem to be stuck in "CMS equals Wordpress Blog" definition of CMS. I was trying a way to have a CMS for my client to update their page content - and the first step was making the site take in a JSON object and build the pages. I made a proof-of-concept in Angular (link below) which was fun, but then when I tried to put it into practice with a client's site, I realized it's not a good solution to put each element into one JSON file. I think I will just use Markdown next time.
stackblitz.com/edit/ck-dynamic-con...

Thread Thread
 
dailydevtips1 profile image
Chris Bongers • Edited

For this particular one I used Kunstmaan (A Symfony based CMS) and customized it for the needs of the project.

It really depends on the stack en needs for what you want to achieve.
There are countless CMS's out there.

You might also be keen on learning about headless CMS or CMS as an API systems like Contenful.

Happy to explain some more if you'd like, or look at your needs.

Thread Thread
 
spaceninja151 profile image
Christian Knoll

Oh you said you built the CMS so I thought you made it yourself, like making the funcionality in React or Angular or something.