* Documentation Linter
@ 2020-05-28 4:00 Mark Van De Vyver
2020-05-28 15:51 ` [docs] " Khem Raj
0 siblings, 1 reply; 2+ messages in thread
From: Mark Van De Vyver @ 2020-05-28 4:00 UTC (permalink / raw)
To: docs
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Hi,
As mentioned in my previous message - which hasn't shown up yet - I'm new to Yocto and thought to try contribute via the docs.
I've made my comment on the conversion from DocBook, and this proposal will be impacted by that effort - hopefully a part of the conversion, and in a way that does not block or interfere.
The idea I had was to introduce a prose linting tool. Specifically, [Vale](https://errata-ai.gitbook.io/vale/).
Before going into the details, lets first establish if any of the following would be of use/value?
It would allow the project to achieve some consistency across paragraphs/pages/documents/repositories.
This would become more important if the project decided to exploit [Antora's](https://antora.org) ability to create a document from different repositories.
In such a case a repo could ensure its documentation had a closer 'fit' within the wider project documentation by ensuring it passed the same lint settings.
After the inital run/port is complete the documentation lint step could be added to the githooks that verify any new commit is green.
Thoughts?
--
Kind regards
Mark
Mark Van de Vyver, B.Bus(Hons), PhD(Dist)
[-- Attachment #2: Type: text/html, Size: 1296 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [docs] Documentation Linter
2020-05-28 4:00 Documentation Linter Mark Van De Vyver
@ 2020-05-28 15:51 ` Khem Raj
0 siblings, 0 replies; 2+ messages in thread
From: Khem Raj @ 2020-05-28 15:51 UTC (permalink / raw)
To: Mark Van De Vyver, docs
On 5/27/20 9:00 PM, Mark Van De Vyver wrote:
> Hi,
> As mentioned in my previous message - which hasn't shown up yet - I'm
> new to Yocto and thought to try contribute via the docs.
> I've made my comment on the conversion from DocBook, and this proposal
> will be impacted by that effort - hopefully a part of the conversion,
> and in a way that does not block or interfere.
>
> The idea I had was to introduce a prose linting tool. Specifically,
> [Vale](https://errata-ai.gitbook.io/vale/).
>
> Before going into the details, lets first establish if any of the
> following would be of use/value?
>
> It would allow the project to achieve some consistency across
> paragraphs/pages/documents/repositories.
> This would become more important if the project decided to exploit
> [Antora's](https://antora.org) ability to create a document from
> different repositories.
> In such a case a repo could ensure its documentation had a closer 'fit'
> within the wider project documentation by ensuring it passed the same
> lint settings.
> After the inital run/port is complete the documentation lint step could
> be added to the githooks that verify any new commit is green.
>
> Thoughts?
I really like the idea of linter.
> --
> Kind regards
> Mark
> Mark Van de Vyver, B.Bus(Hons), PhD(Dist)
>
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-05-28 15:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-28 4:00 Documentation Linter Mark Van De Vyver
2020-05-28 15:51 ` [docs] " Khem Raj
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.