This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-16
Channels
- # announcements (3)
- # babashka (25)
- # beginners (71)
- # calva (18)
- # clj-kondo (52)
- # cljs-dev (94)
- # cljsrn (12)
- # clojure (33)
- # clojure-europe (52)
- # clojure-nl (2)
- # clojure-uk (27)
- # clojurescript (18)
- # clojureverse-ops (4)
- # datomic (64)
- # deps-new (27)
- # depstar (5)
- # events (5)
- # fulcro (5)
- # graalvm (12)
- # graalvm-mobile (82)
- # helix (2)
- # introduce-yourself (1)
- # juxt (5)
- # lsp (10)
- # malli (7)
- # missionary (1)
- # off-topic (41)
- # pathom (69)
- # pedestal (6)
- # re-frame (4)
- # reagent (8)
- # releases (9)
- # remote-jobs (8)
- # shadow-cljs (3)
- # sql (46)
- # tools-deps (44)
- # uncomplicate (1)
- # vim (83)
> Have you ever thought about turning the entire Clojurians Slack Archive into a static site? I've suggested this a couple of times already as well :) I wouldn't mind if the rendering of those static websites would be a bit behind the reality of Slack and would be re-generated every so often, but I understand there are trade-offs.
✅ 2
I've written up some of my thoughts of why I don't want to do static site rendering "as the primary" solution even though I love static sites in the README: https://github.com/oxalorg/clojurians-log-v2 I think adding static site generation as an add-on would not be a super bad idea (if needed ofcourse)