emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: TEC <tecosaur@gmail.com>
Cc: Diego Zamboni <diego@zzamboni.org>, emacs-orgmode@gnu.org
Subject: Re: [Announcement] New package ox-leanpub
Date: Mon, 14 Sep 2020 14:43:35 +0200	[thread overview]
Message-ID: <877dswttoo.fsf@gnu.org> (raw)
In-Reply-To: <871rj4j37g.fsf@gmail.com> (TEC's message of "Mon, 14 Sep 2020 14:13:23 +0800")

Hi Timothy,

TEC <tecosaur@gmail.com> writes:

> My mental model was with the website as 'first class' information,
> and Worg as a 'secondary' wiki. This does seem like the ideal content to
> be collaboratively updated though.

this is more like: the main website should contain as little as
possible while worg, being collaborative, should contain as much 
as possible.

> I would. 


> The one other reason I lent towards the website initially
> though was because I felt that this could be best served by a tiled
> layout similar to https://orgmode.tecosaur.com/tools.html - which
> currently relies on some CSS not in Worg. That could be added inline,
> but that feels slightly hacky to me somehow.

We need to enhance worg css to make this possible.

> Let me know if there's a particular direction you'd like me to take with
> this.

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.

Then once this is done, we can let worg display tiles for some pages.

Is this something you would like to explore?

> Other than that, I don't believe I have an account on code.orgmode.org
> yet --- that could be helpful :P

Please send me a private email with your username and I'll create one
for you.



  reply	other threads:[~2020-09-14 12:44 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 [this message]
2020-09-14 12:56               ` TEC

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:

  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=877dswttoo.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=diego@zzamboni.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \


* 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).