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.
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.
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.
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.
In case people were wondering: 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.
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.
I think there’s room for a solution that offers all this in a single package.