Also thought of another thing which I am not sure has been mentioned yet.
Make Global Components Work with Query Loops.
A Query Loop assigned to an element is like a Component in a way since it repeats itself but you can’t use the same Query Loop element in a different section,page,etc. with a single source of truth. You can copy and paste it to a new location, but this gives you 2 distinct versions that would not mirror each other if you updated the html elements in one.
Global components are in development, webflow new version of components out, check video
Get idea how much powerful it is, later bricks can improve components on time.
Yeah, this looks dope. What doesn’t look dope is some recent comments in reddit regarding WebFlow’s price hikes for hosting and continued lack of functionality. WP continues to accel.
Just a few addition to the features list. Hopefully Bricks offers a way to convert an instance of a component into another component or just revert it back to regular Bricks elements (ie making it not a component)
In case someone missed it, here is a video showing how the Bricks components feature is coming along…
Hi @thomas,
Some of us are wondering how the work on this important new feature is going. If I suppose the brainstorming phase is already over, is there any area where we can jump in to the conversation to provide some ideas and feedback ? I am for instance very curious on how you plan to allow users to decide what is to be synchronized throughout the site’s similar components, and what to remain locally set (such as the dynamic data input source)…
Hi @AnLip, first of all, implementing these kinds of things is not easy in a short period. However, on January 15th, there will be a price increase, and with it, there will likely be new announcements. I expect a stable 1.9.5 release and possibly a beta release. Community feedback time will come soon. Until then, stay patient.
I’m aware of this, thank you. Just asking if there is a space for open discussion, no pressure made.
Why would you delay this? The current date is the 21st now.
Unfortunately, this was not the case. Any updates on when we can expect a beta? @MartinWB
Wanted to quickly chip in with an update on what’s happening in Gutenberg land. They’ve recently made a change to terminology: what was previously known as “partially synced patterns” is now being referred to as “synced pattern overrides.” Just a heads-up for everyone staying in the loop with the latest developments!
They are aiming to roll it out in WordPress 6.5
There is a tiny preview of the UI in the session at 59:09
Also, an elementary functionality demo in the session at 6:14
Any chance the beta is gonna be available soon? We are trying to migrate a large site away from a page builder that shall not be named and this feature alone is stalling us starting.
Unfortunately can’t unhear that its coming, and knowing our build will greatly benefit seemed silly to rush and build the site without it.
Is there a beta channel available? I’m also a plugin author with a decade+ of testing/debugging WP and would be happy to bug test it.
Feeling this as well… I’m working with half-solutions and hoping that a large project does not come down the pipeline until components are available… 
While we were waiting: For client-side work, I’ve started checking out GutenBricks (Forum thread) , which allows for a component-like approach when building pages in Gutenberg. This tool is promising as it enhances the editing experience by turning Bricks templates into Gutenberg blocks, offering a more intuitive interface for clients. Ryan aka @aaskryanlee is pretty active and pushing out some promising features over on his page!
That will work great for our sidebar setups also, Gutenberg just doesn’t have the flexibility to fully match things when using the Bricks Sidebar and editing the sidebar widgets with gutenberg.
The “Explore a game-changing feature for synced patterns in WordPress 6.5” video introduces a significant update in WordPress 6.5 that allows for content overrides within sync patterns while maintaining the original layout. This functionality enables users to edit specific content, for example, text and images, within a pattern without altering the overall design. Certain elements, like a standardized image of Matt intended for release team pages, are initially set to be non-editable to ensure consistency across the platform. However, users have the flexibility to make these elements overridable or keep them consistent, based on their needs.
Additionally, the feature is currently limited to certain blocks like heading, paragraph, button, and images, with options for further customization, including text edits and image replacements. Users can save their customizations or reset them to align with the original pattern if needed. This update, aimed at enhancing content management and design efficiency, is open for discussion on GitHub for community feedback on expanding its capabilities to additional blocks.
WordPress 6.5 is set to release on March 26, 2024, and this new feature promises to enhance user experience by allowing for more versatile content creation and management within consistent design frameworks.
Thanks for sharing these, @MaxZieb 
I have come over from the now defunct Cwicly. Sad state of affairs there unfortunately. I had become very accustomed to building components and was surprised Bricks is yet to add them. I do hope this is implemented soon as they are incredibly functional and versatile. It was one of the main reasons I stuck with Cwicly.
I’m also hoping for the release of components soon. From the dev timeline that started last fall, I am speculating that the Bricks team encountered a bit more difficulty than expected in bringing this feature to life and integrating with all the existing functionality.
I mainly just want to post this to encourage the Bricks team to keep developing, working out the kinks and ensuring the feature is solid. It’s likely a lot of work to really build this in a scaleable way, so I am OK with the time it takes, and I’ll be very happy to test it out when a beta is released!
Wow… everyone is still discussing implementing Global Components for Bricks.
I hope components makes it possible to give editors access to edit properties while restricting access to detailed styling.
Any updates on Global Components being released anytime soon?