using includes from the beginning, but your mileage might vary.
This is how I find library items useful at least for HTML sites: I use
library items for certain items I want to have consistent during development
but know will change just before site launch. For example nav bars:
Home | Products | About Us | Contact
I place the library item on all pages. If the client wants to change "About
Us" to "About" or change the graphics used for the rollover images, I change
the library item once and the change is made on all pages containing that
library item throughout the site. Just before launching the site, I go to
each page, detach the library item and on the Home page, remove the link to
home; on the Products page, I remove the link to products, etc.
In other words, during the development I can easily keep the styles and
verbiage consistent across pages and only need to deal with removing the
links (so pages don't link to themselves) at the end. Yes, I still have to
eventually deal with each page individually but I only do that once. Unless
you're using some fancy server-side logic, you can't do this with SSI or
cfincludes...and again, I typically do this with straight HTML (not CFM)
sites.
-------------
Regards,
Bob Haroche
O n P o i n t S o l u t i o n s
www.OnPointSolutions.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
