Lib agnostic styling #283
Replies: 2 comments
-
At the moment, everything is stylable by using the |
Beta Was this translation helpful? Give feedback.
0 replies
-
Let's track this in #363 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've seen in the issues that the goal at the end of this project is to provide a full out of box editor ready to use on top of Slate. One great feature would be to have way to be able to already implement some styling but in a provider way.
Let's take a example, in my react app I use AntDesign as CSS lib and there is already design for Tooltip and Modal the things is the BallonToolbar provide a new Tooltip design. Since we are using React we could be able to pass the component in the config for using it internally. This is same for Modals like inputting the link properties (displayText, url) could be done by a modal.
But to avoid to reinvent styling for tooltip and modals it could be great to have a provider pattern so we can use either AntDesign, MaterialUI, BootStrap or whatever library with ease. And maybe later we can see some repo like slate-plugins-antd that is on top of this one and provide the needed configuration for having a consistent styling.
Beta Was this translation helpful? Give feedback.
All reactions