Deck v2 - Refactoring

[davidmarkclements]

Principles:

1. Deck v2 is a looser assemblage of tools for facilitating the management, editing and presentation of training content (primary) and conference talks (secondary)
2. A training slide deck is a single git repo
3. The current markdown format will remain the same - with the exception of possible removal of YAML headers (to be discussed)
4. Rely only on git for remote delivery
5. TBD: Slide structure template (styles) and theme (skins)

---

Actions:

• Separate build process from presentation layer
• Presentation layer can wrap any HTML based presentation
• Decouple from npm v2
• Decouple the PDF rendering protocol from bespoke
• Fix notes support
• Publish the skin on main NPM, and decomission the sinopia instance

cc @mcollina @lucamaraschi

EDIT 10/01/2017 - @mcollina - bullet points.

[mcollina]

cc @andrewcashmore @cjihrig

On the actions, I would add:

1. decouple the PDF rendering protocol from bespoke.
2. correctly support notes (currently they are not always working)
3. docs!!!!
4. publish the skin on stock npm, and decomission the Sinopia instance

@davidmarkclements might I edit?

[lucamaraschi]

Regarding principle nr.2, didn't we agree on having each module in separate repositories and aggregate the entire training course (by referencing the different separate modules) in a per training based repository?

[lucamaraschi]

In addition to the before mentioned actions we should probably add:

1. A file format to define the entire course (basically it describes which modules to reference)

2. A generator/scaffolder for:

   • A entire course
   • A module of a course

[davidmarkclements]

@mcollina @lucamaraschi - edit away!

@lucamaraschi we did talk about a tool for pulling entire courses - this can come under the deck banner if we're all happy with that

[mcollina]

Project created https://github.com/orgs/deckjs/projects/1