5 ms·
If only it wasn't built with PHP. We need a batteries included, non-headless, open source CMS for Node.js. Headless is pointless for the vast majority of use c
by 65 3y ago
If only it wasn't built with PHP. We need a batteries included, non-headless, open source CMS for Node.js.
Headless is pointless for the vast majority of use cases, so I don't really understand why Node.js developers keep making them.
It's funny how CMSs follow the same design patterns based on the language. PHP CMSs are generally the same, Node.js CMSs are generally the same.
- pathartl 3y agoHow about .NET?
- vorpalhex 3y agoHeadless cms + static site generator. All the pros of a tiny, static website and all the pros of a cms system and dynamic content. Scale to millions of visitors for a couple of dollars.
- anditherobot 3y agoBecause PHP is bad or because you personally don't like PHP?
- xupybd 3y agoI think they just want it in Node.
- sacnoradhq 3y agoRewrite it in* Maybe in a utopian future, there will be a universal seamless ABI for most dynamic and static languages such that rewriting will be both unnecessary and undesirable.
- tonetheman 3y ago[dead]
- omneity 3y agoThe closest I could get is Sveltekit + Supabase + a custom editor/svelte renderer for my website at https://omarkama.li https://omarkama.li I think there’s room for a solution that offers all this in a single package.
- TheCapeGreek 3y agoI agree. As a PHP dev it seems to me that the JS world is stuck on reinventing every kind of wheel for every kind of project. From what my view as an outsider, it seems that there just isn't as much conglomeration around big projects as there is in PHP/Ruby/etc, or there are many more projects and there haven't been a "sacred few" as winners yet outside of frontend frameworks. In PHP, I can reliably stick myself in a Laravel/Symfony/Wordpress camp and the framework will either have most of what I need, or the ecosystem will have packages for it that get the job done. In JS, the projects that accomplish the same either don't have much publicity or there's some other blocker. In other words, where is Wordpress.js? Solve an entire problem for an end user, not just a fellow developer who can operate a terminal.
- ilyt 3y ago> I agree. As a PHP dev it seems to me that the JS world is stuck on reinventing every kind of wheel for every kind of project. Kettle, met pot lmfao. JS succeeded PHP language as "the first language most developers will most likely experience" and it came with a lot of newbies reinventing wheels with it.
- sacnoradhq 3y agoIt's depressing when there's excessive imitation without differentiation leading to lack of innovation and too many similar options that lack advantages. In case people were wondering: https://en.wikipedia.org/wiki/Headless_content_management_system https://en.wikipedia.org/wiki/Headless_content_management_sy... Most small shops and individuals want an integrated CMS that has an admin interface AND serves the content while handling content versioning, storage, and publication. If a site grew, then it might be worth revisiting which components should be separated.
- tobimori 3y agoA Node CMS is not market-ready. Try to deploy Node on any cheap shared hoster - it either won't work, have a huge cold start because of Plesk, or not be offered at all. Something like Ghost is impossible to be installed on a shared hoster. Then why should I use an inferior technology to build a site when I can use PHP that runs on any shit server, at good performance?