Cameron McBride wrote:
>>Amrita for templating. http://amrita.sourceforge.jp/
> 
> 
> +1  I'm also a big amrita fan.
> 
> 
>>What I like about it is that it keeps the HTML in the template and the
>>Ruby in the script. To me that feels extremely clean (and because it's
>>well done it's also fairly flexible). Took literally minutes to learn to
>>use, too.
> 
> 
> Being able to design the look of a site in standard HTML and CSS, then
> just dropping it into the correct file has felt clean and simple. 
> Since I'm usually time crunched, it's also a nice mental relief that
> it's an easy fix if someone disagree's with my design choice (God
> knows I've made some ugle things, I'm no artist).  With Amrita, I can
> just tell them to make a new template using what they know and just
> put the correct 'id' tags in.
> 
> Like Michael said, the logic stays in ruby and the design stays in
> HTML (fwiw, I use redcloth/bluecloth for content).  no funky hybrid
> templates.
> 
> Cameron
> 
> 
Amrita, how is the performace? And, how do you handle the security for a 
more serious interactive website? Thanks