One Struts content managment is basicPortal.sf.net. V. Hajratwala, Nayan (N.) wrote: > Unfortunately, I don't believe this is a very practical approach. > > A content editor may inadvertantly make a change to a tag without even > noticing it (search & replace, fat-finger, etc). Then after they upload > their change to the server and spend a few hours trying to figure out why it > is displaying an error, they call you, the developer to debug the problem. > You then compare the previous version (you are using source control, right?) > with the modified version to see what the problem is... yada-yada. > > We use an approach of having a template which contains all of our "base" > html .. header, footer, etc. The content editors can create whatever they > want (we encourage valid XHTML, but usually don't get anything for our > efforts), and upload it to the test servers. Our framework then pulls the > content into the template via a custom tag (using java.io.*). > > Hope this helps... Happy to provide more details if you need. > > --- > - Nayan Hajratwala > - Chikli Consulting LLC > - http://www.chikli.com > > > -----Original Message----- > From: Kenny Smith [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 12, 2002 4:01 PM > To: Struts Users Mailing List > Subject: RE: content management ideas? > > > 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]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
