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
I have searched the issues of this repository and believe that this is not a duplicate.
What problem does this feature solve?
Right now some components like aside navigation etc. have some of the styles by default in html structure, and some of them in css files. It makes the whole styling process way more complicated then it should be, and forces a front-end developer to split their work in two (by using css and props).
What does the proposed API look like?
Everything that relates to styling should be moved to CSS for easier and more consistent work. Elements like aside should not contain any inline styles when rendered and should get all styling from .css file/s.
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
Right now some components like aside navigation etc. have some of the styles by default in html structure, and some of them in css files. It makes the whole styling process way more complicated then it should be, and forces a front-end developer to split their work in two (by using css and props).
What does the proposed API look like?
Everything that relates to styling should be moved to CSS for easier and more consistent work. Elements like aside should not contain any inline styles when rendered and should get all styling from .css file/s.
The text was updated successfully, but these errors were encountered: