Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2020-07-25

Channels

#css
<
2020-07-25
>
Drew Verlee23:07:58

@reefersleep > What do you think about this? Your argument, if correct, is sound. I know thats not saying much, but the advice is familiar and your argument would be a good reason. > This idea is one way I’m trying to reason about CSS; there are just so many ways you can do things, so I’m looking for some sturdy, easily understandable guidelines. On that topic i found this enlightening. https://eev.ee/blog/2020/02/01/old-css-new-css/ it underpins why css is the way it is and how were moving towards more stable models.

reefersleep17:07:55

Thanks @U0DJ4T5U1, I’m reading the article 🙂

reefersleep17:07:17

I know that there’s no silver bullet for CSS, but I’m convinced that there must a be some best practices, or better practices, in the general case as well as in specific cases.

Drew Verlee20:07:31

The question is too broad to be answered directly. Some obvious issues with historic css: 1. lack of a constant way to break up space. Grid goes a long way to fixing this 2. Modularization: css is data, you need to be able compose it and have an optimization step after that. There are a couple libs that basically let you do this.

reefersleep20:07:16

Yeah I know that it’s wayyyy too broad 😉 It’s more of a prompt to get to examples of specific areas in CSS where there might be do’s and don’t’s. Particularly, I’m interested solid ways of sizing and placing elements, but I’m generally interested in some reasonable works-in-80%-of-apps guidelines, whatever aspect of CSS they might apply to.

reefersleep20:07:27

Thanks a lot @U0DJ4T5U1, I’ll check it out!