From: "Mark Van De Vyver" <mark@taqtiqa.com>
To: docs@lists.yoctoproject.org
Subject: Re: Possible changes to the project docs
Date: Wed, 27 May 2020 22:49:11 -0700 [thread overview]
Message-ID: <18306.1590644951892762393@lists.yoctoproject.org> (raw)
In-Reply-To: <CAP71WjzD-AMauxpgbydY2fryU6+JU599UPRPXi_c582WvvfV6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
Hmm, it seems the interwebs ate my prior message. TLDR;
Considering AsciiDoc, MkDoc-Materialize, Docusarus, Sphinx and Antora
* A switch from DocBook is a net benefit regardless of what you switch too.
* Making docs more accessible to dev and user contributors is the key.
* I regard ascidoc/md/rst as near enough that they don't swing the decision - in terms of being approachable to devs and users.
* A potential discriminator is l10n/i18n - on the face of it they all seem to be imperfect (wip) and adequate.
* Is there any other strategic benefit to be obtained?
I think so. Looking at https://antora.org/ this stands out:
*The ability to retrieve and aggregate all the content from different git repositories.*
This provides the following headroom:
* Move documentation into the repo that holds the related code. Bringing documentation closer to devs who are more likely to write some preliminary documentation and correct documentation errors/ambiguities.
* Allow individual repo's/tools to evolve at their own pace - a release that repo/tool X would like to make 'yesterday' can be made and everyone can be confident the docs are still consistent (assumes that tool/repo-Y does not make any statements about tool/repo-X in the Y-docs)
* Allow the project to treat a repo as a 1st class citizen even if it is not under the openembedded.org or yoctoproject.org
* Corollary: Allow any repo outside of openembedded.org or yoctoproject.org to incorporate whichever of the tools/repos they need (git cloning & forking model allows/encourages that) and present documentation that is integrated and targeted (Antora could - eventually - allow/encourage that).
* Give the Yocto-project flexibility in how to organize itself going forward - documentation is not an impediment.
Of course there is a learning curve and the docs need to be refactored back to their home tool/repo.
To my mind there is a categorical distinction that can be made between the DocBook alternatives.
The questions is whether any of the above conjectures are of value or attractive?
HTH?
--
Kind regards
Mark
Mark Van de Vyver, B.Bus(Hons), PhD(Dist)
[-- Attachment #2: Type: text/html, Size: 2441 bytes --]
next prev parent reply other threads:[~2020-05-28 5:49 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 [this message]
2020-05-28 7:54 ` 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
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=18306.1590644951892762393@lists.yoctoproject.org \
--to=mark@taqtiqa.com \
--cc=docs@lists.yoctoproject.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox