So, in my original CMS I applied RainTPL server side tempates to render HTML in PHP. When a did a little investigation about a good library to serve HTML templates at server side, Ijound node.js .. and then backbone.js .. and underscore.js, haml templates, T.js templates, middelware layers from jQuery, moTools, Ember.js, Mustache, Modernize, Eco templates, Handlebasrs … arghhhhh
Then I found CouchDB in one side and distal (Dynamic Interface Simplified with Template Attribute Language) at the other side. I thinked that, I could bind the dynamic CouchDB JSON content (important, these content will not be indexed by search engines) into distal templates with almost no work.
But then I found backbone.js …. and ember.js, supporting and … the Bindings, the Computed properties, the Auto-updating templates,
Well, then I think … WOW … those all new libs and techniques … a good CMS will need these so .. YaCMS could be refactorized.
The “hell” ;) was on for some days more with things like:
Front side: Underscore.js + (T.js OR handlebars.js) not SEO friendly, …. complicated and dependency on more libs
Ember.js I like it, i’ll use that. Little Doctrine code can return JSON easily. I mounted a mongodb nosql server too, it’s easy.
I did a little coffeescript experiment published at this blog, and with an online demo ;)
Then a friend @mdaguete talked about Scala and Kneex … ufff my brain is about to explode ….. let’s center the thing .. I want a good server side LIGHT template engine .. i’ll keep RainTPL
Server side: RainTPL … .but then …. i see mustache.php and i like it …. this it’s a hell really … i’ll have to try mustache too.
At this point:
I had published a very rough and basic copy from the original YaCMS … i’m “building” a very basic cms just for fun, so ,,, lets go and dont use any template engine …. well.write a minimal template engine object only and focus cms on extensibility