1. Problem
Allow users to change the layout of content modules, for example portlets within a portal environment.
Use Cases:
- Move location of content modules within a layout
- Constrain "locked" content modules from being moved
2. Users
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 to reorder portlets/boxes? What activities do they undertake in these contexts?
Functional Requirements: What use cases does the Layout Reorderer 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 a Layout Reorderer?
Drag and Drop - Layout Preview Design Pattern: Design advice for previewing the page layout while doing drag and drop.
5. User Testing
Layout Reorderer User Testing: Summary of all user testing performed on the Layout Reorderer component.
User Testing Protocols: Describes how the user testing of Layout Reorderer will be carried out.
- Layout Reorderer User Testing - Round 1
- Layout Reorderer User Testing - Round 2
- Layout Reorderer User Testing - Round 3
- Layout Reorderer User Testing - Round 4
User Testing Results: Describes how the users interacted with the Layout Reorderer prototype and what improvements can be made.
6. Preparing for Implementation
Storycards: Decomposes the Layout Reorderer into small implementable chunks.
Functional Specification: Development specification containing interaction details such as "interesting moments."