Technical and/or design handover documentation

Some of the websites I build are developed and integrated by other companies, which means that my perfect code must be sent away to be handled by a team that doesn't really know how I built it. Occasionally a large project will continue after my part in it has been completed, and I won't necessarily be around to advise developers on the best way to build new elements. In my experience these are potentially risky transition points, which can be made much safer by the provision of comprehensive technical and/or design handover documents.

I also sometimes write CMS training documentation as part of the handover of the completed website to the permanent web editing team. This does depend on budget, and may include instructions on how to edit various parts of the website, as well as a set of "house style" rules for the website, in order to keep everything consistent.

I have written these types of documentation for the following projects: