You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are porting over our project to studio sdk and I'm currently working on migrating custom components. One thing I'm trying to get away from is custom html, which requires a custom stylesheet, and attempting to push all the logic into the editor itself.
For example, if I drop a basic 3 column and put image boxes in each one (e.g. for a very simple grid of images in our starter template to our customers) I can put the resulting html into a template and it seems to render pretty well:
Do you have any specific advice for writing components that play well with the Studio SDK basic layout, or layout plugins, so that I can give my users a great starting point but not mess them up with hidden styling?
Is simply playing with the editor and lifting out HTML after I've built something with grapesjs a good idea? Or is that API unstable and I'm actually better off writing custom css for my custom components to ensure future stability?
Thank you for your thoughts, the Studio SDK is phenomenal so far!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team!
We are porting over our project to studio sdk and I'm currently working on migrating custom components. One thing I'm trying to get away from is custom html, which requires a custom stylesheet, and attempting to push all the logic into the editor itself.
For example, if I drop a basic 3 column and put image boxes in each one (e.g. for a very simple grid of images in our starter template to our customers) I can put the resulting html into a template and it seems to render pretty well:
Do you have any specific advice for writing components that play well with the Studio SDK basic layout, or layout plugins, so that I can give my users a great starting point but not mess them up with hidden styling?
Is simply playing with the editor and lifting out HTML after I've built something with grapesjs a good idea? Or is that API unstable and I'm actually better off writing custom css for my custom components to ensure future stability?
Thank you for your thoughts, the Studio SDK is phenomenal so far!
Beta Was this translation helpful? Give feedback.
All reactions