Modern CMS (built with Node / Meteor)

We’re about to replace a few old static websites with a CMS and looking at the top contenders - while we’d love to not work in PHP anymore sadly the top open CMS’s seem to still be Wordpress & Drupal even after all these years.

We’re already using Meteor for another project - I really wish there was a promising up-and-coming CMS written on more modern technology. I know there are hundreds (thousands?) of small CMS projects but is there a modern one that might be a true potential leader? I’ve been looking at the stats at for CMS trends but it’s been inconclusive.


Hi Monaco,

I find myself in exactly the same situation that you have described and I’m just trying to evaluate the current situation with production ready Meteor CMS solutions such as orionjs.

Did you got with a Meteor solution or have to fall back to Wordpress etc?


Hi there. I have been doing a hybrid workflow from Node.js to WordPress. And what a disappointment when it hits that PHP/MySQL layer. I just discovered Angular - Meteor and want to dive right in. However, I have been asking about this CMS issue.

I wonder if I am going to be building the admin, authentication, etc. by hand, piece by piece. Is it a comprehensive service? Perhaps, it is easy enough. It’s true, I don’t want a huge and heavy overhead (like WordPress) in order to just authenticate and control content. Just not sure how much of a hackathon the Angular - Meteor solution can be.

Pretty basic concern here. Wondering if you brilliant Angular - Meteor programmers out there have any illumination you can shine on this issue.

Thank you so much!

You could always do the admin with OrionJS and the “site” in angular

I just now discovered that the having the latest version of Orion installed completely breaks any site, but only in IE10. Very strange.

Hi Everyone,

TLDR: Check out and

I also had the same problem when it came to creating static portfolio sites using Meteor. I have built a couple of them now and in my early days of development, I was creating json files to store content.

I started using a content management platform called Contentful and it works really well for simple content. You use their platform to define your content and then you can fetch it formatted as JSON - nice and simple separation of concerns. They have a webhook feature so they post updated content as a payload back to you - use node express to listen for it.

I am working on a meteor package that takes care of fetching content, resizing images and listening for incoming changes, so your meteor app is updated in real time when changes are made.

If anyone would like to have a look, try it out and give feedback that would be great. You can find it on atmosphere at and I will be retrofitting it to a few portfolio based sites I am working on, but would love to see how it could benefit other people too.


I fail to see how building a site with a backend to control content is different from creating any other kind of app. I recommend regardless.

1 Like

I’ve hit this issue as well. But I’m so sick of WordPress, Drupal, etc that I really started thinking about what role I needed a CMS to play. In one project it turned out all I needed was a doc store and a way to approve submitted content. I was able to use email actions and server routes for that. That all said, I’ve also learned that rolling your own CMS in Meteor isn’t that bad. At first getting user roles down or any relationship can be daunting but as I went along it just became pretty quick. Ive been on a lucky streak of being able to ditch bloated CMSs for Meteor and hoping to continue. Oriojs is a fantastic package if they can get the IE issue resolved. But take a look at the packages that make orionjs up and you can start to piece together your own CMS pretty quickly. If you do find a great prebuikt solution please share!

I looked at contentful a few months back for a CMS we need to build. I didn’t really get it. Why pay $99 per month to store your blog content on some third-party site, and write all the extra code to push and pull data from them via an API, when you could just store the blog content in your own application’s mongodb? Doesn’t the extra overhead of making API calls to load content come with a performance penalty? Doesn’t it kill Meteor’s reactivity?

Those were my initial thoughts and concerns. Could you possibly help me understand the value proposition better?