Page Comparison

1. Problem

Problem Statement:

More problem statement...

Design Goals:

 More design goals...

Competitive Analysis: Rich Text Inline Edit Competitive Analysis

2. Users

Catalina, Christy and Ashley are the users whose needs we are primarily considering when designing the Rich Text Inline Edit.

Fluid Personas are a collection of various types of important users whose needs we need to consider throughout the design process.

3. Users' needs

Contexts of Use: In what contexts would the user need Rich Text Inline Edit? What activities do they undertake in the contexts?

Functional Requirements: What use cases does the Rich Text Inline Edit component support?

Primary & Secondary Scenarios: In context, what are the primary and secondary user needs are we meeting?

4. Solution

Wireframes: Visual representation of design iterations and final designs.

Storyboards: How, when, and where would the user use Rich Text Inline Edit?

• Rich Text Edit Storyboard - Make text links
• Rich Text Edit Storyboard - Edit Image
• Rich Text Inline Edit Storyboard - Edit rich text

Inline Edit Design Pattern: Design advice for allowing users to edit content in the context of their work.

5. User Testing

User Testing Protocols: Describes how the user testing of Rich Text Inline Edit will be carried out.

User Testing Results: Describes how the users interacted with the Rich Text Inline Edit prototype and what improvements can be made.

6. Preparing for Implementation

Storycards: Decomposes Rich Text Inline Edit into small implementable chunks.

Functional Specification: Development specification containing interaction details such as "interesting moments."