4 ms·
The thing with flat-file cms is, they are often represented as a category of cms, but they are actually not all the same. There is the type that just saves its
by Grumbledour 6y ago
The thing with flat-file cms is, they are often represented as a category of cms, but they are actually not all the same.
There is the type that just saves its data in file form, just like you would in a db. And I never get why this would be desirable. You loose all the benefits of a db system without gaining much.
The other type, the interesting one, is the one where you can work directly on those flat files, not needing some kind of admin interface. Now this can be great!
But it often seems more flat-file cms belong to the former category. I do not know why one would prefer these if you still need a server with a dynamic language and a web interface to edit content. Just use a db!
I never heard of headless API CMS Systems before, but it honestly sound really silly. If you write a front end that consumes JSON, you could just as well write a front end that made db calls. And if you must have JSON, write a wrapper around your db. Having that stuff hosted by someone else is just peak cloud nonsense.
- nsomaru 6y agoIs there a pattern that securely allows JS clients to make arbitrary SQL queries? Or is this a feature of REST? Maybe this is why people invented GraphQL? But then that comes with its own issues... Either way, is it as simple as you’re making it out to be?
- Grumbledour 6y agoI would argue if your frontend is just a js client with no server component you are already doing it wrong. Of course, that then becomes a much bigger discussion about websites vs apps and the current state of the web which we have on here quite regularly.
- z3t4 6y agoEverything becomes more simple if the content is static/immutable as long as it's small... The advance in networking and device storage has made this feasible. Rather then requesting what you need, you get the whole database sent to you and stored locally.
- wolfhumble 6y ago> The other type, the interesting one, is the one where you can work directly on those flat files, not needing some kind of admin interface. Now this can be great! I am not sure I understand; could you please explain? That sounds like working directly on flat html files; or are you talking about working directly with a DB that then writes to flat files? Thanks!
- mahesh_rm 6y agoThink about a api.json file served by s3, which you can openn with vscode, and update. Your html fetches it's content through xhr.
- Grumbledour 6y agoI was thinking about something like grav cms. You put markdown files in a folder and it creates html for you when the page is requested. When you use their web based admin tools, they also just change the markdown files. Easy to use from web and local. I guess many static site generators work the same and we had good success teaching our content creators some markdown. For many, it is often easier than navigating something like drupal and working with the kinks of whatever WYSIWYG editor.