When you embark on starting your web design there are two competing temptations.  To automate and make dynamic as much of the content as possible holds the allure of having the site take on a life of its own.  Allow users to contribute and you might get out of writing a web page ever again (dream on).  The other hand holds the getting to market faster and cheaper because dynamic content costs more in time and often money (programmers are not typically cheap). 

When you have static content there are those that argue that it makes it easier for you to get good search engine positioning and while the jury is out on that assertion, most people can whip out html with tools like your standard word processer whereas dynamic content typcially involves databases and very talented programmers to make even the first page display.

A solid and proven compromise is to start your web design and architecture by putting up a HTML page or two and then pin dynamic and static content onto that base as time goes on.  This gives you cheap and fast when you need it and still leaves you open to leveraging the power of dynamic technologies like ASP, ASP.Net, JSP and PHP to allow you to scale to thousands of pages tailored to the actions of your users.