As a developer that wants to extend Bricks, I’m expecting API to: read & write the data on state management used by bricks’ editor.
Also, the hook/events to attach our listener when some event happened on Bricks’ editor. This package should be a good hint for it @wordpress/hooks - npm (npmjs.com)
I happy with how is the PHP side of Bricks is flexible and easier to extend, but it’s a different story with the front end of the Bricks’ editor. There is minimal info on hook/API on how to extend the Bricks’ editor to follow our workflow standard.
Someone has requested the native version of plain classes for Bricks Builder by emailing the support team, which CC-ed me. And the response is, the team has added it to their development backlog.
I would like to see this thread request taken into the development backlog as well for more wide and more general usage for the 3rd-party developer can be used to extend the Bricks editor with more flexibility.
That’s great news !
Hope to see the ability to write multiple classes at once and make it easy to change.
Yes, plain classes is needed. And maybe it will be cool to also define a list of “reserved classes”. So all tailwind utility classes (or ACSS) cannot be modified inside bricks.