This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-29
Channels
- # aleph (1)
- # announcements (10)
- # aws (1)
- # beginners (110)
- # calva (4)
- # cider (26)
- # clj-kondo (14)
- # cljdoc (24)
- # cljsrn (16)
- # clojure (76)
- # clojure-europe (3)
- # clojure-ireland (2)
- # clojure-italy (15)
- # clojure-nl (8)
- # clojure-spec (23)
- # clojure-sweden (4)
- # clojure-uk (92)
- # clojurescript (37)
- # cursive (19)
- # datomic (59)
- # duct (1)
- # emacs (4)
- # fulcro (7)
- # graalvm (7)
- # graphql (1)
- # hoplon (69)
- # jobs (4)
- # jobs-rus (1)
- # kaocha (2)
- # leiningen (5)
- # luminus (2)
- # pathom (8)
- # reagent (6)
- # reitit (11)
- # spacemacs (12)
- # sql (3)
- # tools-deps (9)
- # unrepl (1)
- # vim (57)
CIDER’s documentation site got a big update https://metaredux.com/posts/2019/05/29/cider-mx-reloaded.html

This nicely lays out the rationale for switching from RTD to Antora - would be curious what you found missing from cljdoc for it to be considered as an option :)
I assume the custom domain is a big part of it?
Yeah, that was part of it, but the biggest part was that CIDER is not a single projects and it’s code is spread over multiple repos. I use cljdoc for everything Clojure (and I love it), but I obviously can’t deploy there docs for CIDER’s Elisp code. And more importantly - there’s no easy way to create just pull doc modules from all the repos and publish them together under some meta project.
I guess CIDER’s case is something pretty rare, though. Bigger projects generally have to rely on some custom sites.
Just published Atom's package to Socket REPL Chlorine, version 0.1.7. Fixed a huge (and strange bug!) on MacOSX where the package would fail to run and activate on OSX version >= 10.13. Discussions on #chlorine channel 🙂
