Why All Existing JS CMS Solutions are Shit

This article explains, in moderate detail, why I am starting to build an open source Node + Express + Angular CMS, called NG Express CMS.

The answer is that all existing alternatives are shit, so I need to make one from scratch.

1. Contents

  1. Contents
  2. Existing Angular Solutions
    1. Why Angular CMS is shit
    2. Why Butter CMS and Cosmic CMS are shit
    3. Why Respond 6 is shit
  3. Existing Express Solutions
    1. Why Ghost is shit
    2. Why KeystoneJS is shit
    3. Why Enduro is shit
    4. Why ApostropheCMS is shit
  4. Why Express and not something else?
  5. Why Angular and not React or Vue?
  6. What exactly makes a non-shitty CMS anyway?

 

2. Existing Angular Solutions

2.1 Why Angular CMS is shit

Because the fucking repo itself says it’s broken. It also requires Mongo. It uses grunt. I truly saved the best for last: It’s not even Angular, it’s AngularJS / 1.x. The grunt templating library it uses is out of date.

2.2 Why Butter CMS and Cosmic CMS are shit

Tbh they are kind of cool, but they are expensive af. They are not open source and require monthly payments. Because of the whole money situation I haven’t really used them, but since the back end is closed source I doubt they are extendable on the back end, and I’m not sure they have server side rendering.

2.3 Why Respond 6 is shit

It’s cool that it’s open source, but the back end is PHP. Who even uses PHP? (Says dude on WP blog.)

Honestly, if you are going for Respond, why not go for WordPress? WordPress is cool, but again, it’s PHP. I want a full-stack JS CMS.

 

3. Existing Express Solutions

3.1 Why Ghost is shit

If you have a small, specific use case, Ghost is awesome, but this is exactly why it’s shit. It uses markdown, not arbitrary HTML, for the UI. It uses Grunt, not Webpack. It Handlebars for templating, which means the front end templating engine is not integrated to state, giving you more syntax to deal with. It also means the back end and front end are not tightly integrated nor as modern as the most modern frameworks (Vue, React, and Angular).

To it’s credit, it has partial server side rendering and some other cool stuff.

3.2 Why KeystoneJS is shit

It doesn’t work with SQL and it doesn’t integrate with the latest frameworks. I dropped KeystoneJS when the CLI tool asked me this:

Inline image

KeystoneJS Beta is super cool for one reason…They have re-written the admin UI to use React. This Beta is still not the official latest release, but like, why. It’s a billion times better than v3.x.

Honestly, keep an eye out for this. Once Keystone is fully reactive, not just UI, it will be a contender. I still want it to be SQL-compatible, but I would rather hack an all-React Keystone to use SQL instead of building a competitor from the ground up.

As I said on this GitHub issue:

…Here’s a big deal for ya, Keystone: Some contracts (eg multimillion dollar DOD contracts) are locked into web development without allowing DB change. Guess what? Legacy DBs are SQL.

Also, SQL definitely has its use cases. Any time data loss is unacceptable, full ACID is required (including complex, mult-doc transactions), or a well-defined schema will be utilized for heavy computation including aggregate statistical reports. Or, when you have a team of developers that no SQL and don’t know NoSQL (say that 10x fast)

https://www.reddit.com/r/mongodb/comments/43m2om/how_exactly_does_mongodb_lose_data_and_is_it/

https://stackoverflow.com/questions/7149890/what-does-mongodb-not-being-acid-compliant-really-mean

As a principle developer on such a DOD contract, the main reason I am not suggesting Keystone is SQL incompatibility. (also I’d like to see React in the public ui, not just admin ui, but that is minor and we would be able to mod that)

 

3.3 Why Enduro is shit

It uses Handlebars for templating and AngularJS / 1.x. This is basically obsolete compared to using modern Angular (v4+), or Vue. (Or React + some state manager like Redux, Angular and Vue are much more similar to AngularJS / 1.x.)

It does have Gulp and Sass, which is pretty dope. I’d still rather see Webpack and Sass. It also has server-side rendering, but by not using the latest frameworks the server-side integration cannot very effectively share code, state, or build configuration with the UI.

 

3.4 Why ApostropheCMS is shit

Nunjucks and Less? Wut? It’s also NoSQL / Mongo. It also doesn’t have full-stack React/Angular/Vue.

 

4. Why Express and not something else?

I want to be able to develop the server and client using JavaScript and probably even sharing code or state. I need full stack JavaScript to get the most out of the JavaScript ecosystem. This includes build tools, server side rendering, and more. Having a full-stack JS CMS allows a developer to master the full stack by learning a single language, and it provides for easier configuration and maintenance. PHP will never be a client language, so full stack means it needs to be JS. As if that weren’t already a nail in the coffin (it was), Node is also way faster than PHP.

There are other Node server solutions, but Express is the go-to in the community. The other solutions do have some advantages, it’s not like they’re all shit. Koa, for example, is cool, but no one uses it. Why does it matter that no one uses it? Because there are no ready-made plugins, extensions, and integrations for other JS libraries. Express has a massive network effect, and in particular it has a ton of plugins for Angular and Webpack which I am using, and a ton of documentation on basically every use case. Lastly, I’ve used Express alot in the past and I love it.

 

5. Why Angular and not React or Vue?

Finally, a good question. Actually I like all three options, and I like Angular the least among the three. So why Angular?

Because my company wants to use Angular, so I imagine I will be most skilled with it here shortly. I’m just picking the one I have the most skill in.

At the same time, I do have another project where I’m kind of doing a similar thing (rescopl) in Vue, and once asynchronous components in React come out I will probably at least try that out.

 

6. What exactly makes a non-shitty CMS anyway?

This is less a description of the perfect CMS and more a description of what I am building. What I am building is not shitty, but you can build other stuff without being shitty. What I am building:

  1. Renders stupid fast because of Server-Side Rendering
  2. Search Engine Optimized, also because of Server-Side Rendering
  3. Built on the latest version of Express, the back end pillar of our JS ecosystem
  4. Built on the latest version of Angular, one of the front end pillars of our JS ecosystem
  5. Works with SQL and NoSQL
  6. Free and Open Source
  7. Does the CMS things: authentication, write, tag, save, schedule, publish, and modify with plugins.
  • 3
  •  
  •  
  •  

Leave a Comment