Symbols plugin vs Symbols API

[lexoyo]

Hi everyone,

I'm the author of the grapesjs-symbols plugin that adds reusable components ("symbols") to GrapesJS.

Since the release of the new Symbols API in GrapesJS core (currently in beta), I plan to adapt the plugin and make it a UI layer on top of this native API. I believe it follows @artf vision for the upcomming architecture.

If you’re using symbols, or thinking about it, I’d love to hear your thoughts:

• Anything you’d want in the new UI?
• Friction you encountered using the API?
• Gotchas when using symbols across pages?

You can try the plugin live in Silex (you'll need a free gitlab.com account)

I’ll get started after I release another plugin, grapesjs-advanced-selector, which is almost out of beta. Feedback on that one is also welcome!

Thank you <3

[artf]

Thanks for the update @lexoyo
We are already leveraging the Symbols in production with Studio SDK, and so far, we haven't faced any issues, but let me know if you find any blockers there.

[lexoyo]

It's updated ! It works great now with the new API

I had little doubts about symbols on your part @artf, your code is always solid in my experience :)

I was hoping to hear about people using my plugin. I'm not sure it is useful to be honest. But anyway now it works great with the new API, thank you !!