I'm working on creating documentation for a programming language and development environement. We're considering creating a wide variety of material including tutorials, reference material, inline documentation, videos, searchacle examples, et cetera.
There are two things I would love to hear from anybody:
1) Books/articles/anything you know of discussing design of documentation
2) Examples of awesome documentation that you know of. Even though I'm working on programming tools, I would love examples from any domain to get inspiration.
I've completed the UI and UX design for an iPad app and now it's time to hand everything off for development and I was wondering if there were any best practices for documenting the interaction design for the developer. Our dev is in house, so I can just pop over and talk to him, but I think documentation would be best for workflow.
If you've had experience documenting interaction design for iOS in the past, please share.
I'm working on the visual/UI design for an application that will use Silverlight components. I'd like the Silverlight visual UI to match the rest of the application. How do people recommend specifying visual design to developers for a theme in Silverlight or other? In the past I've marked up static Photoshop layouts with colors, type specs, measurements, etc., but wonder if there are other/better ways.
Any tips or references on this topic would be helpful.
In a recent convo on Twitter, Janna DeVylder, Dave Malouf, Steve Baty and I were discoursing about the difficulties of traversing the Research > Design chasm. Some really great thoughts ensued. So, I thought I'd keep the convo going here.
It's a topic I'm keely interested in. Having helped present From Design to Research at Agile '09, and having worked on this for many years, I still realize I have lots to learn.
What do you think about creating pixel perfect wireframes? Good or evil? (Or it depends ;-)
The websites our team work on have a standard width, grid, interactive elements and some general guidelines for typography. Therefore any designer working on a wireframe could create it to the pixel (we have a fixed layout).
My organization is moving toward UML for all of its documentation,
from requirements through development and maintenance. The UX
practice here is in it's infancy and I am now a team of one. While
I'm familiar with UML, I'm skeptical that it will be appropriate
for user flows and any other UX documentation.
Has anyone worked in a UML environment? How did you integrate your
practice into RUP or similar methodologies?
I've been tasked at helping our BAs sift through some documentation,
to work within the confines of the RUP methodology. The documents
that I'm working on are the Storyboard artifact, the UI concepts,
and the UI Document or UI Specs. document.
The first two are pretty self explanatory, but I'm struggling with
what's usually in the last one.
The way I see it is this document will be a bridge for people in
systems and people on the business side to rally around the screens
and "be on the same page", literally.
So, my question is, what usually goes in this UI document?
I've been tasked with getting together specs for a usability lab that one of my clients is building. I'm thinking a standard three-stage lab with a relatively large participant room for group testing, if that ever comes up. But I don't have specifics yet. Has anyone out there done this before? Any advice?