I have a client who has no knowledge about web site design and wants me to redesign his present website which was done long time back using Tables and very little css. He also wants his website to be viewed in three main devices (Mobile, iPad and Desktop). He has asked me to mail him several points such as Objectives, quotes, timeline etc., and one of them is Documentation.
What type of documentation should I give him? Should I give him a detail Doc file or some general one, which he can’t use it for getting a quote from other web designers.
The others things listed are forms of documentation unless he means a legally binding contract - if not ask them to clarify. To me it sounds they just want you to give a time frame and general outline as how you can help them achieve the objectives of converting the website and a rough project plan.
You could put the ball back into his court and ask for a description of the required documentation.
Or provide a list of items that can be documented such as
List of all files
Overview of technologies used (Static HTML, SSI, PHP, ASP, MySQL, javascript, CSS etc.)
Commented code
Source details of 3rd party elements e.g. scripts and stock images
Explanation of CSS validation errors due to hacks or vendor-specific properties (hopefully your HTML will be valid).
Usernames and passwords for FTP etc.
The WHOIS for the domain, if you are handling registration
Changelog
It’s for you to choose how transparent to be.
If you’ll be involved with the site long term, it’s also good to seek agreement from the client concerning any 3rd party involvement with the site. If, for example, they employ someone to make alterations for SEO, that person should agree to preserve all functionality, validation and cross-browser compatibility, to state times when they will be working on the site, and supply both you and the client with a changelog. I’ve known such “experts” wreak havoc.