Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Target release
User Story

SWIK-342 - Getting issue details... STATUS

Document status

DRAFT

Date Created 
Document owner
Designer
Developers
QA
Work Package & deliverables 
Related JIRA tasks

Summary

  • Provide user with a selection of layouts to choose from when creating a slide
  • Manage order of components on slides

Layouts are a property of a slide.

  • Should be selected when click add a slide
  • Should be altered through the properties button for a slide

 

Propose that layouts are code through HTML

  • CSS can be removed and overridden
  • CSS used for themes

 

But if use HTML then more difficult to change layout once a slide is created.

For every layout option we need a mobile version that reflows content below a certain screen size. This is to maintain readability.

potentially layout options:

  • Heading only
  • Blank (invisible heading
  • Heading plus 1 content
  • Heading plus 2 content
  • Section title slide

Background and goals

Assumptions

Requirements

#TitleUser StoryImportanceNotesJIRA
1
 
2     

User interaction and design

Description of fields/input/elements + validation + test scenarios


Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionAsked byOutcome
 

Not Doing

FeatureStatus
  

Source material for user/stakeholder feedback


Requirements (/user stories) from pilot roadmap:

 

Evaluation/improvements by Farid Hasanov master thesis :


 

Evaluation at UniBonn :  


Project Partners feedback:



 

  • No labels