doom-emacs VS dot-doom

You can take a look at the default init.el file for Doom emacs here, as you can see, there is a :lang section where you can uncomment support for commonly used languages. Although you generally don't change the init.el file too much, usually, it is there to load your actual config files. If your language is not supported out of the box, there are ways to add packages (a.k.a. "plug-ins") in packages.el. And you can add customizations in config.el.

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