I wish it was split into the processor and "IDE". I'd be able to use my preferred editor instead. I'd be able to run an md -> html -> pdf pipeline in a lightweight, headless build script.
Just saying.
I wish it was split into the processor and "IDE". I'd be able to use my preferred editor instead. I'd be able to run an md -> html -> pdf pipeline in a lightweight, headless build script.
Just saying.
The build pipeline is a simple git-push. Your slide deck is then instantly available for sharing online and for download as self-contained bundle or PDF.
A dedicated desktop tool is also available that gives you live previews and speaker support offline. You can also export your decks to Microsoft PowerPoint, Apple Keynote, and Google Slides.
For a sample GitPitch slide deck see here:
This is how I make my presentation PDFs from Markdown files using pandoc (except I think for me it's md -> latex -> pdf). I use Snakemake[1] to automate it using the following Snakefile: https://gist.github.com/DarwinAwardWinner/5c3fd8fb82757bb04a...
The idea is that you write presentation.mkdn, and then run "snakemake", which runs pandoc to produce presentation.pdf. Any images you include should be in a subdirectory called "images". If you have "images/giraffe.svg", you can include "images/giraffe.pdf" in your presentation and it will convert it for you automatically (using Inkscape's CLI), and same for pdf to png using ImageMagick.