by Durant Imboden » May 23rd, 2009, 7:00 pm
>>The advantage is that my Content is always separate from the Design of the site (the look, feel, layout).<<
You can achieve the same thing with CSS-based Dynamic Web Templates in Expression Web, and I'm sure you can do it in Dreamweaver, too.
One advantage of the "flat file" approach is that you don't need add-ons, security patches, modules, etc. to create and manage a successful site that does exactly what you want it to do. It can also be quicker to enter titles, descriptions, keywords, etc. in code view than by filling in blanks.
For example, on our site (which is maintained for the most part in FrontPage 2003), I use several basic editorial templates into which I can just start typing, entering photos, and so on in much the same way as I'd do it in Microsoft Word. I save the page with a search-friendly file name ("widget-railroad-tickets.htm" or whatever), click the "code view" tab, and add text on the title, meta="description," and meta="keywords" lines. The whole process takes only a few seconds, after which I'm ready to write the page, insert any photos that I want to use, and save the file for publishing after I've previewed the page to make sure everything works correctly.
Just as important, "flat files" are inexpensive to host and put a very small load on the server, which translates into fast display times--even if you've got thousands of pages and are serving well over a million page views per month.
I've worked with flat files and CMSes, and as someone with an editorial background, I much prefer the flat-file approach. Other people (especially those who are able to visualize their sites as collections of database records and don't need to create new menus or paths on the fly) may have a different opinion. I think it's worth experimenting with different approaches to find what best fits your own personal style and publishing needs.