You should maintain your own page. You should add content, update products, portfolio items, etc. Why? Because you actually know what should be there. I probably don't have any idea, because I'm not you, I don't have your skills, and I might have an idea of your vision, but I probably don't have the vision itself.

Just like navigation should be flat, so too should the hierarchy of people's responsibilities and duties. If something is updated on the website, someone has to decide this. When they make that decision, it is often easiest for them to implement it as well.

And when the website changes, probably other things have to be updated at the same time -- a contact list probably exists on paper just like on the website. Having a flat hierarchy of responsibility and duty means that one responsible person should be able to make all these changes themselves, without going through anyone else.

To make this possible, I always make administrative interfaces to web pages. If a document gets changed by someone, they should know how to change it themselves, and I'll find a way to do that. Maybe with a form on a website, maybe by allowing them to edit the page (or parts of it) in Dreamweaver or FrontPage, maybe even just by working through Word.

I can't make the entire site accessible to every person of every skill, but I first try to figure out who needs to do what and then abstract those parts of the page that need to be maintained.

I feel it is important not to make every part instantly accessible to everyone. It is not necessary or beneficial for all parts of the site to be exposed -- not just for security, but also for quality of results. To the degree possible, policy should be implemented in the programming code, because programming code never forgets to review the policy. A common example is the look and feel of the site -- color schemes, navigation, etc. It is best not to allow this to be changed arbitrarily, because then the website can become fragmented as the look is changed in small ways over time.