It might be a good idea to store the information in a db anyway. Scheduled
routines could be created to write static pages using the content in the db.
This would allow for easier editing, versioning, and
syndication/distribution. Using static pages would require a heck of a lot
of parsing and integration with XML to make the content more accessible
seperate from the presentation.
Steve
-----Original Message-----
From: Seth Petry-Johnson [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 03, 2000 7:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Content management
> I store just about all of the content in a database, and have an
> administrative interface where the owner can change the text on each page.
> This is password protected.
I'm going to do something similar, although I'm going to write the user
specified text to a file and CFINCLUDE it, rather than doing a database
query. For sites where the content isn't changing more than a few times a
month, it seems rather inefficient to keep hitting the database over and
over.
Thanks for the thoughts,
Seth Petry-Johnson
Argo Enterprise and Associates
----------------------------------------------------------------------------
--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
