Hi everyone, I'm happy to announce that my package ox-leanpub is now available in MELPA. Ox-leanpub contains Org-mode export backends to produce books in the correct structure and format for publication with Leanpub (https://leanpub.com/). It allows you to write your book entirely in Org mode, and completely manages the production of the necessary files for Leanpub to be able to render your book. I use this package to publish most of my books published on Leanpub (https://leanpub.com/u/zzamboni). You can find full documentation at https://github.com/zzamboni/ox-leanpub (original source is kept in GitLab, but the documentation is more readable in GitHub). Please check it out! Let me know if you have any feedback or questions. I would also like to thank everyone in this community for your support and willingness to answer my questions :) All the best, --Diego
Hi Diego, Diego Zamboni <diego@zzamboni.org> writes: > I'm happy to announce that my package ox-leanpub is now available in > MELPA. I added a link to https://orgmode.org/worg/org-tools/ Links to Org external exporters should perhaps have a dedicated section and/or page, especially if/when we will move some out of Org's core. Thanks for writing and sharing this! -- Bastien
[-- Attachment #1: Type: text/plain, Size: 683 bytes --] Hi Bastien, Thanks! I agree it would be nice to have a comprehensive list of org exporters in worg - although usually a search for "org export <whatever>" points in the correct direction :) Best, --Diego On Thu, Sep 10, 2020 at 3:53 PM Bastien <bzg@gnu.org> wrote: > Hi Diego, > > Diego Zamboni <diego@zzamboni.org> writes: > > > I'm happy to announce that my package ox-leanpub is now available in > > MELPA. > > I added a link to https://orgmode.org/worg/org-tools/ > > Links to Org external exporters should perhaps have a dedicated > section and/or page, especially if/when we will move some out of > Org's core. > > Thanks for writing and sharing this! > > -- > Bastien > [-- Attachment #2: Type: text/html, Size: 1258 bytes --]
Hi Diego,
Diego Zamboni <diego@zzamboni.org> writes:
> Thanks! I agree it would be nice to have a comprehensive list of org
> exporters in worg - although usually a search for "org export
> <whatever>" points in the correct direction :)
Indeed, such a list would be helpful.
Is anyone interested in working on this?
--
Bastien
Bastien <bzg@gnu.org> writes:
>> Thanks! I agree it would be nice to have a comprehensive list of org
>> exporters in worg - although usually a search for "org export
>> <whatever>" points in the correct direction :)
>
> Indeed, such a list would be helpful.
>
> Is anyone interested in working on this?
I'd happily add that to my website revamp, in a similar manner to the
"Tools" page.
Timothy.
Hi Timothy,
TEC <tecosaur@gmail.com> writes:
> Bastien <bzg@gnu.org> writes:
>
>>> Thanks! I agree it would be nice to have a comprehensive list of org
>>> exporters in worg - although usually a search for "org export
>>> <whatever>" points in the correct direction :)
>>
>> Indeed, such a list would be helpful.
>>
>> Is anyone interested in working on this?
>
> I'd happily add that to my website revamp, in a similar manner to the
> "Tools" page.
I think it would be best to store this information on Worg rather than
on the website: the website should be for quasi-immutable things (with
only a few people having write access), while worg is a perfect place
for things that can be collaboratively updated.
Would you volunteer to build the list on Worg? It does not need to be
complete, just regularily updated.
Thanks!
--
Bastien
Bastien <bzg@gnu.org> writes: > I think it would be best to store this information on Worg rather than > on the website: the website should be for quasi-immutable things (with > only a few people having write access), while worg is a perfect place > for things that can be collaboratively updated. 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. > Would you volunteer to build the list on Worg? It does not need to be > complete, just regularily updated. 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. Let me know if there's a particular direction you'd like me to take with this. Other than that, I don't believe I have an account on code.orgmode.org yet --- that could be helpful :P Timothy.
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. Thanks! > 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. Thanks! -- Bastien
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.