Wireframes | Information Architecture
Workflows | Heuristics | Other Diagrams
The primary purpose of a wireframe is to communicate the content and navigation of a specific page (or series of pages) to a development team. I believe that for the most part, wireframes are best done in “low fidelity,” because a programmer does not require unnecessary graphic details to understand the scheme of a page. In other words, the carpenter does not need to know what color the house will be painted in order to frame the house. Lo-fi wireframes include: page name, cross references, description, how to arrive there, persistent and unique content/data, persistent and unique navigation/buttons/links, error conditions.