Hail thelist-

We're in the architecture phase of a new EDI system that will use JSP.  As the UI person, I'll be working primarily on the presentation aspect of the system, as opposed to the logic portion.  I've been asked to get things rolling on the topic of design and coding strategy.  Meaning, how we can best separate layout/format (html/css) from content (scripts) in the JSP environment (this is possible, isn't it?) and still have intelligent workflow between designers and coders, with maintenance being a big concern.  We want to make it very easy for designers to tweak the presentation later, without having to mess around with the scripts that make the system go.  How's that for technospeak? :)

This place has been a mainframe shop, and so JSP is new technology for most of the people here.   I know a little about ASP and I'm giving myself a crash course on JSP this week.  I won't be strategizing alone, but I do have to sort of coordinate people's thinking about this new way of working.  So while I'm reading and researching other sources, I'm interested in hearing any real-world experience you all might have.  Are there any pitfalls we should watch out for?  Any best practices that you've learned the hard way?  Resources you'd recommend?  I'd appreciate hearing any thoughts.

Thanks in advance...
Peggy Daniels
peg@anxietygirl.com
today's anxiety: new job = over my head?