Nikolaos Chatzikonstantinou <nchatz...@gmail.com> writes: > 3) Source code blocks + colors (server-side; not a .js coloring client-side)
Note that ox-html can fontify src blocks by itself. Via htmlize + CSS styles. > 1) I got colors in source blocks by post-processing with node.js + > highlight.js the raw HTML. Is it possible to write my own backend that > feeds the source block into my node app? Yes, of course. See my next answers. The whole export proces is hackable on multiple levels. > 2) I got several issues with how the org files are exported as HTML, > for example I may want to insert an <article> tag, I may want a div > around content and a div around nav bar, etc. Not everything can be > solved with #+HTML: tags because I don't have precise control of where > those go. Can the HTML backend be edited or do I have to write my own > backend? Check out https://orgmode.org/manual/Advanced-Export-Configuration.html > 3) I am very inexperienced with org backends. What good resources are > out there for this subject? See https://orgmode.org/manual/Adding-Export-Backends.html Org export backends can use inheritance. So, if you need to re-define a part of backend (if filters are not enough), you can always create a "subclass" by creating a "derived" backend. > Finally a highlight of the hacks I had to pull off: apparently > #+INCLUDE: will strip away inline backend information such as > @@html:<b>@@. I figured out that if I write something like > @@html@@a:@@:<b>@@, only the inner @@a:@@ is recognized and stripped, > which leaves me with what I originally wanted! (see > <https://github.com/createyourpersonalaccount/blog-v2/blob/main/content/publish.el#L14-L20>) May you show more concrete example? #+INCLUDE by itself does not remove export snippets. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
