I'm curious how you capture and document interfaces, from site maps, to describing the different states of page components, rules for image sizes, page layout templates, etc? A lot of thought goes into these things and they may not be apparent by just looking at static designs or a clickable prototype. Documenting these things is also key to ensure that tech teams execute as intended, QA teams test as intended, and editorial/marketing teams create content as intended.
From what I see, the standard is to create hundreds of pages of annotated screenshots or wire frames (in OmniGraffle, InDesign, etc) and send them to a client as a PDF.
Are PDFs the best we can do, or are there better solutions? How do you handle this?