Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate moving away from Bulma #51

Open
robb-j opened this issue Nov 9, 2021 · 0 comments
Open

Investigate moving away from Bulma #51

robb-j opened this issue Nov 9, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@robb-j
Copy link
Member

robb-j commented Nov 9, 2021

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

@robb-j robb-j added the enhancement New feature or request label Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant