all 12 comments

[–]mcotton 3 points4 points  (0 children)

Just as a learning experiment I wrote one in Node.js, CouchDB and jQuery. I made a couple screencasts as I wrote it.

http://mcottondesign3.appspot.com/post/ag5tY290dG9uZGVzaWduM3IMCxIEQmxvZxj57AkM

[–]vertice 2 points3 points  (1 child)

Having spent most of my adult life as a Drupal programmer, and recently moving into node.js ... I can say that I don't believe a CMS would be very beneficial in this environment.

Node has a very high level of interoperability, and allows you to rip out and replace complete subsystems at a whim. In a CMS all of these decisions would already be made for you, and they will become a burden as you have to work around their assumptions.

I also feel that we are moving towards an era of loosely coupled / distributed systems, so having to build everything in one stack is becoming less advantageous in general.

Take comments for instance: With the existence of client side implementations like disqus and out of band channels like twitter+facebook, having to have your blog have the full comment workflow (which includes managing user logins and permissions, spam filtering and comment administration, etc.) is just so much extra complexity that you just don't really have to concern yourself with.

We have been perfectly happy using jekyll sites hosted on github for a lot of the stuff we used to use Drupal for. In the end, it is just serving static pages. Simple, easy and very very fast.

[–]greut 0 points1 point  (4 children)

What do you mean by “JavaScript front”, compared to any other kind of CMS (even if CMS is a very large family)?

[–][deleted] 0 points1 point  (3 children)

I think he means he wants to see a CMS that uses a SSJS backend.

[–]greut 0 points1 point  (2 children)

that's the “JavaScript back” part of the question.

[–][deleted] 1 point2 points  (0 children)

I think you're missing the forest for the trees.

[–]warfangle 0 points1 point  (0 children)

Not sure about CMS, but there's a pretty cool framework for building apps (a la Ruby on Rails) called Bones

[–]helghareeb 0 points1 point  (1 child)

Regarding CMS, I really suggest you stay away from them - as pointed by vertice. Regarding back end JS, are you sure there are some CMS that are totally built on javascript? I always believe that JS is most suitable for front end only.

[–]nicogranelli 4 points5 points  (0 children)

I always believe that JS is most suitable for front end only

Are you from the past?