You may have missed my point. I will try to expand on it.
You're referring to CRUD (Create, Read, Update, Delete) common database functionality...
That is what i consider that the author is talking about when he is referring to CMSs, not what i consider as CMSs.
You mention databases in trying to illustrate my point, so, trying to expose my view, i would underline some basic ideas. Those being that just by using markdown one is already managing content. That Data is not synonym of database. And managing is not synonym of CRUD.
(Although i must say that CRUD do deserve more understanding and respect than what he has commonly gotten.)
At this time it should be "relatively easy" to create a simple worpress that just use files as data container (ex: use next and markdown or sqlite?). Easy? Just thinking about making and maintaining the plugin system makes me loose hair...
My definition of CMS is way broader than the quote. And I argue, right or wrong, that it is a healthy point of view for devs to have a "correct" vocabulary (not forgetting that it is ever changing). Engineers depend heavily on vocabulary for effective communication.
I do not consider myself in any way as a good example of effective communication (more of the lazy types 😎 ), but In this particular case I am not concerned about experienced devs. They have the "luxury" of engineer scars. I more concerned about "junior devs" confusing simple things and misunderstanding their power to do whatever they need and want with the great tools they have.
(And to not forget also about some common "unfortunate" twitter/youtube/facebook trends that end up loosing all credibility for too many good ideas.)
tltr: CMS is just an acronym for an engineering (marketing, etc) problem and should not be tightly coupled to some tech stack. By "easily" talking of CMSs as worpress (drupal, joomla, ...) we can only loose power in this all connected, uncontrolled world.
I love how you said "Easy? Just thinking about making and maintaining the plugin system makes me loose hair" haha :)
As you know, CMSs are good at managing content so someone who is not a developer can update content. If you use one, you have to choose between an existing product (Drupal, Joomla, etc) or make your own. As a junior I thought Wordpress was a good choice but as I learned more and used Wordpress more, I realized how bad it was for me. Making my own has the advantage of being just what it needs to be - if the site you are making needs changes only to heading content and paragraph content, then as a developer you can make that happen yourself. You can use a database of course, or you could even just use Node to edit/save to a local JSON file using the Node's FS (File System) APIs. Either way you can make a hidden or password-protected page with a form that allows you (or your customer) to edit and update that content. Then you can solve that problem and it's easy enough for a client to actually use it (versus having your client learn Joomla or something). It's a good level to reach for, but a beginner might have trouble with that. Or you can use a "headless CMS"
Like the author says, it's good to know your options so you don't feel that CMS is the only option. Sometimes you can just add a little money to your project which will buy a little of your time each month if they have updates. Then you don't need a CMS.
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.
You may have missed my point. I will try to expand on it.
That is what i consider that the author is talking about when he is referring to CMSs, not what i consider as CMSs.
You mention databases in trying to illustrate my point, so, trying to expose my view, i would underline some basic ideas. Those being that just by using markdown one is already managing content. That Data is not synonym of database. And managing is not synonym of CRUD.
(Although i must say that CRUD do deserve more understanding and respect than what he has commonly gotten.)
At this time it should be "relatively easy" to create a simple worpress that just use files as data container (ex: use next and markdown or sqlite?). Easy? Just thinking about making and maintaining the plugin system makes me loose hair...
My definition of CMS is way broader than the quote. And I argue, right or wrong, that it is a healthy point of view for devs to have a "correct" vocabulary (not forgetting that it is ever changing). Engineers depend heavily on vocabulary for effective communication.
I do not consider myself in any way as a good example of effective communication (more of the lazy types 😎 ), but In this particular case I am not concerned about experienced devs. They have the "luxury" of engineer scars. I more concerned about "junior devs" confusing simple things and misunderstanding their power to do whatever they need and want with the great tools they have.
(And to not forget also about some common "unfortunate" twitter/youtube/facebook trends that end up loosing all credibility for too many good ideas.)
tltr: CMS is just an acronym for an engineering (marketing, etc) problem and should not be tightly coupled to some tech stack. By "easily" talking of CMSs as worpress (drupal, joomla, ...) we can only loose power in this all connected, uncontrolled world.
I love how you said "Easy? Just thinking about making and maintaining the plugin system makes me loose hair" haha :)
As you know, CMSs are good at managing content so someone who is not a developer can update content. If you use one, you have to choose between an existing product (Drupal, Joomla, etc) or make your own. As a junior I thought Wordpress was a good choice but as I learned more and used Wordpress more, I realized how bad it was for me. Making my own has the advantage of being just what it needs to be - if the site you are making needs changes only to heading content and paragraph content, then as a developer you can make that happen yourself. You can use a database of course, or you could even just use Node to edit/save to a local JSON file using the Node's FS (File System) APIs. Either way you can make a hidden or password-protected page with a form that allows you (or your customer) to edit and update that content. Then you can solve that problem and it's easy enough for a client to actually use it (versus having your client learn Joomla or something). It's a good level to reach for, but a beginner might have trouble with that. Or you can use a "headless CMS"
Like the author says, it's good to know your options so you don't feel that CMS is the only option. Sometimes you can just add a little money to your project which will buy a little of your time each month if they have updates. Then you don't need a CMS.