You might also be interested in: https://github.com/deoxxa/node-ginger https://github.com/deoxxa/node-ginger https://github.com/chrisdickinson/plate https://g

You might also be interested in: https://github.com/deoxxa/node-ginger https://github.com/deoxxa/node-ginger https://github.com/chrisdickinson/plate https://github.com/chrisdickinson/plate https://github.com/paularmstrong/swig https://github.com/paularmstrong/swig Sounds like my reasons for liking Jade are the same as yours for not liking it: simplicity, but for me, as opposed to someone who only knows HTML. The trade-off for requiring less typing in some cases (which is a bonus, but not a goal) via significant whitespace and being element-based is having many fiddly moments trying to get whitespace to appear between elements where its lack affects the layout. I've loved Django's template inheritance since I first laid my eyes on their template docs in the magic-removal days, so once Jade added the same sort of inheritance - plus conveniences like "append" for adding to blocks in parent templates - the deal was pretty much sealed for my Node.js projects. Form rendering and other truly display logic is the point where I part with the appreciation Django gave me for designer-friendly templates which just can't do logic beyond the basics. Jade's mixins, effectively being functions which can only return elements, but allowing you to optionally pass in arguments, attributes and a block of elements, and use JavaScript logic, are getting me most of the way there when using my JavaScript port of django.forms, without having to step outside the templating system.