When building a web project, what sets of artifacts should be produced? How should they be organised so as to give a living Documentation Set to the client?
Some discussion along this line in Documents First Code Later. The idea seems to be evolving towards using a Wiki of some sort to capture design decisions and The Road Not Traveled so as to come up with a unified, overall view of the development life cycle.
Related:
See original on c2.com 