Marp: Markdown Presentation Writer
yhatt.github.io
yhatt.github.io
On a related note, I've developed an open source editor that can edit Markdown, R Markdown, and XML documents[1][2]. The input document is translated in real-time to HTML. Using the Chain-of-Responsibility pattern[3] makes it straightforward to introduce additional processor chains, which could include slide show output via CSS.
On a minor technical note, including HTML tags (such as <small>...</small>) defeats one of the key benefits of Markdown: separation of content from presentation. An alternative is to use named blocks to classify text, such as[4]:
::: footer
Copyright 2019 ...
:::
[1]: https://github.com/DaveJarvis/scrivenvar[2]: https://github.com/DaveJarvis/scrivenvar/blob/master/USAGE.m...
[3]: https://github.com/DaveJarvis/scrivenvar/tree/master/src/mai...
Last week I wrangled together a repo that adds Spectacle with MDX support to a Create-React-App project, as a reusable starting point [3]. Worked out nicely for a talk I gave this week.
[1] https://github.com/jxnblk/mdx-deck
[2] https://github.com/FormidableLabs/spectacle
[3] https://github.com/markerikson/cra-spectacle-mdx-boilerplate
Of course not, we've had Beamer[1] for that purpose for many years :)
>I love markdown as much as the next person, but it was designed for writing, not for slides.
People said that about LaTeX, and it stopped no one :D
On a more serious note, imagine living in a world where your presentations/slides are version-control friendly.
Now look around you. You are in that world now.
LaTeX is for writing long-ish text. If what you are writing doesn’t contain sufficiently long text, then it’s hard to justify the overhead compared to say Markdown-based solutions.
https://bitbucket.org/Maurizio_Tomasi/adass2018-julia/src/ma...
(The keynote is in "presentation.md", and the paper in "article.md".)
I had to customize a few pandoc's defaults (see the Makefile) and even had to use a Python filter to tweak the output, but the result was excellent: once everything was in place, creating the slides required no effort at all. I was even able to switch the format from 4:3 to 16:9 in a breeze, once I learned what the resolution of the projector was.
I find working in heavy-duty presentation software packages to be like running through glue. Instead of creating content, I get caught up in pixel-pushing to make everything look right. Marp offers a couple of styles. It's very refreshing to use.
Best of all, it'll output nice-looking PDFs that you can share afterwards. Recommended.
I have no affiliation with Marp or its creator - I'm simply a happy user.
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.
"We have already dropped maintenance."
... so, don't use this one?
It's like a scaled-down Beamer[1] for people who don't speak LaTeX :)
But regardless of these choices I think this method of writing plain text with a sprinkling of markup is great for all kinds of documents. Thanks to tools like pandoc I haven't had to touch MS Turd in years, but I can still produce better looking doc files than people who do use it (obviously I prefer pdf but sometimes the battle is not worth fighting).
Only have to what? Not the first title I've seen today where someone accidentally a word.
The title has been fixed, I noticed that too, and I'm always advocating for removing artificial barriers such as HN limit on titles. When truncating a title HN could for example show the complete one onmouseover or use some JS to expand the title.
you only have to do all these extra things in a convoluted syntax
deep down, you already knew
Once I have good data pre-processing and charting in R, what is the best way to easily automate much of the creation of presentations? Any experiences?
With my terminal focus I suspect I'd go with landslide before an electron app.