DeckTape is a high-quality PDF exporter for HTML presentation frameworks.
DeckTape is built on top of Puppeteer which relies on Google Chrome for laying out and rendering Web pages and provides a headless Chrome instance scriptable with a JavaScript API.
|
ℹ️
|
DeckTape 1.0 was built on top of PhantomJS which relies on Qt WebKit. See the 1.x branch for more information. |
DeckTape currently supports the following presentation frameworks out of the box:
• Bespoke.js • DZSlides • remark • Shower • CSSS • Flowtime.js • reveal.js • Slidy • deck.js • impress.js • RISE • WebSlides
DeckTape also provides a generic command that works by emulating the end-user interaction, allowing it to be used to convert presentations from virtually any kind of framework. The generic mode is particularly useful for supporting HTML presentation frameworks that don’t expose an API or accessible state.
DeckTape’s plugin-based architecture exposes an extension API, making it possible to add support for other frameworks or to tailor existing plugins to your specific needs.
DeckTape can optionally be used to capture screenshots of your slide decks in various resolutions (similar to pageres). That can be useful to make sure your presentations are responsive or to create handouts for them.
You can browse some slide deck examples below that have been exported with DeckTape.
$ decktape -h
Usage: decktape [options] [command] <url> <filename>
decktape version
command one of: automatic, bespoke, csss, deck, dzslides, flowtime, generic, impress,
remark, reveal, shower, slidy, webslides
url URL of the slides deck
filename Filename of the output PDF file
Options:
-s <size>, --size <size> Size of the slides deck viewport: <width>x<height> (ex. 1280x720)
-p <ms>, --pause <ms> Duration in milliseconds before each slide is exported [1000]
--load-pause <ms> Duration in milliseconds between the page has loaded
and starting to export slides [0]
--screenshots Capture each slide as an image [false]
--screenshots-directory <dir> Screenshots output directory [screenshots]
--screenshots-size <size> Screenshots resolution, can be repeated [--size]
--screenshots-format <format> Screenshots image format, one of [jpg, png] [png]
--slides <range> Range of slides to be exported, a combination of slide indexes
and ranges (e.g. '1-3,5,8')
Defaults to the automatic command.
Iterates over the available plugins, picks the compatible one for presentation at the
specified <url> and uses it to export and write the PDF into the specified <filename>.In addition to the general options listed above, command specific options can be displayed the following way:
$ decktape <command> -h
Iterates over the available plugins, picks the compatible one for presentation at the specified url and uses it to export and write the PDF into the specified filename.
Emulates the end-user interaction by pressing the key with the specified --key option and iterates over the presentation as long as:
-
Any change to the DOM is detected by observing mutation events targeting the body element and its subtree nor
-
the number of slides exported has reached the specified
--max-slidesoption.
The --key value must be one of the UI events KeyboardEvent key values and defaults to ArrowRight, e.g.:
$ decktape generic --key=ArrowDown
Captures each slide as an image at the --screenshots-size resolution, exports it to the --screenshots-format image format and writes the output into the --screenshots-directory directory.
The --screenshots-size option can be set multiple times. For example:
$ decktape --screenshots --screenshots-size=400x300 --screenshots-size=800x600
Exports only the slides specified as a series of slides indexes and ranges, e.g.:
# Capture a single slide
$ decktape --slides 1
# Capture a series of slides
$ decktape --slides 1,3,5
# Capture a range of slides
$ decktape --slides 1-10
# Capture a combination of slides and ranges
$ decktape --slides 1,2,5-10The rendering stops and the file written out after the largest numbered slide is exported.
The following slide deck examples have been exported using DeckTape:
| HTML5 Presentation | Framework | Exported PDF |
|---|---|---|
reveal.js |
devoxx-es6-maintenant.pdf (2.3MB) |
|
reveal.js |
reveal-js-mathjax.pdf (0.3MB) |
|
reveal.js |
opensource-getting-involved.pdf (0.6MB) |
|
Asciidoctor + DZSlides |
going-further-with-cdi.pdf (2.4MB) |
|
deck.js |
deck-js-presentation.pdf (0.5MB) |
|
remark |
remark-js-slideshow.pdf (0.3MB) |
|
Slidy |
html-slidy-presentation.pdf (0.5MB) |
|
CSSS |
||
Shower |
shower-presentation-engine.pdf (0.6MB) |
|
Bespoke.js |
new-es5-overloards.pdf (0.2MB) |
DeckTape can be executed within a Docker container from the command-line using the astefanutti/decktape Docker image available on Docker Hub:
$ docker run astefanutti/decktape -h
For example:
-
To convert an online HTML presentation and have it exported into the working directory under the
slides.pdffilename:$ docker run --rm -v `pwd`:/slides astefanutti/decktape http://lab.hakim.se/reveal-js slides.pdf -
Or, to convert an HTML presentation that’s stored on the local file system in the
homedirectory:$ docker run --rm -v `pwd`:/slides -v ~:/home/user astefanutti/decktape /home/user/slides.html slides.pdf
-
Or, to convert an HTML presentation that’s deployed on the local host:
$ docker run --rm --net=host -v `pwd`:/slides astefanutti/decktape http://localhost:8000 slides.pdf
You may want to specify a tag corresponding to a released version of DeckTape for the Docker image, e.g. astefanutti/decktape:2.0.0.
Besides, it is recommended to use the following options from the docker run command:
Alternatively, you can use the docker cp command, e.g.:
# Run docker run without the --rm option
$ docker run astefanutti/decktape http://lab.hakim.se/reveal-js slides.pdf
# Copy the exported PDF from the latest used container to the local file system
$ docker cp `docker ps -lq`:slides/slides.pdf .
# Finally remove the latest used container
$ docker rm `docker ps -lq`
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent