Originally posted by: notfred
Originally posted by: BingBongWongFooey
Originally posted by: notfred
Originally posted by: BingBongWongFooey
If some paltry include()s are bogging down your webserver, you could just have a script that creates a static page, which updates via cron or whatever.
How would that possibly be better than having dreamweaver do it when the files are updated?
Perhaps it's not, I guess the idea of relying on some big expensive gui program for maintiaining a website just seems strange to me.
Well, if you want to consider my site:
There's at least 10 or 12 people who contribute information to the site. None of them know PHP. About half know HTML. Dreamweaver allows users to check out files off the site, so that two peoplea ren't editing the same file at the same time. WYSIWYG editors are easy to use, especially for those people that don't know HTML.
We have thousands of HTML files that predate the existance of the first PHP interpreter. When an email address changes at the bottom of most of those files, dreamweaver makes global search and replace simple.