From: TEC <tecosaur@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Diego Zamboni <diego@zzamboni.org>, emacs-orgmode@gnu.org
Subject: Re: [Announcement] New package ox-leanpub
Date: Mon, 14 Sep 2020 20:56:05 +0800 [thread overview]
Message-ID: <87v9ggh5zu.fsf@gmail.com> (raw)
In-Reply-To: <877dswttoo.fsf@gnu.org>
Bastien <bzg@gnu.org> 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
link.
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.
Example:
#+begin_src html
<div id="outline-container-python" class="outline-3">
<h3 id="python">Python</h3>
<div class="outline-text-3" id="text-python">
<p>
<a href="https://github.com/karlicoss/orgparse">
<img src="https://cdn.iconscout.com/icon/free/png-256/python-14-569257.png" alt="python-14-569257.png">
</p> # malformed here
<p>
<i>orgparse</i> creates a tree from an org file.
</a> # malformed here
</p>
</div>
</div>
#+end_src
> 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,
Timothy.
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]
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9ggh5zu.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=bzg@gnu.org \
--cc=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).