From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aaron Ecay <aaronecay@gmail.com>
Subject: Re: RFC: Proposal for an Org Special Block for ox-html
Date: Fri, 25 May 2018 15:19:54 +0100
Message-ID: <87d0xj7r79.fsf@gmail.com>
References: <CAFyQvY2YoLDpM9PWLV86FwvPOVkuxg9O8KdryG3z=5QRm7Aujg@mail.gmail.com>
	<87o9h56jdl.fsf@gmail.com>
	<CAFyQvY2j1=qh37wad3V-u0XUziih2-tuNjFUrUjiru23q0riJg@mail.gmail.com>
	<87lgc87vf1.fsf@gmail.com>
	<CAFyQvY1pNWwp0-fh77B1JFRbrQoCkW8FNTsZgfquCCixhq_wUA@mail.gmail.com>
	<87in7c7tye.fsf@gmail.com>
	<CAFyQvY2uSiK94WAOU7aBsf=iXOFdgjU_SdouFwYJma_updfJTw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44591)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1fMDZa-0001Wk-6J
	for emacs-orgmode@gnu.org; Fri, 25 May 2018 10:20:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1fMDZW-0000rx-7b
	for emacs-orgmode@gnu.org; Fri, 25 May 2018 10:20:02 -0400
Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]:35842)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <aaronecay@gmail.com>) id 1fMDZW-0000rD-1c
	for emacs-orgmode@gnu.org; Fri, 25 May 2018 10:19:58 -0400
Received: by mail-wr0-x236.google.com with SMTP id k5-v6so9551262wrn.3
	for <emacs-orgmode@gnu.org>; Fri, 25 May 2018 07:19:57 -0700 (PDT)
In-Reply-To: <CAFyQvY2uSiK94WAOU7aBsf=iXOFdgjU_SdouFwYJma_updfJTw@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>, emacs-org list <emacs-orgmode@gnu.org>

Hi Kaushal,

2018ko maiatzak 24an, Kaushal Modi-ek idatzi zuen:

> That's why I am using (org-element-property :attr_html special-block) in
> the code to get the raw values to #+attr_html.

I=CA=BCm not sure I made myself clear in the previous message.  In any case,
this org:

=E2=95=AD=E2=94=80=E2=94=80=E2=94=80=E2=94=80
=E2=94=82 #+attr_html: :open t
=E2=94=82 #+begin_details
=E2=94=82 #+begin_summary
=E2=94=82 Open for details
=E2=94=82=20
=E2=94=82 More summary.
=E2=94=82 #+end_summary
=E2=94=82 Many details here.
=E2=94=82 #+end_details
=E2=95=B0=E2=94=80=E2=94=80=E2=94=80=E2=94=80

exports to this HTML (using current-ish master with no additional
modifications beyond the tweak to org-html-html5-elements):

=E2=95=AD=E2=94=80=E2=94=80=E2=94=80=E2=94=80
=E2=94=82 <details open=3D"t">
=E2=94=82 <summary>
=E2=94=82 <p>
=E2=94=82 Open for details
=E2=94=82 </p>
=E2=94=82=20
=E2=94=82 <p>
=E2=94=82 More summary.
=E2=94=82 </p>
=E2=94=82 </summary>
=E2=94=82 <p>
=E2=94=82 Many details here.
=E2=94=82 </p>
=E2=94=82 </details>
=E2=95=B0=E2=94=80=E2=94=80=E2=94=80=E2=94=80

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.

> That would be great. I myself wasn't sure if I should bring that up to Org
> core.. I had just implemented #+attr_css support for ox-hugo.
>=20
> It looks like this:
>=20
> #+attr_html: :class red-text
> #+attr_css: :color red
> - Red list item 1
> - Red list item 2
>=20
> Above will generate <style .red-text { color: red; } </style><div
> class=3D"red-text">..</div>, with that list in the div.

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 =E2=80=9Cstyle=E2=80=9D and =E2=80=9Cdiv=E2=80=9D elements.

>=20
> You can find many such examples in
> https://kaushalmodi@github.com/kaushalmodi/ox-hugo/blob/master/test/site/=
content-org/all-posts.org,
> and the implementation in
> https://github.com/kaushalmodi/ox-hugo/blob/master/ox-blackfriday.el. Let
> me know what you think if you have a chance to review those.

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.

On a broader level, both org and html have well-defined syntax, and
easy-to-work-with programmatic representations in lisp.  Markdown...does
not.  Since markdown-ing a valid HTML document should be a no-op
(AFAIK), I don=CA=BCt 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=CA=BCs user=
s).
If the set of QOL improvements is empty, then the custom backend would
disappear entirely.  Less code for the same features =3D maintenance win in
my book.  YMMV of course...

--=20
Aaron Ecay