The recent rise in more powerful technologies that provide richer user experiences online has presented us with a challenge. As designers, we are moving from from designing for “PIAs” to designing for “RIAs.” Does our documentation style change with the technology? Will our standard ways do the job?
Spend any time with Visio and you’ll find yourself wondering how glue works. In the real world, it’s pretty straightforward: put glue between two things and they’ll stick. Although glue is used for sticking shapes together in Visio, the metaphor ends there.
The Yahoo! platform design team shares their process for defining and designing a pattern and standards library, the process for defining the requirements of the repository and the process for defining the lifecycle of a pattern.
This article will expand upon the Visio techniques presented in the last Special Deliverable and will build on them, showing how to create a widget that can be toggled between two states.
Few information architects tap the full power of Visio. For the IA, Visio is a means to an end—a mechanism for capturing some ideas on paper before they are transformed into graphics, HTML, and code.
Site diagrams can be quite helpful in answering all kinds of hard questions. How to create the right diagram became a personal challenge for Jason Withrow. He shares his story through tips and techniques…
Visio practically groaned as I opened the wireframes for my current project, which were in something like the twentieth revision. It was the usual story—poorly defined requirements and business rules—and my project folder was fast becoming the poster child for Feature Creep Flu.
I’ve heard of a fantastic land far, far away where magical people called “project managers” collect something called “requirements.” These requirements so clearly, concisely, and completely describe work to be done that all the villagers involved share a common understanding of a project’s goals.
In October 2000, Jesse James Garrett introduced a site architecture documentation standard called the Visual Vocabulary. Since then, it has become widely adopted among information architects and user experience professionals.
Wireframes: At once a singular composition and a collaborative expression, communicating the vision of both an individual and a team. As a result, they can be stacked with an enormous amount of detail. Are we becoming victims of information pollution in our own wireframes?