@@beatc 2 main reasons: 1) Their containers were designed without flexbox in mind. They insert a clearfix before and after pseudo elements that will break your layout if you apply flexbox or grid. Clearfix was used when we were all still using floats to align elements in a row. 2) 940px default max-width is pretty useless. Too small for regular content and too wide for articles/posts. So you'll end up fixing it or writing custom css. Might as well just use a div since you'll be editing the default container so heavily, anyway. Plus, with modern css you can use advanced functions like, "width: min(1280px, 100% - 3rem);" to create a container with padding built in, removing the need for an extra padding wrapper. Just my 2 cents.
I'm new to webflow but not to css and front end dev. And when I started working with webflow and followed their university courses. They heavily recommended containers so I followed. But I was soon confused as to why use them especially when it came to the defined width. I think div blocks inside of sections in a better and more intuitive approach, especially if one is used to html and css.
@@RA-zv8xm Exactly! Webflow's strength definitely isn't in their default recommended elements (don't even get me started on the slider - it's an abomination). The magic happens when you finally realize Webflow is just a fancy UI for CSS with a lightweight database tacked on, not a real design tool. That's when you can really start using it to its potential. It can be amazing for building and maintaining marketing sites, but you've gotta learn to dance around its quirks - and honestly, there seem to be more of those popping up every year. A large chunk of their default elements are outdated or useless.
Don't use Webflow's containers. They'll give you heartburn later.
why?
@@beatc 2 main reasons:
1) Their containers were designed without flexbox in mind. They insert a clearfix before and after pseudo elements that will break your layout if you apply flexbox or grid. Clearfix was used when we were all still using floats to align elements in a row.
2) 940px default max-width is pretty useless. Too small for regular content and too wide for articles/posts. So you'll end up fixing it or writing custom css.
Might as well just use a div since you'll be editing the default container so heavily, anyway. Plus, with modern css you can use advanced functions like, "width: min(1280px, 100% - 3rem);" to create a container with padding built in, removing the need for an extra padding wrapper.
Just my 2 cents.
I'm new to webflow but not to css and front end dev. And when I started working with webflow and followed their university courses. They heavily recommended containers so I followed. But I was soon confused as to why use them especially when it came to the defined width. I think div blocks inside of sections in a better and more intuitive approach, especially if one is used to html and css.
@@RA-zv8xm Exactly! Webflow's strength definitely isn't in their default recommended elements (don't even get me started on the slider - it's an abomination). The magic happens when you finally realize Webflow is just a fancy UI for CSS with a lightweight database tacked on, not a real design tool. That's when you can really start using it to its potential.
It can be amazing for building and maintaining marketing sites, but you've gotta learn to dance around its quirks - and honestly, there seem to be more of those popping up every year. A large chunk of their default elements are outdated or useless.
@@DerekAtMeridian What do you recommend for a legit design tool? I've been thinking about Framer lately.
Love the delivery as always 🫶 Just curious if there a reason the HTML Tags in the div settings weren’t mentioned? 1:34