This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-04
Channels
- # announcements (1)
- # architecture (18)
- # aws (7)
- # babashka (63)
- # beginners (38)
- # bristol-clojurians (1)
- # circleci (1)
- # clj-kondo (10)
- # clojars (4)
- # clojure (159)
- # clojure-berlin (3)
- # clojure-europe (4)
- # clojure-italy (7)
- # clojure-losangeles (6)
- # clojure-nl (7)
- # clojure-spec (3)
- # clojure-uk (109)
- # clojurescript (54)
- # css (1)
- # cursive (38)
- # data-science (2)
- # datascript (3)
- # datomic (14)
- # docker (2)
- # duct (11)
- # fulcro (47)
- # jobs (8)
- # jobs-discuss (3)
- # kaocha (4)
- # malli (3)
- # nyc (2)
- # off-topic (30)
- # overtone (3)
- # re-frame (17)
- # reagent (33)
- # shadow-cljs (29)
- # spacemacs (3)
- # specter (4)
- # tools-deps (13)
- # xtdb (13)
Hello css friends!
After dipping my feet in a couple ideas: Flex, Grid, Atomic Design Atomic Layout, tailwind css...I'm starting to reach the conclusion that the idea solution build a processor from your clojurescript to css. Simply put anywhere the processor (probably a macro?) reads
{:styles {:font-size "40px"}}
in your cljs file the outputted js would contain something like class=<id> and a css file would be created with .<id> {font-size "40px"}. This mapping seems to be all that tailwind and atomic design are doing. (please let me know if thats wrong). But i don't like that the names are munged fz -> font-size. This seems a needless abstraction layer. I'm positive this is ground that has been walked a million times before, I have probably looked at cljs libs that are doing this, but wasn't sure what they were or what the problems they were solving meant.