This is the current intro to the templating system:
The template system is designed to be used by two classes of users: programmers and designers. In bulding a web site, programmers are generally responsible for defining and implementing the application logic of the site, while designers are more responsible for the presentation. Generally speaking, the application logic generates data for the presentation to display to the user. The template system must provide mechanisms that supports both of these tasks and allows the designer and programmer to work seperately, but for their work to be combined at runtime into something that the user sees as a single page.
My suggestion would be to add a third party, the folks that will be using it in the end, and that are looking for relatively easy sollutions for everyday problems. Afterall those are the folks that will contact designers. A kind of reverse communication maybe, but if OpenACS gains momentum, not ilogical. I am getting this kind of questions from corporate secretaries for example, neither developer, nor designer, but faced with a question form a "pointed headed boss", hey Jane, just get this solved.... If the secretary would be able to play around, and than walk into the designers office to ask for a professional update, that would be great.
