bricks is not elementor or any other shit builder… 
not even close…
bricks builder already very loyal to the html and css terminology and structure rules
just because there is no ux/ui designed around that doesnt mean it doesnt have it.
I truly believe a new beginner can learn alot webdev and html+css while using bricks as well
same for other side of the coin if you know html+css you can use that in your full advantage too
welcome
My thinking on this has evolved – bi-directional sync with UI panels isn’t critical. What matters more is direct HTML code access. This would remove tons of limitations instantly.
Quick example: props passing between nested components. Currently impossible, but with code access you could do React-style <Component text="some text"><Nested text={props.text} /></Component> without needing special UI for it.
This unlocks massive possibilities. Agree with others that improving components, core builder optimization, and direct code access should be priorities.
Yes. That was the main reason I moved to Bricks, and I think it was the same for many other developers back when Bricks was being developed. Today some competitors, still immature, are offering interesting tools for developers. What I would like to see in Bricks:
Two way or bidirectional CSS and HTML editors. Not essential, but I have been testing this in Builderius and not only it is very practical to edit, modify, import, but also helps to track CSS on different breakpoints.
A better way to track different custom code, including CSS, JS and PHP. Right now global code is accessed in one place, page level code in another, and the builder also allows inline code, which makes everything scattered and harder to track. A single place to access all of this easily would help a lot. When it comes to tracking and custom code, a manager for CF getters and custom dynamic tags would be useful too.
A way to add code comments for developers, which would help with some of the issues above.
I am not advocating for any other tool and I am far from wanting to migrate to a different builder. I am just disappointed that I could not even find these suggestions on the Idea Board. But I’m having hope if we keep demanding it.
I don’t like the “random” idea board anyway. It is in no ones control, what ends up there and when something is published.
Simple publicly understood feature requests like element xyz will always be more popular than a feature that needs some understanding of the topic.
Threads like this have much more value and allow a good discussion too.
I wish forum had up voting on the feature requests category
thats not really true – many of the settings in bricks are NOT the same naming property as css
+1 – weird they have been quiet about it… maybe they a quietly cooking and it will be a surprise update!
I don’t either because I think that poplular votes on some features should be a low priority over others. For me, fixing back issues and fine tuning some of the newer features should be a priority over implementing better animations, motion effects, multi-step forms, and some of the other high vote items, because that can be done well with other plugins.
This happen every update anyway, they just don’t tend to get added to the roadmap. The roadmap only ever shows new features, from what I’ve seen. But it doesn’t mean the bug fixes and fine tuning isn’t happening with every release.
Sorry, but there are some back issues that have been not fixed for many releases.
Sure, I mean generally (obviously there’ll always be some bugs still not addressed). But my point was these things never appear in the roadmap either way.
While we are not supporting yet bi-directional, we have add support for HTML to Bricks element pasting:
nice 
Bi-Directional CSS / dynamic CSS is by far the BIGGEST feature I want to see from Bricks. More than any other new element or support for xyz library.
Being able to handwrite CSS and/or input it from the editor, and have it automatically sync in both places would be fantastic and make it so powerful! I understand this would require some serious reworking of how Bricks currently outputs stylesheets…
Glad to see this is gaining traction Would love to hear from the Development Team’s thoughts.
And anyone else lurking, if you think it’s a good idea please drop a comment! Lets get some more traction and eyes on this.
Yes, please! It would be very helpful if you could paste natively HTML into the bricks builder structure.
yes – all of the above! It will be so beneficial for doing more custom things with AI and devs who create templates/ layouts.
knowing them - they won’t respond and it wont get added to the roadmap. it will just come as a surprise feature release 
This will definitely set up Bricks Builder to be the best for professionals and beginners. I also think that this will quiet down some very loud voices in the sphere.
Oh yes, that would be an absolute game-changer and would boost our workflow considerably. If the Bricks team manages to achieve this synchronisation, then Bricks will truly be a builder for years to come!