All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Mark Van De Vyver <mark@taqtiqa.com>, docs@lists.yoctoproject.org
Subject: Re: [docs] Possible changes to the project docs
Date: Thu, 28 May 2020 10:47:00 +0200	[thread overview]
Message-ID: <CAP71WjzDb2kMV1J+t6vRVogqo+dZ=rr==SsAQcXzBoSZt9E5og@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2005280427160.515316@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

On Thu, May 28, 2020 at 10:29 AM Robert P. J. Day <rpjday@crashcourse.ca>
wrote:

> On Thu, 28 May 2020, Nicolas Dechesne wrote:
>
> > hi Mark,
> >
> > thanks a lot for joining the discussion! This is very helpful and much
> appreciated.
>
>   ... snip ...
>
> >       Considering AsciiDoc, MkDoc-Materialize, Docusarus, Sphinx and
> Antora
> >
> >       * A switch from DocBook is a net benefit regardless of what you
> switch too.
>
>   the one aspect of docbook i will miss is actual semantic markup
> which can then be customized with stylesheets, but that benefit is
> outweighed by all the downsides of the complexity. and given that i'm
> poring over the sphinx docs right now and playing with it, yeah,
> sphinx is my choice. :-)
>

Ah, nice. If you have any patches that are relevant for the sphinx proof of
concept, please share them. I started a sphinx2 branch here:
https://git.linaro.org/people/nicolas.dechesne/yocto-docs.git/log/?h=sphinx2

with a 'better' commit log structure. I have also done the pandoc
conversion for all manuals.


>
> rday
>

[-- Attachment #2: Type: text/html, Size: 1761 bytes --]

  reply	other threads:[~2020-05-28  8:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 10:19 Possible changes to the project docs Richard Purdie
2020-04-15 15:21 ` [docs] " Trevor Woerner
2020-04-16 16:51   ` Robert P. J. Day
2020-04-16 17:00     ` Nicolas Dechesne
2020-04-16 17:46       ` Robert P. J. Day
2020-04-16 17:55         ` Nicolas Dechesne
2020-04-16 18:06           ` Robert P. J. Day
2020-05-21 20:41             ` Mark Morton
2020-05-25  7:33               ` Nicolas Dechesne
2020-05-26 10:43                 ` Nicolas Dechesne
2020-05-28  5:49                   ` Mark Van De Vyver
2020-05-28  7:54                     ` [docs] " Nicolas Dechesne
2020-05-28  8:23                       ` Robert P. J. Day
2020-05-28  8:29                       ` Robert P. J. Day
2020-05-28  8:47                         ` Nicolas Dechesne [this message]
2020-06-01  1:19                       ` Mark Van De Vyver
2020-06-12 11:52                   ` [docs] " Nicolas Dechesne
2020-06-15 19:52                     ` Nicolas Dechesne
2020-04-15 15:37 ` Nicolas Dechesne
2020-04-15 17:13   ` [docs] " akuster
2020-04-16 16:47 ` Robert P. J. Day

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP71WjzDb2kMV1J+t6vRVogqo+dZ=rr==SsAQcXzBoSZt9E5og@mail.gmail.com' \
    --to=nicolas.dechesne@linaro.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=mark@taqtiqa.com \
    --cc=rpjday@crashcourse.ca \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.