Per-project or Centralized User Documentation?

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?

Start by reviewing the linked coreutils docs/book.toml and the existing coreutils-docs and findutils-docs documentation locations. Trace their maintenance status and compare the per-project and centralized options described in the issue. Done means the long-term documentation direction is decided and recorded for the affected projects.