Here Here!

I believe too many programmers don't think enough about division of labour issues like this.

When doing any Application + Templates type work, you should be looking to seperate form and function as much as possible. And this often means making your templating system as stupid, simple and web designer friendly as possible.

Ideally, you want to be able to write your application code anyway you like and have ex-receptionist-web-designer-who-doesn't-know-HTML-but-can-work Dreamweaver, or clueless-Marketing-Director-that-likes-to-tweak-the-copy-on-pages, to be able to make changes here and there and not be able to break it. Having other people doing non Perl related things is GOOD!

For the next step, they should also be able to use things like Dreamweaver Templates and Library items across both the static website AND your dynamic templates and have it "just work"

Get something like this working well, and your designers will love you, and be much more efficient too. Hey, we have to compete with India somehow, and the more efficient your people are, the less likely the role is to be shipped offshore. :)

It's also the primary reason that I've been saying for years that ASP/JSP/PHP or any other server page type languages don't scale up enough, because it's way to easy for the above mentioned people to break it.