Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/bennypowers/eleventy-plugin-slide-decks

🎼 It makes an itsy-bitsy, teeny-weeny, web-component slide deck prezzy 🎵 🎚️ Write slide decks with 11ty and share them over the web. 🎴
https://github.com/bennypowers/eleventy-plugin-slide-decks

11ty eleventy eleventy-plugin html presentation slides web web-components

Last synced: 29 days ago
JSON representation

🎼 It makes an itsy-bitsy, teeny-weeny, web-component slide deck prezzy 🎵 🎚️ Write slide decks with 11ty and share them over the web. 🎴

Awesome Lists containing this project

README 

        
![Am Yisrael Chai - עם ישראל חי](https://bennypowers.dev/assets/flag.am.yisrael.chai.png)



# eleventy-plugin-slide-decks



🎼 It makes an *itsy-bitsy*, *teeny-weeny*, *web-component* slide deck prezzy, 

which is basically a small SPA. 🎵



🎚️ Write slide decks with [eleventy](https://11ty.dev) and share them over the 

web. 🎴



Uses [``](https://github.com/ruphin/slidem) to do most of the work 

for you.



## Installation and Setup



```

npm i eleventy-plugin-slide-decks

echo "_includes/deck.html" >> .gitignore

```



Then in your 11ty config:



```js

const DecksPlugin = require('eleventy-plugin-slide-decks');

eleventyConfig.addPlugin(DecksPlugin);

```



## Writing Decks



Create a `decks` directory in your 11ty source root (or use `decksDir` option).

Each slide deck is a single dir under the `decksDir`. Add an 11ty data file for 

each deck or for all decks.

You must add a single template to each deck's root dir, containing frontmatter 

for that deck. At minimum, that file should have `layout: deck.html` and  `deck: 

deckdir`. For example, if you have a deck in `decks/prezzo`, you must at very

least create `decks/prezzo/prezzo.md` with this content:



```md

---

layout: deck.html

deck: prezzo

---

```



Optional frontmatter keys:

```yaml

title: Slide deck title

author: slide deck author (used in open graph tags)

description: meta description (and og)

lang: en # default

dir: ltr # default

date: 2022-12-02

locale: en-US # default

origin: https://bennypowers.dev # slide deck origin (used in og:url)

coverImage: prezzo.png # used in open graph tags

icons:

  - rel: icon # required

    href: /assets/images/favicon.ico?v=2 # required

  - rel: shortcut icon

    href: /assets/icon.svg

  - rel: apple-touch-icon

    sizes: 72x72

    href: /assets/images/manifest/icon-72x72.png

preconnect:

  - https://fonts.googleapis.com

stylesheets:

  - href: /optional/urls/to/stylesheets.css

    async: true # optional

    media: 'screen and (prefers-color-scheme: dark)' # optional

scripts:

  - src: prezzo.js

    type: module

```



You can also provide an `importMap` as data, and it will print in the ``.



All urls are passed through the `url` filter for you.



It's possible to put content in this file, but you should expect that content to 

be invisible, for example, you can put an SVG sprite sheet in there:



```html



  {% for icon in collections.icon %}

    {{ icon.templateContent | safe }}{% endfor %}

  



```



### WebC Decks



If you want to go buck wild, let loose; if you're so excited and you just can't 

hide it, you can also (deep breaths) use the 

[WebC](https://www.11ty.dev/docs/languages/webc/) deck component:



```html

---

eleventyImport:

  collections:

    - webbyprezzy

---



```



Don't leave out the eleventyImport or or the `webc:nokeep`, or else things will

break in hilarious ways.



### Writing Slides



Each decks slides are located in it's `slides` directory, and ordered by name. 

It's recommended to name the slide files `00-first-slide.md`, 

`10-second-slide.md`, etc. You should also add an 11ty data file for the slides 

directory containing `permalink: false`, in order to prevent 11ty from rendering 

individual HTML pages for each slide, which would only duplicate the slide 

content.



So for example:



```

decks

├── decks.json

└── prezzo

    ├── img.png

    ├── prezo.css

    ├── prezzo.md

    └── slides

        ├── 00-first-slide.md

        ├── 10-second-slide.md

        ├── 99-last-slide.md

        └── slides.json

```



#### Stepping Through Slide Content



If you want certain elements of a slide to reveal one by one, specify a CSS 

selector in the `reveal` frontmatter key. Take for example this slide:



~~~md

---

reveal: li, img

---

## Using Slidem



- HTML wins

- JavaScript is p. cool too



![a satisfied and productive slide author](img.png)

~~~



When switching to this slide, on step 1 only the heading will be visible, on 

step 2 the first list item ("HTML wins") will appear, on step 3, the next list 

item, and on step 4, the image.



#### Styling Slides



You can set the classname for the slide with the `class` frontmatter key:



```md

---

class: dark

---

```

```html



```



Slides get the `name` attribute based on their filename, so `00-first-slide.md` 

would render as ``. You can then style that 

slide with good-old CSS. Each slide exposes `container` and `content` [CSS 

Shadow Parts](https://developer.mozilla.org/en-US/docs/Web/CSS/::part):



```css

[name=first-slide] {

  background: hotpink;

}



[name=first-slide]::part(content) {

  display: grid;

  grid-template-columns: 1fr 1fr;

  gap: 1em;

}

```



##### `style` frontmatter



Although using CSS is encouraged, you can also set styles on the slide element 

with the `style` frontmatter key. If the value is a string, it will be dumped 

into the `style` attribute:



```md

---

style: 'color:hotpink'

---

...

```

```html



...



```



But if you pass a YAML dictionary or a JSON object, it will be collapsed into a 

style string for you:



```md

---

style:

  color: hotpink

  font-size: 200%

  animation: jazz-hands

---

...

```

```html



...



```



#### Extending `SlidemSlide`

You might want to create your own custom slide types by extending `SlidemSlide`. 

One case in which this is useful is in providing custom slots to a slide, like a 

slide which presents a `
` in a `` with the author in the 

``. In that case, you can specify the tag name to use for the slide 

with the `is` frontmatter key:



```md

---

is: slidem-quote

---



  All our work, our whole life is a matter of semantics, because words are the 

  tools with which we work... Everything depends on our understanding of 

  them.




Felix Frankfurter



felix at the window

```

```html



```



## Options



| option             | type     | default                  | description                                             |

| ------------------ | -------- | ------------------------ | ------------------------------------------------------- |

| `decksDir`         | string   | 'decks'                  | directory off the 11ty input dir which contains slides  |

| `assetsExtensions` | string[] | see below                | file extensions to pass-through copy from the decks dir |

| `target`           | boolean  | [esbuild target][target] | esbuild target to use when bundling slide dependencies  |

| `polyfills`        | object   | see below                | polyfills to load on the decks page                     |



By default, files matching `decks/**/*.{css|jpeg|jpg|js|mp4|png|svg|webp}` will 

passthrough copy to the output dir.



The `polyfills object` defaults to the following:



```json

{

  "constructibleStyleSheets": true,

  "webcomponents": false,

  "esmoduleShims": false,

}

```



[target]: https://esbuild.github.io/api/#target