Speaking as a library consumer, please don’t. Scaladoc is uniform, fairly task-oriented (assuming your API is), and integrates into pretty much all editors. I get somewhere between annoyed and enraged every time I’m interacting with a library that decides that they’d much rather shove me into their “curated” “cookbook” instead. Yes, I’m looking at you, scalajs-bundler. †
Wanting project-wide documentation is fine, but doesn’t belong together with your API reference anyway. What language you used for the implementation doesn’t really matter here, use Sphinx, Jekyll, or whatever to your heart’s content. But always ask yourself “does this belong in Scaladoc instead?” every time you add something new.
† I have nothing (else) against scalajs-bundler or the team behind it. It has seemed to work fine in what little I’ve used it so far. It’s just an example of a library that I recently really wished had uploaded their Scaladocs.