From: TEC <firstname.lastname@example.org>
To: Bastien <email@example.com>
Cc: Diego Zamboni <firstname.lastname@example.org>, email@example.com
Subject: Re: [Announcement] New package ox-leanpub
Date: Mon, 14 Sep 2020 20:56:05 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Bastien <email@example.com> writes:
> this is more like: the main website should contain as little as
> possible while worg, being collaborative, should contain as much
> as possible.
Ok. I'll keep this in mind in future efforts. Sounds like the current
tools page should be shifted over, I'll try to do this in the future.
> I think for handling tiles and other fancy display layouts, it is
> safer to use a minimal css framework. I like https://bulma.io a lot,
> but as long as it is CSS-only, it's good.
Thanks to the CSS grid / flexbox, this is actually pretty trivial now :)
The most annoying thing is getting Org's export to wrap the div in a
At the moment it's quite hacky - it relies on browsers correcting
malformed XML and I'd desperately like to fix this but I'm not sure how.
<div id="outline-container-python" class="outline-3">
<div class="outline-text-3" id="text-python">
<img src="https://cdn.iconscout.com/icon/free/png-256/python-14-569257.png" alt="python-14-569257.png">
</p> # malformed here
<i>orgparse</i> creates a tree from an org file.
</a> # malformed here
> Then once this is done, we can let worg display tiles for some pages.
> Is this something you would like to explore?
I'll happily lay the groundwork in Worg's CSS.
All the best,
prev parent reply other threads:[~2020-09-14 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 10:56 [Announcement] New package ox-leanpub Diego Zamboni
2020-09-10 13:53 ` Bastien
2020-09-10 18:44 ` Diego Zamboni
2020-09-13 20:06 ` Bastien
2020-09-14 2:49 ` TEC
2020-09-14 5:26 ` Bastien
2020-09-14 6:13 ` TEC
2020-09-14 12:43 ` Bastien
2020-09-14 12:56 ` TEC [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).