dot-doom VS org-reveal

I switched from a hand-maintained config to Doom last year, and I can highly recommend it. It's very well organized, the community is very friendly and it works great. If you are interested, my config is at https://github.com/zzamboni/dot-doom/blob/master/doom.org.

This sets the default for all the emacs-lisp blocks in the file, but you can still selectively write other blocks to different files, or not at all by specifying :tangle no. This way you can easily tangle multiple destination files from a single Org file. For an example, you can see my doom.org file, from which Doom's init.el, config.el and packages.el are all tangled.

In my config I have a hook I can call after saving the .org file to automatically export it and update the open browser to the current slide. This makes the process of updating/viewing the presentation a lot smoother. You can find my config here: https://github.com/zzamboni/dot-doom/blob/master/doom.org#revealjs-presentations

Note that I said my "old config". A few months ago. I decided to try Doom Emacs. Over a couple of days, I ported most of the important bits of my decades-old, hand-maintained config, and in the process realized I could get rid of a lot of scaffolding (like the whole package-management bits in your config) by virtue of Doom's existing mechanisms, and also I could omit a lot of the configuration because Doom includes decent defaults for many things. I have not regretted moving to Doom. You can find my new config at https://github.com/zzamboni/dot-doom/blob/master/doom.org.

If you use use-package, it works well to define the package to be loaded :after org. I have lots of examples in my old emacs config, for example: (use-package ox-hugo :defer 3 :after org :custom (org-hugo-use-code-for-kbd t)) I now use Doom Emacs, but the same technique can be used with use-package!. For example, from my Doom Config: (use-package! ox-leanpub :after org :config (require 'ox-leanpub-markdown) (org-leanpub-book-setup-menu-markdown)) HTH

I think that org-reveal is able to deal with most of your requirements. At least I've used background images multiple times. Overlapping non-background images and text probably is difficult.

Is there somebody who knows the differences between org-reveal.el and org-re-reveal.el?

I now use emacs and Org mode for notetaking (with zetteldeft) and for drafting articles. I can export them into Word and get pretty close to the formatting I want. But I also use it for writing lecture notes and making slideshows for my classes using org-reveal.

What are the main differences between org-reveal (the one that's still maintained) and org-re-reveal?

I think `emacs` with `org-mode` _is_ the life management software. Also there are all kinds of "apps" built on top of this, such as https://github.com/yjwen/org-reveal/. For desktop, maybe this just serves the target group well enough, and there isn't much incentive to create a new platform, native apps or similar built on top of the org format. It would be a lot of work as well, compared to create a module for `emacs`, probably. For mobile, this doesn't work, and there are some initiatives, I have used orgzly a bit, http://www.orgzly.com/, it uses org files exactly like you describe, where the user doesn't have to be aware of the underlying format.

Org mode is my documentation secret weapon. I write books, presentations, technical documentation, and even literate data migration scripts.

Some added tips: ditaa is cool but you can also integrate mermaid [0] well and display inline images. There's a well-done revealjs [1] exporter. And you can also use results blocks as input to other code blocks!

PDF export is excellent and integrates well with some scripts I wrote to publish them to my remarkable. Great for writing and then reviewing specs on the go.

[0] https://mermaid-js.github.io/mermaid/#/

[1] https://github.com/yjwen/org-reveal

People seem to like using reveal.js via ox-reveal.

Thanks! I write them in org-mode and use org-reveal to export it to reveal.js/HTML5 format. I have some custom tweaks in org to allow customizing style without having to use an external .css, but most of it is using org-reveal features out of the box. My next blog post will most likely be about covering this topic in more detail, and provide an org template for this kind of presentation, as many have asked about how I've created the slides. I can add a ping here for you once the post is up (late January/early February).