Metadata
- Source
- FLUID-1264
- Type
- Task
- Priority
- Major
- Status
- Closed
- Resolution
- Won't Fix
- Assignee
- Daphne Ogle
- Reporter
- Daphne Ogle
- Created
2008-08-20T20:31:27.000-0400 - Updated
2013-04-11T17:40:28.989-0400 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Design Framework
- Inline Edit
Description
Tell the user story. A suggestion is to start with context scenarios describing what the user needs to do and see without getting into any interaction with the component. Once we clearly understand what the user needs to do the context scenarios can be iterated on to describe how those needs are met with interaction in the system. (For information on context and other types of scenarios see "About Face 2.0 or 3.0", Cooper).
Flesh out each primary and secondary scenario in this way. Eventually these will become storyboards as we create wireframes for each step in the scenario. They should be documented on the wiki in the component design space.
Comments
-
Daphne Ogle commented
2008-08-21T20:05:18.000-0400 iteration19
-
Daphne Ogle commented
2008-10-13T21:01:31.000-0400 Won't fix at this point. We may decide we need to revisit simple text and dropdown to identify and flesh our primary and secondary scenarios but for now we'll close and move forward since we are so far along in design.
Also, primary & secondary scenarios should be brought into design process for rich text editing.