You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 6, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# DeckDeckGo
2
2
3
-
Create a lightweight presentation using HTML and Web Components.
3
+
Create a lightweight presentation using Web Components.
4
4
5
5
[DeckDeckGo] is build with [Stencil](https://stenciljs.com) and could be use in any modern framework or even without any.
6
6
@@ -15,6 +15,7 @@ Create a lightweight presentation using HTML and Web Components.
15
15
-[Installing DeckDeckGo in any projects](#installing-deckdeckgo-in-any-projects)
16
16
-[Editing](#editing)
17
17
-[Detailed documentation](doc/slides/slides.md)
18
+
-[Markdown](doc/markdown/markdown.md)
18
19
-[Navigation](#navigation)
19
20
-[Extra features](#extra-features)
20
21
-[Lazy loading](#lazy-loading)
@@ -25,7 +26,7 @@ Create a lightweight presentation using HTML and Web Components.
25
26
26
27
## Features
27
28
28
-
* ✏️ Create **without effort** your presentation using HTML and CSS
29
+
* ✏️ Create **without effort** your presentation using Web Components
29
30
30
31
* 📰 Use predefined **templates**
31
32
@@ -59,7 +60,7 @@ To get started and **to create your presentation**, run the following command an
59
60
npm init deckdeckgo
60
61
```
61
62
62
-
Once your presentation created, go to your new project's folder and start editing `src/index.html` to prepare your slides and content for your talk 😉
63
+
Once your presentation created, go to your new project's folder and start editing your slides and content for your talk 😉
63
64
64
65
## Installing DeckDeckGo in any projects
65
66
@@ -88,6 +89,10 @@ The deck should be declared using the tag `<deckgo-deck/>` and each slide should
88
89
89
90
The 👉 [extended documentation](doc/slides/slides.md) 👈 displays all templates and options available for each slides.
90
91
92
+
### Markdown
93
+
94
+
Per default, [DeckDeckGo]'s presentations are edited using HTML and are Web Components, that's why the documentation and examples are provided in HTML. But if you are using the [starter kit](https://github.com/fluster/deckdeckgo-starter) and are editing your talk with Markdown, you could have a look to the [Markdown documentation](doc/markdown/markdown.md) to get some examples.
95
+
91
96
[DeckDeckGo] also offers a couple of components which could be used in almost every templates, these are documented in a separate [chapter](doc/components/components.md) of the documentation.
This documentation has for goal to introduce you briefly on how is it working out if you are using the [starter kit](https://github.com/fluster/deckdeckgo-starter) and are editing your talk with Markdown.
4
+
5
+
## Table of contents
6
+
7
+
-[Introduction](#introduction)
8
+
-[Editing](#editing)
9
+
-[Example](#example)
10
+
-[Attributes](#attributes)
11
+
12
+
## Introduction
13
+
14
+
It's pretty simple, the goal of the editing with Markdown is to offer the same abilities as if you would have while editing your talk with HTML.
15
+
16
+
When you edit your talk with Markdown, furthermore than the set of common supported tags, the [DeckDeckGo Webpack Markdown Plugin](https://github.com/fluster/deckdeckgo-webpack-markdown-plugin) extend these by adding the support of the different [DeckDeckGo] slides as documented in the 👉 [extended documentation](doc/slides/slides.md) 👈.
17
+
18
+
Your Markdown code will, through the help of the plugin, be compiled and injected in the `index.html` distribution file at build time. Doing so, your [DeckDeckGo] presentation will remain SEO friendly even without server side rendering.
19
+
20
+
## Editing
21
+
22
+
As describe above, furthermore than the Markdown tags, you could use extended tags in order to specify which types of slides you would like to use. To do so, use the separator `---` followed by a shortened version of the template's name, like for example `--- title` for `</deckgo-slide-title>`.
23
+
24
+
Furthermore the plugin takes care of injecting the content you would provide in the right slots.
25
+
26
+
### Example
27
+
28
+
The following `</deckgo-slide-title>` slide:
29
+
30
+
```
31
+
--- title
32
+
# My presentation title
33
+
34
+
Hello World 🚀
35
+
```
36
+
37
+
would be parsed into:
38
+
39
+
```
40
+
<deckgo-slide-title>
41
+
<h1 slot="title">My presentation title</h1>
42
+
<p slot="content">
43
+
Hello World 🚀
44
+
</p>
45
+
</deckgo-slide-title>
46
+
```
47
+
48
+
### Attributes
49
+
50
+
As some templates needs attributes, you would also be able to specify them in Markdown.
0 commit comments