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
Deconf ui has always been based on Bulma, maybe it is time to move beyond it?
Bulma does provide lots of great components which deconf components are wrappers or straight copies of but there are a couple of issues we've arrived at in using it.
rtl support is the most noticeable, Bulma's components are written in a left-to-right way which doesn't place nicely with new css properties like padding-inline-start, it instead uses padding-left which doest automatically work in rtl.
weight is another concern, all of the compiled scss is shipped in one big .css file, if we made our own thing it might be able to be broken up into multiple exports which tree-shaking could only use the required bits in the required cases.
bulma x maintainable css is another issue, components use maintainable css to name things which clashes with bulma's simplified naming system and could lead to naming collisions.
It would definitely be a lot of work to do this, but it has been on my mind to think about it
The text was updated successfully, but these errors were encountered:
Deconf ui has always been based on Bulma, maybe it is time to move beyond it?
Bulma does provide lots of great components which deconf components are wrappers or straight copies of but there are a couple of issues we've arrived at in using it.
padding-inline-start
, it instead usespadding-left
which doest automatically work in rtl.It would definitely be a lot of work to do this, but it has been on my mind to think about it
The text was updated successfully, but these errors were encountered: