I have an overlooked point on the "Handling Static and Dynamic Pages" thread that I'd
like to discuss. A majority of sites appear to be built as files. That's also
generally true of Fusebox dsp files. Each page is a distinct html, cfm or whatever
file. However, I've seen some that employ a template and a "page ID".
www.example.com/aboutus/stuff.cfm vs. www.example.com/index.cfm?pageid=42
The pageID method can work well for iterative content like press releases, daily
announcements, etc. But why not use it for an entire site? A pageID method could be
used to support a "web site in a box" or content management system to allow not
technical staff to create new pages.
A pure pageID system could support dynamic site navigation which would also update as
pages are added and removed. I've seen this in a "web site in a box" solution where
all of the navigation elements are built out of HTML.
Aside from development time and server overhead, what disadvantages would a pageID
site building method have vs. file based?
Thoughts? Opinions? Any personal experiences?
Tom Briscoe
Web Developer
Compass Bank
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
