This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-22
Channels
- # announcements (3)
- # beginners (22)
- # braveandtrue (6)
- # calva (2)
- # cider (85)
- # cljdoc (1)
- # cljs-dev (21)
- # cljsrn (2)
- # clojure (70)
- # clojure-italy (9)
- # clojure-spec (1)
- # clojure-uk (144)
- # clojure-ukraine (6)
- # clojurescript (109)
- # cursive (59)
- # data-science (15)
- # datomic (40)
- # emacs (8)
- # fulcro (64)
- # funcool (8)
- # graphql (8)
- # hispano (3)
- # hoplon (7)
- # jobs-discuss (29)
- # leiningen (3)
- # luminus (2)
- # off-topic (13)
- # onyx (9)
- # parinfer (49)
- # pedestal (2)
- # portkey (8)
- # re-frame (10)
- # reagent (33)
- # reitit (13)
- # ring (2)
- # ring-swagger (16)
- # shadow-cljs (193)
- # spacemacs (1)
- # sql (19)
- # tools-deps (19)
there are so many resources for the basic syntax that its hard to find more intermediate topics, like how to take a design and translate it into a semantic markup that endures change
I've got a pretty good grasp of CSS patterns and fundamentals, but I'm just sitting here like "I guess I'll just make everything a div and style it later?"
@U250T6MFA for semantics, http://html5doctor.com/element-index/ is helpful
If you rely more on classes to specify initial styles, it may let you adapt the types of tags later to be more semantically useful. If there's obvious semantic tags to use for a situation, might as well use them over divs, though. 🙂
ahh, I see, that makes sense. easier to iterate if you're not relying on the user agent styles
I also have a lot of doubts about how to structure my DOM Should I keep everything flat? Should I nest just to make easier CSS? is possible do this layout without nest?