Per-project or Centralized User Documentation?

[hwhsu1231]

Hello, Uutils Team,

I’ve been browsing through the projects maintained under the @uutils organization, and I noticed a few things:

1. Only coreutils and findutils have their own user documentation built with mdBook.
2. While coreutils-docs is actively maintained, the last commit of findutils-docs is about 2 years ago.
3. The book.toml configuration for coreutils-docs is titled "uutils Documentation". (Or just forgot it?)

Based on the above, I was wondering about the long-term plan for its user documentation:

1. Per-project: Each project gets its own independent docs (e.g., coreutils-docs, findutils-docs, etc.).
2. Centralized: Gathering all projects into a single uutils-docs user documentation.

Which direction is @uutils heading?

[sylvestre]

I don't think we discussed that :)
What do you recommend?

[hwhsu1231]

Well, I'm actually OK with both. Currently, I have started the incubation of the uutils-coreutils-docs-l10n project. So I just want to make sure the direction before publishing it.

[hwhsu1231]

Hello, @sylvestre

Regarding point 3 I mentioned at the beginning:

The book.toml configuration for coreutils-docs is titled "uutils Documentation". (Or just forgot it?)

Looking at the git blame, the line title = "uutils Documentation" was last updated nearly 5 years ago. Therefore, I’m inclined to believe the @uutils team simply forgot to update it. If that is the case, which of the following titles is preferred?

1. coreutils
2. Coreutils
3. uutils coreutils
4. Uutils Coreutils
5. coreutils Documentation
6. Coreutils Documentation
7. uutils coreutils Documentation
8. Uutils Coreutils Documentation

[naoNao89]

um, almost all the docs can be reused from GNU