https://htmx.org logo
Join Discord
Powered by
# missing_dot_css
  • g
    I like this, in particular, because it goes against the current "Silicon Valley" way of doing things, which is my first indication that it might be the right way to go.
  • g
    Does this make enough sense on its own for this discussion? Or, should I flesh this idea out more with an example to make clear what I'm getting at?
  • g
    My grammar checker wants me to say "at what I'm getting" -- but I'm just not gonna. 😛
  • m
    Yes that was my idea with high powered classes and layouts could fall under this for sure
  • m
    I like a few "high power" classes to apply to the body for general layouts (top nav, left nav, hero, etc.) and then from there you use our 
    row
    and 
    card
    concepts
  • m
  • m
  • m
    “The Missing Stylesheet”
  • m
    Kept kicking around in my head from the old missing manuals: https://www.oreilly.com/missingmanuals/
  • p
    Other potential sources of inspiration: https://andybrewer.github.io/mvp/#docs (i like how they document the list of tags and show how to manipulate the CSS vars) https://classless.de/#demo
  • r
    I don't like MVP because there's a lot more magic/hijacking of elements compared to Pico, but the overall concept is solid
  • m
    Very glad to have you on the project!
  • r
    I've been lurking a bit lol, seems interesting to be honest
  • m
    What are some examples of mvp being too aggressive? @User has mentioned using some nesting to make sure we don’t too aggressively style things
  • r
    My personal opinion is that a fork of Bulma with styles applied by default would be perfect
  • r
    It really nails the important utility classes
  • m
    I like pico a lot of ootb styling
  • r
    Section > aside is a card I think
  • r
    Which makes little sense to me from a semantic point of view
  • m
    We can take the beat of bulma but we want to avoid classes via opinionated vanilla html (including aria)
  • m
    Best of
  • m
    How do you feel about @User suggestion of li > article ?
  • g
    we might want to have a concept of "contexts" -- many elements have different meanings in different contexts; i.e. a 
    <section>
    can be a toolbar or U.S.C. Section 3. Example contexts: `prose`: document-like content, blog posts, landing pages, informational sites `widget`: interactive figures usually embedded in noninteractive content
  • m
    Can you change styling based on children?
  • g
    nope
  • g
    not until 
    :has()
    gets good browser support
  • m
    That’s too bad
  • m
    But gives us a long run goal
  • g
    how do we feel about using custom elements for layout?
  • g
    Copy code
    html
<missing-card>
  <img src="">
  <p>stuff</p>
</missing-card>
1...456...44Latest