Wow, awesome advice Tom. Thanks sooooo much!
We discussed admin responsibilities a little here. What are your opinions of the interfaces that allow you to make changes on your own? Things like dreamweaver and the like?
With the way this site is going to be, at least the way I want it to be, there are many parts of it that I'm going to want to add to and modify on a regular basis. I can't imagine having to go through someone else every time I want to add an article, change a picture, etc.
Dreamweaver:web development :: personal trainers:fitness
In other words, there are some good sites developed in Dreamweaver, but not many. One of the problems with the code generators is that they let developers create a) atrocious code; and b) sites that can only reasonably be maintained with the right version of the software that created it.
Your second question, about adding and modifying on a regular basis, is where PHP comes in. Basically, you want that part of your site to read from a database, in such a way that you are completely independent of the developer. In other words, it would work just like this forum, where the users can create new content without the intervention of an admin.
This relates to the paper layout of your site. Clearly mark the portions of the site that you want to be "content managed". That way, when the site is laid out, there won't be a lot of rework to build that in.
Since you will undoubtedly be working with images and video, make sure the developer has experience storing and retrieving those media types in a MySql database (MySql is probably the database your developer would use, since it's free, and most ISP's offer it free of charge as well).
One other thing that I just realized:
Today, as you've probably noticed, WLF is extremely unstable. You need to review with your developer what happens when situations like that crop up.
And one other, more technical, item: Ask the developer about the dangers of sql injection. I don't expect you to understand the answer, but if the answer is that it's not a concern, you need to watch out. This
link explains more about it than you would ever want to know. But the basic idea is that since you are going to have a public site with a backend database, you want to make sure you can't get hacked. There are certainly other ways to hack a site, but sql injection is one of the most common and most dangerous.