Bryan, I am sure there are many suggestions. I will convey what has worked for us in practice. Our site utilizes our Struts based content management system (CMS) called eContent. Since much of our site is dynamically generated our users update dynamic content via the CMS directly. Basically a resource can be comprised of defined "attributes" which are pieces of data related to the one resource. An example of this is any of our project summary pages: where each piece of data on the summary page is an attribute of a project, i.e. Description, Stable version, License, Status etc. The formatting is done by a template.
If formatting changes are desired, a request for change is made or for more detailed changes a mockup is provided to the administrator to modify the template. Static content is edited in Webphere Studio and is either uploaded directly to the site or via the CMS system (the later when the page/content requires authentication to access onsite). When uploaded via the CMS, we sometimes utilize a workflow process, i.e. for verification before publishing; or to ensure the file is checked into CVS as the case may be. Hope this is helpful. Regards -- Sandra Cann http://www.jcorporate.com Open Standards based Java components "Our separation from each other is an optical illusion of consciousness." (Albert Einstein) > -----Original Message----- > From: Bryan Field-Elliot [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 12, 2002 4: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]>
