This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-17
Channels
- # beginners (45)
- # boot (33)
- # chestnut (9)
- # cider (2)
- # cljs-dev (24)
- # cljsrn (1)
- # clojure (114)
- # clojure-conj (3)
- # clojure-dev (3)
- # clojure-dusseldorf (3)
- # clojure-greece (5)
- # clojure-italy (22)
- # clojure-russia (10)
- # clojure-spec (12)
- # clojure-uk (19)
- # clojurescript (117)
- # core-async (16)
- # cursive (3)
- # data-science (1)
- # datomic (5)
- # docs (13)
- # emacs (1)
- # fulcro (13)
- # graphql (1)
- # hoplon (20)
- # immutant (3)
- # jobs (1)
- # juxt (12)
- # lein-figwheel (1)
- # luminus (4)
- # off-topic (12)
- # onyx (61)
- # portkey (1)
- # re-frame (21)
- # reagent (26)
- # ring-swagger (38)
- # rum (1)
- # shadow-cljs (222)
- # slack-help (4)
- # spacemacs (11)
- # specter (67)
- # uncomplicate (236)
@seancorfield hi sean. You're working on some improvement for clojure docs, Am I right?
@lxsameer I was part of a group of folks that discussed a "documentation hub" at Clojure/conj, yes.
The thinking is that if we can create a central hub of documentation for Clojure symbols (across all libraries), with an API that allows any tooling to retrieve it, we can improve the ecosystem for everyone. Right now, it's very much in the "ideas" phase. We don't have any concrete plans.
I think there will be more discussions -- somewhere, not sure where -- to flesh out the approach and build a list of things we need to do and people we need to talk to. Specifically, we need to get buy in from all the tooling projects and existing Clojure doc sites, that pulling documentation-as-data from a central hub is acceptable and that they would implement it.
It's worth bearing in mind that the Clojure/core folks are happy to see the community take on this work but are probably not going to be involved themselves -- so clojure-dev is not an appropriate venue for the discussion around docs.
But if you have ideas about improving Clojure-the-language, clojure-dev is appropriate.