Комментарии:
Enjoooy?? Subby subby!
Ответить"specifity. I can never say it right. SPECIFITY! there we go!" DEAD xD great video though!!
ОтветитьVery very good! was trying to understand this before but only now I understand :)
ОтветитьThank you for explaining BEM so clearly and succinctly. You got a new sub and I'm looking forward to watching some of the other videos you have.
ОтветитьGreat ✌
Ответитьwrong naming. very wrong.
Ответитьthanks
ОтветитьWhat's the point of doubling up on the underscores and the hyphens?
Wouldn't card_button-active tell you the same information (what it's for) as card__button--active?
I've used BEM for many years.
Modifiers are great and truly provides a nice way of stating a clear intention that this element has a shared base style and a variant that overrides or adds a few things.
But the block__element concept is less useful. It's fine in tiny flat components that you don't change a lot.
But in larger things the double underscore often has to be moved deeper down and feels useless.
You begin with footer__menu but as that menu gets more and more children you rename it to footer-menu so can have children like footer-menu__user and footer-menu__faq
If this renaming happens multiple times, or the dom tree for the footer is quite deep then you end up just forgetting which nodes have the block__element thing and which just use dashes.
At which point I usually go "screw it, let's use single dashes all the way" and I never end up regretting it.
I still use BEM on small isolated components though.
great job with the slides... best slides I have ever seen
ОтветитьGEnial! Thanks!
ОтветитьThanks
Ответить👏👏
Ответитьgreat video
ОтветитьI spy with my little eye a Kemper Toaster!
Ответитьthe best BEM tutorial
Ответить"spess-uh-FISS-it-tee"
Ответитьthanks!
Ответитьi dont really understand, how the selector in css works, when you reference the name just with the the __name, just because its named differently in the html...
ОтветитьThank you so much for this tutorial...
ОтветитьGreat easy to understand video. Thank you!
ОтветитьSpecificity! :P
ОтветитьIt's useless, using SASS is better.
ОтветитьThat was clear... but a little bit confusing if we want to use isolated component or block to another block. We can not override style from unrelated block.
for example, we want to use .btn block inside .card block. Let say that the button inside .card block have different style. So how we deal with it?
There are only one elem of everything...
ОтветитьFantastic video
ОтветитьIsn't it SpeciFIcity
Ответитьnice method on writing css, scss + bem probably the best way to go for large project
Ответитьthanks a lot!
Ответитьperfect
Ответитьgonna follow that convention
ОтветитьI have used BEM in one previous company project, not a big fan of it. I like modular css/scss much better.
ОтветитьThank you for a good explanation! This video helped a lot!
ОтветитьImportant question. What is that green guitar in the background? Are these EMG pickups?
ОтветитьVery helpful, great tutorial. Thank you!!!
ОтветитьI don't care if I'm doing large project or small, I always use BEM. (that's different thing I don't get large projects)
ОтветитьIt is Spe-ci-fi-ci-ty ;-) And why arent you using semantic elements in HTML? Like a section or an article for the card? It is supposed to be an element that can stand alone and therefore it should be an article or a section for each card? I know that there is not a title/heading in this example, but anyways? And why is the picture/img not a part of the content element?
ОтветитьThank you so much. I feel like I have been given the secret handshake to the club :)
ОтветитьGreat tutorial ! Good speed, clean and straightforward to the point. Thanks.
ОтветитьComing from a big project, one important lesson learnt: don't abuse Sass/SCSS, keep it to bare minimum. Reason? Trying to resolve a high priority production defect with a huge SPA codebase, it doesn't help to have .block { ...; &__element{... &--modifier{...}} rulsets: it very hard to find the original rule definition in source code, since in the browser you'll see generated version. The lesson learned, in order to be able to quickly find a rule, write entire selector by hand, don't leave it up to SCSS preprocessor. One thing is to write confusing Sass code to impress junior female developers on your team, and another thing to debug prod issue under pressure and a lot of stress. KISS.
ОтветитьBy mistake you have added class on closing tag as well
ОтветитьWhat happened to the red guitar in the background?
ОтветитьI started using this method after a tutorial without even knowing what it is lol
ОтветитьThank you Gary!
ОтветитьI still dont get the point of BEM
Ответить