I did some other improvements with the convertor. I am quite happy with the
result now. There are still some glitches, but I think it would be manageable
to be fix them manually.
Then I tested with the website. It works nicely apart from the home page and
the download page. These two pages are
> Le 30 déc. 2014 à 17:16, Jean-Louis Boudart a
> écrit :
>
> Hi Nicolas,
>
> Definitively yes !
>
> I was trying a similar approach with Jelly/markdown, but due to several
> issues and lack of time i stopped there.
> I'm fine with asciidoc.
>
> Could you tell us how you imagine the next st
Hi Nicolas,
Definitively yes !
I was trying a similar approach with Jelly/markdown, but due to several
issues and lack of time i stopped there.
I'm fine with asciidoc.
Could you tell us how you imagine the next steps ?
Will xooki only be used to produced toc ?
What will be the flow to edit docu
Hi,
I like xooki because it manages well the templating of the web pages, and it
manage well how to build a toc. I hate when documentation is not « browsable »,
like in a wiki, and xooki handle it well.
But is is quite slow, generating Ivy’s documentation can takes minutes.
And on macos jrunscr
