@t I'm having second thoughts about mkdocs, given the comments I'm getting on these polls: https://twitter.com/borkdude/status/1598983708417003522 https://mastodon.social/@borkdude/109449232257239390 People (me including) like the simplicity of a single page (as we have for https://book.babashka.org/) and to be able to just use ctrl-f for finding stuff. So I might still go with this solution for nbb as well
Yes, or just: - this already works if you just set up github pages in the respective project
E.g. here: https://babashka.org/scittle - but since scittle works in the browser, it uses itself for docs, which is an exception on the rule. I think we should just copy the way we do docs in babashka to the other projects, since most people voted for the single page over the mkdocs (although mkdocs looks more flashy).
we can structure the book to create "sub-documents" for each project - babashka - nbb - obb - and so on avoiding duplicate content and linking existing content in babashka I just wouldn't call it a book, I'd call it documentation: http://docs.babashka.org: babashka documentation http://docs.babashka.org/nbb: nbb documentation http://docs.babashka.org/obb: obb documentation do you think it works this way?