Hi Bryan, ..but that's what JSP is designed to be... html developer friendly. Once you create the page with all of the struts tags, they should just be able to code the html and content around the JSP. I know it's not exactly what you were expecting, but my suggestion would be to let them modify the JSP, just instruct them that they are not supposed to touch the JSP tags.
Kenny Smith JournalScape.com -----Original Message----- From: Bryan Field-Elliot [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 1:09 PM To: Struts Users Mailing List Subject: content management ideas? I was wondering how people handle frequent content updates with Struts/JSP? At my company, I'm building a site for which much of the "static" content (including things like the CSS stylesheet) will probably undergo frequent revision. I'd like to open it up for easier access, such as via FrontPage, so that I (the programmer) am not in the middle of such changes. But the site is very dynamic, with almost all page fetches resulting in a database query and dynamic content being built. So the site needs to be JSP-based, and I don't want the aforementioned "Frontpagers" modifying the raw JSP pages. Opinions appreciated on how this compromise can best be reached, Bryan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
