I think a couple of other comments here have the right perspective (multiple, so I'm not commenting as a child to any particular one). First, assess where the

I think a couple of other comments here have the right perspective (multiple, so I'm not commenting as a child to any particular one). First, assess where the intended user(s) is at and what they can and will realistically do, and not do. As a favor to a relative, I once revised a business's static site to use a CMS. Pretty simple stuff. But it turned out that the business partners, while claiming they wanted to be able to edit/update the site themselves, simply refused to look at the prototype and the pretty clear documentation I'd written up -- screen shots and all. They said they wanted to be able to update the site themselves. What they apparently really wanted was to be able to tell someone to update the site and have it happen quickly. Well... that's what you pay a web developer or assistant for, on an ongoing basis. They weren't so into the paying part (aside from my relative -- also, I wasn't particularly looking for a standing content-maintenance gig). Assess where your customer is at. Make sure you're really on the same page, and that they are willing to take the required initiative.