This is an article to capture discussions around the deck structure that have taken place between Ali Khalili and Abi James when designing the layout and functions of the deck page. This is captured here as a reference guide for developers and to help with informing users in the future.

A deck consist must consist of:

the deck properties. These are displayed and edited in the RootDeckView
at least 1 slide that is visible
has an owner who originally added the deck to SlideWiki and is an editor of the content

A deck can contain:

any number of slides
one or more sub-decks which contain
- Properties, which are displayed and edited in the SubDeckView
- At least 1 slide
one or more editors

A deck can be forked or translated. This will create a new revision of the deck and the owner will change to the users who undertook this action.

A deck cannot be deleted. However, an owner can choose to remove a deck from listings so that it is no longer public.

A slide can be created within the deck or appended from another deck.

The slide remains on the revision from the time it was inserted until an /editor of the deck updates it
If any edits are made to the slide or its properties of the slide then it is forked and becomes a new revision and the owner is changed to the owner of the root-deck. This new revision is not displayed in the history of the original deck but is still linked through the Usage tab.

A sub-deck can created within the deck or appended from another deck. You can append a whole deck or a sub-deck

The sub-deck remains on the revision from the time it was inserted until an editor of the deck updates it
If any edits are made to the deck or its properties then it is forked and becomes a new revision and the owner is changed to the owner of the root-deck. This new revision is not displayed in the history of the original deck but is still linked through the Usage tab.
If the user attempts to append a sub-deck in a different language then then are directed to translate the original deck before it is appended.

A sub-deck

can not be translated or forked
can be deleted.
inherits the theme from the root-deck

A sub-deck can be added through the context menu on the tree diagram or through the add subdeck button above the deckview. In the slide view this button will not be active.

Example of deck actions

User A creates a new deck with the following information:

Title: Basic101

Description: Example deck about really old computing

Owner: User A

Date: 2nd August 2016

Language: English

MetaData:

Tags:

Theme: Liquid

The deck automatically has 1 slide in it which is created with the default layout for theme and an auto-generated title.User A edits the slide and adds a title. The slide has the properties:

Title: Introduction

Owner: UserA

Date: 2nd August 2016

Tags: Introduction1

Layout: Default

User A appends a slide from another deck. The slide retains the properties from the original deck:

Title: What is Basic

Owner: UserB

Date: 1st Jan 2016

Tags..... Computing

Layout: image only

User A changes the title of the slide "What is Basic" that they had appended. This creates a new revision of the slides. This changes the owner and the date of the slide so the properties become:

Title: Basic - an introduction

Owner: User A

Date: 2nd August 2016

Tags..... Computing

Layout: image only

User A adds a new sub-deck. This inherits the properties of the deck but User A is required to add a title. The properties for the sub-deck are:

Title: Why use Basic?

Owner: User A

Date: 2nd August 2016

Language: English

Tags: Introduction1, Computing

Theme: Liquid

This sub-deck automatically has 1 slide in it which is created with the default layout for theme and an auto-generated title.

User A appends a sub-deck with 5 slides. This retains the properties of the original deck but inherits the theme from the root-deck.

Title: Old computing

Description: What I know about really old computing

Owner: User C

Date: 12th April 2015

Language: English

Tags: education, computing, 20th century

Theme: Liquid

After these revisions the root deck has the following properties:

Title: Basic101

Example deck about really old computing

Owner: User A

Date: 2nd August 2016

Language: English

Tags: education, computing, 20th century, Introduction

Theme: Liquid

No of slides: 8

And a deck structure of:

Basic101

-- Introduction

-- Basic - an introduction

- Why use Basic?

-- Slide 1

- Old computing (owner remains User C)

-- Old Computing 1

-- Old Computing 2

-- Old Computing 3

-- Old Computing 4

-- Old Computing 5

Page:

Deck Structure and actions

Example of deck actions

Related articles

Browser not supported