Is cljdoc only suited for libraries, or could I use it to build nice documentation for an internal project? That I would commit under say a local folder and people would just open using a file:// url?
This sounds like an interesting use case. People can self host at the organization level and can have pretty docs π
I agree π
And perhaps a business case?
I mean, ideally Iβd like if I can build and commit the generated docs side-by-side with my code. I donβt mind doing it manually. But setting up codox from scratch seems a little bit of a waste of time, esp. since cljdoc has much better looking output.
hey. It's not really intended for that type of use case but you could commit an offline bundle into source control and view that using file://
urls
Here's an example off an offline bundle: https://cljdoc.org/download/lambdaisland/uri/1.1.0
Alternatively you could also run a cljdoc instance on your own infrastructure. Depending on how many libraries/releases/developers there are one might make more sense than the other