Issue description

It is not possible to access the "getting started" page by using the left side navigation.

Of course you could click on the Dekk icon in the top side navigation, but I would not expect to have the "getting started" as the "main" page of Dekk. So I would also not try to use that. I would expect the getting started as first element in the left side navigation.

Steps to reproduce

• Open https://sinnerschrader.github.io/dekk/api/
• Click on any item in the navigation

Versions

1. yarn: 1.3.2
2. node 6.9.1
3. dekk: 1.0.0-17

Issue description

The documentation is missing an example on how Code should be used.

I'm trying it like this, but I only get errors:

      <Code>
        const helloWorld = foo => {
          console.log(foo)
        }
      </Code>

or like this:

      <Code>
      {
        const helloWorld = foo => {
          console.log(foo)
        }
      }
      </Code>

Steps to reproduce

• Open Code documentation

Versions

3. dekk: 1.0.0-17

Add a web wrapper around Dekk.
This wraps Dekk into an editor.

As we have discussed!

Issue description

In the examples it says fadeSwipe, but the only animation that exists in fadeSlide.

Steps to reproduce

• Open the Using Fragments example
• Look at the code

Versions

1. yarn: 1.3.2
2. node 6.9.1
3. dekk: 1.0.0-17

should probably go to dekk-web

Issue description

Without having the config component loaded, dekk will fail with the following message:

Uncaught TypeError: Cannot read property 'paging' of undefined
    at Deck.get (index.js:286)

Steps to reproduce

• Use the gh-pages example

Steps to fix

• Load the Config component
• Add the Config component into Deck component

Versions

dekk 1.0.0-4

1. yarn: 1.3.2
2. node 6.9.1

Issue description

It's confusing for me that the preconfigured Dekk is called Dekk. Don't get me wrong: I love that there is a default component to use without having to touch everything else. BUT when I want to change something, it gets confusing, because after the "getting started" you use the dekk/deck component.

I'm not sure how to address this issue. Maybe rename the preconfigured Dekk into PreconfiguredDeck? So that it's clear that this is the base to get started?

Steps to reproduce

• Open the getting started and create your App based on the steps
• Open anything else from the documentation

Versions

3. dekk: 1.0.0-17

Issue description

The documentation for Plugins is still importing the Config component instead of the Plugins.

Steps to reproduce

• Adding URLs
• Enable Paging

Versions

1. yarn: 1.3.2
2. node 6.9.1
3. dekk: 1.0.0-5

Issue description

It's not possible to wrap a Fragment around a FitImage when using Grid & ImageGrid master slides.

<Fragment order={1}>
  <FitImage
     src="https://placehold.it/600"
     alt="this is a placeholder image. please adjust the alt accordingly"/>
</Fragment>

Actual result

I don't see any image.

Steps to reproduce

• Wrap Fragment around FitImage and use that in an Grid or ImageGrid

Versions

3. dekk: 1.0.0-17

Issue description

All tests fail. This causes failed builds on Travis.
Please add passing tests or remove them from the packages.
This will also encourage writing tests from now on.

Steps to reproduce

run yarn test or look at https://travis-ci.org/sinnerschrader/dekk/jobs/344486288

Versions

• dekk: 1.0.0-4

make sure the wrapper works as intended (including dev mode)

• Rewrite Dekk
• Use React Context API
• React 17+
• Use emotion.js
• use memo
• use functional components
• provide hooks for common operations
• use framer-motion for animations
• ensure SSR compatibility
• Rethink Master slides
• Rethink Fragments and Sequences
• Take Accessibility VERY SERIOUS
• Rewrite Presenter View
• Better plugin API
• Add interaction API
• Better streaming API
• Optimize for performance
• Better mobile / responsive support
• Rethink core vs community packages

Issue description

React 16.3 offers a new API for Context.
Please investigate how this can help handle context in Dekk.

More info: https://medium.com/dailyjs/reacts-%EF%B8%8F-new-context-api-70c9fe01596b

Versions

• dekk: 1.0.0-4

Issue description

using 0 in the URL might be irritating
We could simply shift it by one to make it easier to interpret by the human mind.

Steps to reproduce

Use <Url/> inside <Plugins/> (requires #12)
or set <Config url="hash" /> (requires https://github.com/sinnerschrader/dekk/releases/tag/v1.0.0-4)

Versions

• dekk: 1.0.0-4

Issue description

I would be nice to have the ability to define speaker-deck layouts.

This could look similar to createStyledMaster

const SpeakerDeck = createStyledSpeakerDeck(
  <Layout>
    <Slot name="Current" withComponent={Current})/>
    <Slot name="Next" withComponent={Next})/>
    <Slot name="Notes" withComponent={Notes})/>
  </Layout>
)`
  display: grid;
  grid-template-rows: 1fr 1fr;
  grid-template-columns: 1fr 1fr
  grid-template-areas:
    "Current Next"
    "Notes Notes";
`

