If you are referring to having a menyu like "Edit News", "Edit events", type of CMS, and you are making templates to edit each type of item then this is always going to be your problem.
Instead you have just one CMS edit template and store all content in one place, specifying which section the content is for. A Title, a teaser etc, and you can add extra fields according to the section if you like. > -----Original Message----- > From: Dave Phipps [mailto:[EMAIL PROTECTED]] > Sent: 14 January 2003 11:37 > To: ColdFusion User group > Subject: [ cf-dev ] Digging for information > > > Hi, > > I am about to begin the early stages of a new site management > system which > will supersede our current CMS. One of the major problems we > have found is > that the product is very hard to port to different sites > because of the > menu systems that each site uses is slightly different and > our old system > generates menus, submenus and pages dynamically based upon > the content > which requires me to re-write the navigation code base for > each project. > > How do most CMSs handle the menu/navigation of dynamically > generated content? > > Any suggestions or helpful pointers would be most appreciated. > > If you want to see an example of a site running our system > then take a look > at www.abingdon.org.uk. > The main categories at the top are the only fixed navigation. > All the > other menus are generated based on the content in the db. > > Is there a better way to do this? > > MTIA > > Dave > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] For human help, e-mail: > [EMAIL PROTECTED] > > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
