This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-05
Channels
- # adventofcode (8)
- # aleph (42)
- # announcements (4)
- # beginners (157)
- # boot (4)
- # calva (1)
- # cider (6)
- # cljdoc (8)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (50)
- # clojure-europe (9)
- # clojure-italy (16)
- # clojure-nl (2)
- # clojure-russia (6)
- # clojure-spec (59)
- # clojure-uk (25)
- # clojurescript (20)
- # core-async (41)
- # cursive (30)
- # data-science (9)
- # datomic (20)
- # fulcro (28)
- # kaocha (9)
- # nrepl (1)
- # off-topic (3)
- # om (3)
- # pathom (10)
- # re-frame (8)
- # reagent (2)
- # ring-swagger (38)
- # rum (9)
- # shadow-cljs (209)
- # spacemacs (7)
- # tools-deps (11)
- # vim (6)
- # yada (2)
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?
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
This sounds like an interesting use case. People can self host at the organization level and can have pretty docs 😄
I agree 😄