Looking for insight into the Rails Way of handling views

I've been developing rails apps for a couple of years now and I must
say that I think it is a great way to build web apps. Rails is
constantly evolving as are the lines of thinking / features /
practices / conventions, etc. As Rails evolves, it is important to
decide what to adopt. Some things I adopt right away and others I try
to monitor and see what happens. Historically, I have found that
views / erb have been the one area leaving me scratching my head on
the approach to development and more importantly the maintenance of an
app. Especially large applications. My current method is using a
custom scaffold generator to generate views that utilize a custom code
base that helps deliver the html. The code in the views adheres to
The Rails Way and works great, but, I have been building apps this way
for a while and have kept a close eye on how things have evolved.

I'm at a point where I need to make a decision on how to design views
for my apps moving forward. I'm looking for insight as to the current
line of thinking / convention for handling views in rails.

What is the current "Rails Way" to design views?

What direction is Rails moving with regard to views?

You might want to send your message to rails-talk
(http://groups.google.com/group/rubyonrails-talk)

As far as direction goes... nothing is really changing.