I will be picking up Bricks Builder soon. Next week is my plan. From everything I have seen, I find it hard to even consider anything else. I would go full Kadenace and have the lifetime license on that one. I will go for the Full LIfetime unlimited sites license for Bricks Bui9lder From what I can see it addresses almost all my complaints with builders like Elementor. This is not to say this is only Elementor as there are other builders I have used that are just frustrating to build in. Thanks again for the great content you produce and especially on Bricks Builder.
Imran... always the best to explain things, really clear. I need to do a website with Bricks, so I need to learn it and I am greatfull to have your tutorials to help me in this new journey. 🙏
There are some other 3rd Parties that provide Subscription Lists but I will be looking to develop some (at some pint) and make them available for Free.
The only thing you're missing in all your tutorials, which are great, is that you can select a color palette by default, instead of clicking on the dropdown menu everytime you choose a color ;)
I know what you mean :) I need to make that clear as I’ve been lazy on that bit :) :) Did you notice a New 2 palette as well that’s been defunct for ages :)
I'm kinda confused with Bricks when it comes to their structure Section -> Container -> Blocks -> Widgets, compared to the direction Elementor went for. One of the reason Elementor switched from Section and Column do Flexbox, and introduced Containers was to reduce the number of DOM elements (I think you or Paul made a video on this, comparing the number of DOM elements with Sections and Columns vs Containers). Indeed, it did reduce the number of elements, made sites faster, thus achieving better scores in Google Page Speed and GTMetrix. In contrast, Bricks approach adds DOM elements. Isn't an issue with more complex pages with loops/listings where you have like 20-30 items per page?
Bricks is more semantically correct to do this. A section should be 100% wide, no margin, filling the full space and if it makes sense, have some padding. The padding is important mostly for mobile because you don't want content touching the edge of the browser. The contain part is meant to have a max-width and be the main "column" of the website, although you can make it 100% wide if needed in some situations. The blocks then become the horizontal columns or flexbox content containers for the inner content. To create consistency for your overall design, you want all your sections to follow the same padding rules, and your containers to follow the same padding/margin rules, so that all your columns line up and all your mobile content sits where it needs to. Let's take another example. Let's say you add a section and then just start putting stuff in it like an H1 and then a subtext and more text and buttons. So to do this you have to set the section to be flexbox perhaps, column mode. The problem is, you can't have a consistent section now, because this will will have to be set to flexbox columns and with justification space-between or whatever. Then you have to set max-widths on your heading and text to make sure they don't get too wide. You have to set padding on the section so that the content doesn't touch the edge. But now if you add another section but use the columns mode to have three columns, well the paddings and margins are off, things don't line up, the section styles can't be the same, you have to set different general styles on the content widgets based on what kind of container they're in, etc etc. The takeaway is, use sections because they are 100% wide and each section touches each following section with no margins, so that you have no "unfillable space" between sections, you don't want gaps around them. Use containers to house your inner content because they set max-width and margins to help line things up and look good on mobile. Use the blocks to house flexbox layouts for the inner content. Use divs when you need to do even more grouping, or set up things like ul>li lists or other tags. It's not just about reducing DOM elements, it's about having consistent semantic structures that share style defaults.
Bit messy explanation. Why not start with one section, one container with max width and two columns in it. And point your visitors to the flexbox page, cause that’s what they really need to learn if you want to understand😂bricks.
![[Live] : ONE FIGHT NIGHT 28 วันนี้!! "พระจันทร์ฉาย vs เอลลิส"](http://i.ytimg.com/vi/LfImEQqfARc/mqdefault.jpg)
Wow, this is a great explanation! I learned so much. Thank you!
좋은 영상 잘 봤습니다. 올 바른 사람으로 느껴집니다. 브릭스와 워드프레스에 관련된 깊이 있는 영상 잘 부탁드립니다. 감사합니다.
best explanation for the section/container/block story
I will be picking up Bricks Builder soon. Next week is my plan. From everything I have seen, I find it hard to even consider anything else. I would go full Kadenace and have the lifetime license on that one. I will go for the Full LIfetime unlimited sites license for Bricks Bui9lder From what I can see it addresses almost all my complaints with builders like Elementor. This is not to say this is only Elementor as there are other builders I have used that are just frustrating to build in. Thanks again for the great content you produce and especially on Bricks Builder.
Great tutorial! Such a pleasure to listen how you explain everything!
Thanks again for sharing Imran! 🙌
- more Bricks content please
Trust me - lots coming up. Keep an eye on that Bricks Playlist. We also released Part 4 today.
@@websquadron I already saved the playlist. 😊
This was really helpful. I joined the web squadron as a thank you. Looking forward to more on bricks. Thank you again.
Welcome aboard!
Checkout the Bricks Playlist: th-cam.com/video/nQ8LriNnSnM/w-d-xo.html
@@websquadron perfect! Thanks
I slowed down the audio play back speed and it really helped my retention
I’ll keep that in mind and try to be slower.
Excellent vid mate... loving the 101 series. Time to bust out my Bricks license and take it for a spin. Keep the vids coming
I'll move onto more advanced stuff (soon) :)
good stuff. Super helpful thank you
Imran... always the best to explain things, really clear. I need to do a website with Bricks, so I need to learn it and I am greatfull to have your tutorials to help me in this new journey. 🙏
thank you for the clear explanation. Are there many templates, pages and ful kits for Bricks. I did take a look and found only a handful?
There are some other 3rd Parties that provide Subscription Lists but I will be looking to develop some (at some pint) and make them available for Free.
@@websquadron wow, can't wait! 👍
The only thing you're missing in all your tutorials, which are great, is that you can select a color palette by default, instead of clicking on the dropdown menu everytime you choose a color ;)
I know what you mean :)
I need to make that clear as I’ve been lazy on that bit :) :)
Did you notice a New 2 palette as well that’s been defunct for ages :)
I'm kinda confused with Bricks when it comes to their structure Section -> Container -> Blocks -> Widgets, compared to the direction Elementor went for. One of the reason Elementor switched from Section and Column do Flexbox, and introduced Containers was to reduce the number of DOM elements (I think you or Paul made a video on this, comparing the number of DOM elements with Sections and Columns vs Containers). Indeed, it did reduce the number of elements, made sites faster, thus achieving better scores in Google Page Speed and GTMetrix.
In contrast, Bricks approach adds DOM elements. Isn't an issue with more complex pages with loops/listings where you have like 20-30 items per page?
So far not had an issue and I have seen a reduction in DOMS.
Bricks is more semantically correct to do this. A section should be 100% wide, no margin, filling the full space and if it makes sense, have some padding. The padding is important mostly for mobile because you don't want content touching the edge of the browser. The contain part is meant to have a max-width and be the main "column" of the website, although you can make it 100% wide if needed in some situations.
The blocks then become the horizontal columns or flexbox content containers for the inner content.
To create consistency for your overall design, you want all your sections to follow the same padding rules, and your containers to follow the same padding/margin rules, so that all your columns line up and all your mobile content sits where it needs to.
Let's take another example. Let's say you add a section and then just start putting stuff in it like an H1 and then a subtext and more text and buttons. So to do this you have to set the section to be flexbox perhaps, column mode. The problem is, you can't have a consistent section now, because this will will have to be set to flexbox columns and with justification space-between or whatever. Then you have to set max-widths on your heading and text to make sure they don't get too wide. You have to set padding on the section so that the content doesn't touch the edge. But now if you add another section but use the columns mode to have three columns, well the paddings and margins are off, things don't line up, the section styles can't be the same, you have to set different general styles on the content widgets based on what kind of container they're in, etc etc.
The takeaway is, use sections because they are 100% wide and each section touches each following section with no margins, so that you have no "unfillable space" between sections, you don't want gaps around them. Use containers to house your inner content because they set max-width and margins to help line things up and look good on mobile. Use the blocks to house flexbox layouts for the inner content. Use divs when you need to do even more grouping, or set up things like ul>li lists or other tags.
It's not just about reducing DOM elements, it's about having consistent semantic structures that share style defaults.
@@vigilantezack Great explanation.
Bit messy explanation. Why not start with one section, one container with max width and two columns in it. And point your visitors to the flexbox page, cause that’s what they really need to learn if you want to understand😂bricks.
Thanks for the feedback.
@@websquadron Sorry for my harsh comment, you're doing great putting out that much of content.
@@johanstam3602 Not harsh at all, and I'll be fleshing out more as the series goes on :)