I didn't make the icon a "property" because I want you to explore that on your own. What will happen if you make the icon a property also and link it up? Experiment and find out! Also, I'm clearly struggling with the best Screen Studio workflow for editing. Thanks for your patience, haha.
The last missing piece is a way to sync components and css classes between Bricks websites through a server and client relationship. That way you could essentially build a single centralised components and styles library on one Bricks website then stream it to a family of related websites at the click of a button, this would effectively create a centralised style library. I also learnt that Cwicly is back and may be open sourced soon (you should do a review), I feel that Cwicly has the best implementation of components overall. Now Bricks is launching components again, this is definitely a good Christmas. We now just need people to plug the gap and we will have a fully fledged design system based website workflow in WP 🎉🎉🎉 My champ days are coming to an end
A really good video to add to the one we watched from you. I now understand why components are so powerful. I also appreciate the use of accurate terminology especially for novices like me. With ACSS, you aren’t just buying a CSS framework. You’re on a journey to become a professional web designer and developer. Happy Holidays and a happy, healthy and peaceful 2025. Thank you 🙏 Kevin.
I've watched a few other "Early look at Brick's Components" videos.. and this explains it the best, most concise and I see what you did there Kevin, you actually used of the correct term "fields" instead of "properties".
Oh yes, it helps a lot! Thank you. I feel the shift to shorter, dedicated videos like this is going to be to the channel what component will do to Bricks. 😋
Hi Kevin, I am new to this concept of components, this video help me understand better what is all about. big thank you for this video (short and to the point), really appreciated it. 👏
First if all, components are awesome and much needed! Imho using a button as an examle gives a great visual, but might encourage people ( who are used to the typical vb) to not use classes still. I get why you did it, im just saying. Definitely the simplist and easiest. I already have some use cases where we used nested templates because components didnt exist. No matter what, thanks for the video!!
The example in the video does use classes still. That's where the button styling comes from. You just can't tell because the new ACSS feature applies the button classes behind the scenes using Bricks' button UI instead of adding them manually in the classes area.
Nice!! This is a great start. It would be great if they can do something like Figma. I find hard to switch my brain between Figma component and Bricks component logic already 😂
Thanks for the video. It is still in Beta and so many opinions flying around at the moment, will wait a few weeks or months to wrap my head around best use cases, when query loops are the way to go, when global styling is the way to go, looks like design will have to be thought out differently with components......
Don't wait around. Start experimenting with them now. They're 100% necessary and useful, even in their current simplistic state. They don't require any re-thinking of design or architecture, they just require that you know what should be a component and what doesn't need to be. Re: the use of query loops - that's unrelated to components.
I just had a client tell me their board was horrified the button said "Buy Tickets" for their event. The board figures it should say Register. (I asked if this was based on a feeling or data, but that's another story). With a component button i could update that text everywhere to say "register" until i could chat with them about split testing the phrasing
Buttons yes, an excellent use case. Will definitely be testing out various scenarios. Say you connect up the icons and in some instances just leave them blank? Is that bad practice? The placeholder would kick in, unless that’s left blank as well? …things to explore. Even though we are now thinking ahead to Etch, my last year in Bricks has afforded far better workflows where I once was going into crazy magic area with Toolset. Lastly your observations on technical debt, re-architecting and back dooring in features. With Wordpress itself, the CMS and the underlying database are we seeing limitations there as well, hobbling everything built on top of it. Can it be changed at this late stage. A cursory look at it and it doesn’t seem to be normalised to the 3rd normal form in respect of post and pages. It seems to be the same for CPTs. Changing things could be quite radical and break a lot of things. Not an expert in this field so maybe anything is possible?
I have an option page called "Business info" in all my sites where among other information I have fields for Primary and secondary call to action buttons (the fields are button text, button link and aria label). This way most of my buttons in a website use dynamic data that I only need to change in one spot if necessary just like in your case. Maybe something to consider for future builds? Components will take my setup to the next level though 🤗
I didn't make the icon a "property" because I want you to explore that on your own. What will happen if you make the icon a property also and link it up? Experiment and find out! Also, I'm clearly struggling with the best Screen Studio workflow for editing. Thanks for your patience, haha.
The last missing piece is a way to sync components and css classes between Bricks websites through a server and client relationship. That way you could essentially build a single centralised components and styles library on one Bricks website then stream it to a family of related websites at the click of a button, this would effectively create a centralised style library.
I also learnt that Cwicly is back and may be open sourced soon (you should do a review), I feel that Cwicly has the best implementation of components overall. Now Bricks is launching components again, this is definitely a good Christmas. We now just need people to plug the gap and we will have a fully fledged design system based website workflow in WP 🎉🎉🎉
My champ days are coming to an end
I thought that was tella (the new software)
@ nope, new version of screen studio
A really good video to add to the one we watched from you. I now understand why components are so powerful. I also appreciate the use of accurate terminology especially for novices like me. With ACSS, you aren’t just buying a CSS framework. You’re on a journey to become a professional web designer and developer. Happy Holidays and a happy, healthy and peaceful 2025. Thank you 🙏 Kevin.
I've watched a few other "Early look at Brick's Components" videos.. and this explains it the best, most concise and I see what you did there Kevin, you actually used of the correct term "fields" instead of "properties".
Yeah they’re basically just custom fields that are local to the component.
Oh yes, it helps a lot! Thank you. I feel the shift to shorter, dedicated videos like this is going to be to the channel what component will do to Bricks. 😋
Thank you Kevin.... You continue to bring value with nearly every video you drop. I'm ready for my #etchucation
🙏
Well explained! I like short and concise vids
Hi Kevin, I am new to this concept of components, this video help me understand better what is all about. big thank you for this video (short and to the point), really appreciated it. 👏
Glad it was helpful!
Very helpful, many thanks. I think a good working knowledge of Figma will help with understanding the concept too.
Or any design-forward software in which thing’s are iterative and happen…cwicly 😢
Nice and short video, thank you Kevin!
First if all, components are awesome and much needed!
Imho using a button as an examle gives a great visual, but might encourage people ( who are used to the typical vb) to not use classes still. I get why you did it, im just saying. Definitely the simplist and easiest.
I already have some use cases where we used nested templates because components didnt exist.
No matter what, thanks for the video!!
The example in the video does use classes still. That's where the button styling comes from. You just can't tell because the new ACSS feature applies the button classes behind the scenes using Bricks' button UI instead of adding them manually in the classes area.
@Gearyco ohhh that makes sense!
Great video man. And Screen Studio's looking SWEET!
Double the time to make a video so I gotta try to find a way to speed it up!
Thank you for this, very helpful.
this is great!
thank you for this... great example of usage
Thanks Kevin. #Q: does it make sense to use classes for the elements within components?
For sure
@@Gearyco Double power 🙂
Nice ... One of the First... thanks!
Nice!! This is a great start. It would be great if they can do something like Figma. I find hard to switch my brain between Figma component and Bricks component logic already 😂
Thanks for the video. It is still in Beta and so many opinions flying around at the moment, will wait a few weeks or months to wrap my head around best use cases, when query loops are the way to go, when global styling is the way to go, looks like design will have to be thought out differently with components......
Don't wait around. Start experimenting with them now. They're 100% necessary and useful, even in their current simplistic state. They don't require any re-thinking of design or architecture, they just require that you know what should be a component and what doesn't need to be. Re: the use of query loops - that's unrelated to components.
Let's go! I'm gonna use it on my project. IDC if it's beta lol
YOLO!
Figma has Components, a as an example. It’s how F4F works.
Yep I did a tutorial on them long ago
I just had a client tell me their board was horrified the button said "Buy Tickets" for their event. The board figures it should say Register. (I asked if this was based on a feeling or data, but that's another story). With a component button i could update that text everywhere to say "register" until i could chat with them about split testing the phrasing
Yep!
Buttons yes, an excellent use case. Will definitely be testing out various scenarios. Say you connect up the icons and in some instances just leave them blank? Is that bad practice? The placeholder would kick in, unless that’s left blank as well? …things to explore.
Even though we are now thinking ahead to Etch, my last year in Bricks has afforded far better workflows where I once was going into crazy magic area with Toolset.
Lastly your observations on technical debt, re-architecting and back dooring in features. With Wordpress itself, the CMS and the underlying database are we seeing limitations there as well, hobbling everything built on top of it. Can it be changed at this late stage. A cursory look at it and it doesn’t seem to be normalised to the 3rd normal form in respect of post and pages. It seems to be the same for CPTs. Changing things could be quite radical and break a lot of things. Not an expert in this field so maybe anything is possible?
I have an option page called "Business info" in all my sites where among other information I have fields for Primary and secondary call to action buttons (the fields are button text, button link and aria label). This way most of my buttons in a website use dynamic data that I only need to change in one spot if necessary just like in your case. Maybe something to consider for future builds? Components will take my setup to the next level though 🤗
👍