This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-07
Channels
- # adventofcode (4)
- # aleph (1)
- # architecture (9)
- # beginners (67)
- # boot (7)
- # boot-dev (12)
- # cider (3)
- # clojure (166)
- # clojure-austin (3)
- # clojure-estonia (1)
- # clojure-greece (2)
- # clojure-russia (5)
- # clojure-spec (1)
- # clojure-uk (4)
- # clojurescript (19)
- # cursive (1)
- # data-science (5)
- # datascript (4)
- # datomic (3)
- # docs (10)
- # emacs (24)
- # events (4)
- # fulcro (16)
- # graphql (8)
- # hoplon (2)
- # jobs-discuss (1)
- # leiningen (5)
- # off-topic (2)
- # planck (30)
- # re-frame (20)
- # reagent (36)
- # ring (3)
- # shadow-cljs (5)
- # spacemacs (1)
- # specter (2)
Would be curious if other people have thoughts on a centralized documentation platform for Clojure libraries: https://clojureverse.org/t/creating-a-central-documentation-repository-website-codox-complications/1287 Especially if you’re working on some documentation tooling yourself 🙂 /cc @arrdem @sekao
@martinklepsch lotta thoughts, where's best to engage with you on this?
@arrdem that forum thread is a good start, DMs also welcome ofc
This is a really good writeup of the user flow for learning GraphQL: https://github.com/graphql/graphql.github.io/blob/source/notes/NewSiteArchitecture.md.
@arrdem Re your reply: are you aware of codox support for markdown docs? It seems to me that this could address the guides/cookbooks etc. part of documentation?
@martinklepsch I am aware of that support, I just don't think it goes nearly far enough and frankly I've never seen anyone use it.
Ok just checking, will read again + reply tmrw :) thanks for weighing in! 👍
There is a twitter account if you want to have new stuff pop up in your feed