I've even gone so far as to remove the concept of "live data sync" from all my apps, partially because it's so incredibly error prone and hard to get right, partially because it tends to make software seem laggy and slow since it shows stale data while loading live data in the background, and partially because usually it's unneeded as a built-in feature if you're just using files, which can then be synced with any of the many file syncing service (iCloud, Dropbox, OneDrive, Box).
Although it's very doubtful other power users will adopt internet-less lives, if more of us did, not only would we be more productive, but we'd all have more incentive to make "offline-ready" a much better experience and even move to "offline-first" like I aim to.
Your attitude is mildly depressing, not because its wrong, just that it's coming from a place where 'offline' is niche.
For years I've been using Deckset for all my presentations. Being able to just edit a text file to write and update slides is a massive advantage.
I usually export them as pdf, which 99% of conferences are happy with.
A big bonus is that you can now version control your slides, allow them to get forked, etc.
If you're curious to see what those slides look like, check any of my previous talks .
And: yes, deckset (as I learned today) sounds a lot like markdeck, feature-wise... I will have a closer look on that and compare these tools.
We had more than 200 commits at the end of one day, 150 of them to solve minor layout problems... with a (feeled) round-trip-time of 10-20seconds, that became frustrating quite fast...
can you commit with --amend instead to avoid creating new commits every time?
I've used reveal.js for a while. I found it most useful when I did presentations for multiple meetups on the same open source project. I created a little build tool that let me re-use slides for Ruby, Scala and Python meetups (the service was written in Scala, client in Python and devops was all Ruby, but that's since been migrated to Docker):
Tools like this are great if you have several similar presentations. Some of the additions in Markdeck are things I've kinda hacked in (like terminal output players). Still with a recent presentation where I did everything from scratch, I used the same build process and found it felt a bit much for something that didn't require the shared-slides use case and I wondered if I would have just saved time writing it in a GUI/WYSIWYG tool like OpenOffice or Powerpoint.
GP knows. You were being commended for it. :-)
btw: with markdeck, I tried the completely different approach: do not dependent on an uplink, neither when authoring, nor when presenting...
I tried to help by putting in a change request, but couldn't exactly figure out where the slides were coming from.
but for now: the `showcase` gets rendered from the `examples` folder, here.
ERROR: Version in "./docker-compose.yaml" is unsupported. ... specify a version of "2" (or "2.0") ...
markdeck uses version 3.2
I guess it's time to finally upgrade to Ubuntu 18 LTS. I just needed a reason. =)
p_slides doesn’t have any dependency that doesn’t run in the browser and its files can be checked into SCM which makes collaboration easy.
But when you don't need any of the above, then markdeck in fact has no advantage over plain reveal.js and markdown.
DeckRocket looks cool, but unfortunately I cannot build it on my machine (to convert the app from swift 2.4 to swift 3 or even higher, xcode8 or so is needed... and that is not a priority at the moment)
Okay, that made me curious and I gave it a try:
please have a look at the slides.md and the resulting pdf
If it requires a VCS isn't everything collaborative?
It's just that I would expect it to be built in if you're mentioning it in the title of the submission like that.
People don't tend to notice this as much though, and they are more concerned with familiarity or speed-of-production of the slides rather than make the slides effective for the audience. But hey, that same issue can be raised for most PowerPoint presentations, too. People just don't know how to make good slides and just take whatever is easiest for them.
But even embedded images implies uninspiring slides to me.
For example they have a system that allows you to add source code to a slide, but then don't you want to be annotating that code? Adding arrows, lines, highlighting bits, breaking it apart, etc?
As to this: I just don't get what's so special about this. I especially don't get, what this could do, what plainly putting your presentation into git doesn't do already? Apparently behind the curtains (which probably does not concern people who do `curl <url> | bash` stuff...) it's using pandoc to convert md to a reveal-js presentation and using a node-based live-server for display. Not even sure if speaker notes work (or if you have to use the reveal.js internal server for that)...
Also, this is a security nightmare, as a ton of boilerplate-dockercode/npm-packages/random-binaries is necessary for just about nothing, as in the end it's just downloading the pandoc-binary from github to a docker-container (well, building pandoc was to hard apparently). I'm scrambling my head, what this means for security in applications developed by people lead by the poster if he goes forward like this.
So many people end up writing what should be their presentation notes as their slide content. Personally I think you're better off with a holding image and move your content to the presenter notes section.
I've used revealjs.com and hovercraft  in the past but usually end up on GSuite Slides to throw things together quickly. Slides (like PowerPoint) can't do branching presentation paths though :(
the resulting slides can be as colourful (and text-less) as you want...
for convenience, here is a list of all alternatives mentioned (in no particular order):
(i added a quick but incomplete review of key aspects of each tool. almost all are using markdown and support pdf export)
https://arnehilmann.github.io/markdeck/ (reveal.js docker)
https://pandoc.org/MANUAL.html#producing-slide-shows-with-pa... (export-to: S5 DZSlides Slidy Slideous reveal.js pdf ppt)
https://godoc.org/golang.org/x/tools/cmd/present (go-present-markup local-go-server "can't find documentation of how to actually use it")
http://slideshow-s9.github.io/ (commandline-tool browser-preview many-templates)
https://github.com/FormidableLabs/spectacle (react-based presenter-mode local-node-server)
https://gitpitch.com/ (online-service 'desktop version is docker based and not free')
https://yhatt.github.io/marp/ (electron-app live-preview)
https://www.deckset.com/ (osx-only not-free)
markdeck uses pandoc as converter; and, yes, there is a LaTeX-Importer available, too (besides the Markdown-Importer used now by markdeck).
So, on a per-file basis, it should be quite easy to support other input formats than markdown (restructerdText might be another candidate).
Embedding LaTeX in markdown might be a little bit more trickier, because we already use html-tags where markdown is not expressive enough... sigh
I'm not trying to poo on the OP or Marp. I'm actually interested in using a project like these and would be keen to see some kind of "why x over y" section in the readme.
i really liked the live preview and the output to pdf.
i do prefer pdf over web-based presentations because they are easier to share without a webbrowser (just send a document) (and they can still be viewed in a browser).
most irritating was the fact that i could not use my preferred editor. i haven't checked all the recommendations here, but i'll be looking for a combination if something like markdown in vim with live preview in a browser or pdf viewer
And markdeck has a standalone-exporter: it generates a single html file with all resources embedded (url-data, base64, ...); one file to send/open/view, but with working animations and the like (even the terminal session works)
It's too bad, because these tools are fantastically useful, but it doesn't look like any one managed to gather enough adoption to get critical mass around it.
The site guidelines too: https://news.ycombinator.com/newsguidelines.html
(Your comment would be much better without the first sentence.)
Anyway, it exports pdf.
Not contempt. Instead of a lukewarm indifference-couched-in-praise, I'm giving you real feedback. People should cherish that. (I know I do.)
My priority isn't esoteric, it's the priority of 99.9% of those doing slide presentations. For the vast majority of people the problem they need solved is "will this work on their junk setup I first saw five minutes ago", not graphviz integration.
> Anyway, it exports pdf.
If so, this should be point #1 on your README, in big bold letters. In reality, of course, there's caveats, and the exported PDF will mostly fail in real-world conditions.
This is not surprising: the priorities are off, the features tested aren't the ones that need testing, and so the tool isn't solving the problem that really needs to be solved.
Again, please don't take this as contempt. Best wishes and I hope you set your priorities in order.
And of course ignoring the fact that your "first concern" might not be so important for other people, who either seldom need export or can use HTML as an export format.
No, it's definitely not. Most people I see (I see a lot) are presenting from their own laptops.
For the record I'm not involved in this project.