Iʼm not sure I made myself clear in the previous message. In any case,
this org:
╭────
│ #+attr_html: :open t
│ #+begin_details
│ #+begin_summary
│ Open for details
│
│ More summary.
│ #+end_summary
│ Many details here.
│ #+end_details
╰────
exports to this HTML (using current-ish master with no additional
modifications beyond the tweak to org-html-html5-elements):
╭────
│ <details open="t">
│ <summary>
..│ </details>
╰────
which displays in the open state in a browser (in any event, in Chromium
66). So I think what you want already exists for this feature.
What is wrong with:
#+attr_html: :style color:red;
- red list 1
- red list 2
?
That works in vanilla org today (exporting to html), without needing to
generate extra “style” and “div” elements.
I looked at the file briefly. I had trouble determining what might
represent missing features in ox-{html,md}, and what was included to
work around quirks in a particular implementation of markdown.
I donʼt understand why you are bothering with markdown at all
in your usecase. If it was me, I would just generate HTML from org and skip the markdown step entirely.
It seems to me like you could get rid of ox-blackfriday, leaving behind
only a small ox-html-plus-plus containing whatever QOL improvements to
the vanilla html backend suited your taste (and that of ox-hugoʼs users).
If the set of QOL improvements is empty, then the custom backend would disappear entirely. Less code for the same features = maintenance win in my book. YMMV of course...
Kaushal Modi