Versions

• dekk: 1.0.0-11

Issue description

There is a vulnerability issue for react and react-dom

Steps to reproduce

Versions

1. dekk: v2.0.0-2

Issue description

What is the desired way to use all plugins with their default values? Because doing it like this

<Deck>
    <Plugins>
    </Plugins>
</Deck>

is throwing an error:

index.js:260 Uncaught TypeError: Cannot read property 'type' of undefined
    at index.js:260
    at Array.map (<anonymous>)

Steps to reproduce

• Add the Plugins component without any elements to the Deck

Versions

1. yarn: 1.3.2
2. node: 6.9.1
3. dekk: 1.0.0-5

Issue description

Fragments only allow simple transitions. It would be nice to have the same capabilities as we have with <Slide/>.

Slides and fragments could also use the same animations.

Versions

• dekk: 1.0.0.-4

Issue description

The documentation is missing an example on how FitImage should be used.

Steps to reproduce

• Open Fit image documentation

Versions

3. dekk: 1.0.0-17

Issue description

The new feature Plugins allows rendering global elements inside Deck.
There is no separation of Plugins and actually rendered components.

We could add a "slot" similar to Plugins which will allow separating both cases.

Steps to reproduce

Use the new feature Plugins and create a plugin that renders more than null.

Example: https://github.com/sinnerschrader/dekk/blob/ac4b54362e1868af5eb91e35b7e1d53b3c245858/gh-pages/gh-pages.js#L30-L36

Versions

• dekk: master (https://github.com/sinnerschrader/dekk/tree/ac4b54362e1868af5eb91e35b7e1d53b3c245858)

Issue description

The identifier naming is 🐯 ("wild"). Some newer features try to make these easier to understand: (See #12)

• fragment => fragmentOrder
• fragmentCount => fragmentIndex
• page => slideIndex
• pageCount => slideCount
• ... (everything should use the same identifier for the same purpose

Steps to reproduce

Look at the source code (Store and anything in core that uses store + dependants)

Versions

• dekk: 1.0.0-4

Issue description

Timer would be nice with seconds and milliseconds.

"Minutes only" are limiting the usage.

Steps to reproduce

• Use `import Timer, {renderCountdown} from '@dekk/countdown'"

Versions

3. dekk: 1.0.0-17

Issue description

We want to change the config/plugin logic

Suggestion 1

const plugins = [
  url({type: 'hash'})
  paging({trigger: 'keyup'})
]
<Deck plugins={plugins}></Deck>

Suggestion 2

<Deck>
  <Plugins >
    <Url type="hash" />
    <Paging trigger="keyup"/>
  </Plugins>
</Deck>

Issue description

There is no documentation on how the properties animation, animationIn and animationOut can be used and on which elements.

Steps to reproduce

• Open the animations documentation
• Search for "animation" or "animationIn" or "animationOut"

Versions

dekk: 1.0.0.-17

Issue description

When setting the paging={true} I receive this warning in the browser console:

Warning: Failed prop type: Invalid prop `paging` of value `true` supplied to `Config`, expected one of [false].
    in Config (created by App)
    in App

Steps to reproduce

• Use the Config component
• Set paging to true: <Config paging={true} url='hash'/>

Versions

1.0.0.-4

1. yarn: 1.3.2
2. node 6.9.1

Create a value proposition for Dekk.

Issue description

The ToC on every page is not working, its always pointing to the home page.

Steps to reproduce

• Click on any element in any ToC

Versions

1. yarn: 1.3.2
2. node 6.9.1
3. dekk: 1.0.0-17

Issue description

Right now we only Cover and Chapter. Both of them are dividing the screen into A and B.

It would be nice to have an element that is in center of the whole screen. And that in only one area A.

This way the Cover would be different from the Chapter and people can use it in different ways.

Proposal

Big

┏━━━━━━━━━━━━━━━┓
┃               ┃
┃       A       ┃
┃               ┃
┗━━━━━━━━━━━━━━━┛

Versions

3. dekk: 1.0.0-17

Issue description

When using the Text component in the Main master slide I get this error:

Uncaught Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Steps to reproduce

• Use the Main master slide
• Add the Text element like this:

    <A>
      <Text>This is some text</Text>
    </A>

Versions

1. yarn: 1.5.1
2. node 6.9.1
3. dekk: 1.0.0

Should pubnub be used. Are there other options?
Best case: something native, serverless.

running a server is not a problem and will probably be needed for routing anyways.

Discussion open.

• buttons
• text inputs
• range inputs
• spinner inputs
• toggles / checkboxes / radiobuttons
• sidebar
• header
• menu

Does it make sense to use lerna for this project?