| Page Properties | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Summary
...
potentially layout options:
- Heading only
- Blank (invisible heading)
- Heading plus 1 content
- Heading plus 2 content areas, side by side
- Section title slide
(Images are screenshots from PowerPoint to illustrate possibilities)
Background and goals
Assumptions
- A slide must always have a title, even if it is not displayed on the slide.
Requirements
| # | Title | User Story | Importance | Notes | JIRA |
|---|---|---|---|---|---|
| 1 | As a content creator I want to select a different layout for a slide when I add a new one to my deck | ||||
| 2 | As a editor, I want to change the layout of an exisiting slide | ||||
| 3 | As a user I want slides to reflow correctly when I view them on a mobile device | ||||
| 4 |
User interaction and design
...
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Asked by | Outcome |
|---|---|---|
| Do we want to store the layout in a slides metadata? | Abi | |
| Do we want to use layouts to manage inserting different types of content e.g. a layout which includes heading and code? | Abi |
Not Doing
| Feature | Status |
|---|---|
Source material for user/stakeholder feedback
Google Slides layout options:
Requirements (/user stories) from pilot roadmap:
...
Evaluation/improvements by Farid Hasanov master thesis :
Evaluation at UniBonn :
Project Partners feedback: