React, Flux, GraphQL, Hack, HHVM...? All of this and more!
Content management is an absolutely huge market, where the largest number of sites are more or less straightforward business card sites with some integrations. Open Source WCMS products like WordPress and Joomla! are household names where as more heavy weight tools are not that known among consumers.
The challenge for content management system developers at this level is that they are essentially a dime-a-dozen offering. They all essentially do the same thing as WordPress and a large number of other tools do.
On the other end of the CMS scale are enterprise level systems. These are often rather complex and sometimes downright archaic monoliths that are a pain to use and customize. These tools are often used across continents by hundreds of people. The products are supported by large ecosystems that offer integration modules to other enterprise software.
While some of these applications are truly on life support, many are still decent to use and develop. In fact many of them are continually refactored within their Java, .NET or PHP codebases. The advantage that many of these tools have on their side is stability and features. Many of the CMSes listed earlier have already fizzled down, while many older tools have renewed significantly.
While creating a Node.js and MongoDB powered CMS with an excellent user interface might be (relatively) trivial, but building the features that are de-facto requirements in many web content management projects continues to be a a challenge: multisite, multilingual, expandable APIs, versioning, audit trails, user and permissions management...
At this point in time there are no credible Node.js content management system players that would have something that would be comparable to something like SiteCore or even Drupal. With a CMS implementation project the assumption is that developers get a large number of features for free and there is a large pool of developers available.
Though as the world continues to be evolving, it might be that the golden age of large monolithic CMSes has already peaked. In the future content might simply be published by more lightweight tools then they currently are.
There is still complexity to be managed behind large numbers of people managing a content repository. This is why an oldschool monolith CMSes like Drupal or SiteCore might end up being the software that is walled of the public internet, only exposing their data via a GraphQL or REST API.
So it might well be that there will be no killer Enterprise Node.js CMS, but the old systems will work in the background just like ERP and PIM systems power many web sites today.Tweet