#How much customization is still ok?

4 messages · Page 1 of 1 (latest)

oak blade
#

Hi, I'm struggling to understand how to use "mantine" in the "right way".

Let's talk about an specific example https://ui.mantine.dev/category/navbars
"Navbar with 2 sections"

Based on the view I'd expect using standard Stack component for the right and the left sides of the sidebar. I'd use standard Text and Title giving them some padding/margin customization maybe . For the icons in the sidebar I'd defiantly use ThemeIcon around them.

But when I open the code, I see a bunch of custom css!
Not even ThemeIcon presented anywhere!
Why did it happen?

I ask myself is it something what regular code written with Mantine would look like? Or, it's happed because there was a goal to implement exactly like in the design so we have to customize greatly? What if I don't have a specific requirements in the design and I'm given much more freedom to define my margins, fonts etc. would it considerably simplify this implementation?

For me, now it looks like, the given design and framework doesn't have a good match here for some reason. It may serve as a great example of the customization abilities of the framework, but if you have to do it too often then something is wrong, isn't it?

So, to reiterate, my question is: in the project where everything is "οκ", Ι mean where the ui framework has been chosen correctly for the design (and vise versa) , should you code look like this mostly? Is it a typical example using Mantine?

jaunty grail
oak blade
#

Thank you for your swift response) So this is how your code supposed to look like in a case you've chosen Mantine UI correctly as your UI library . Ok, got it) Just trying to understand how the correct using of modern UI libraries looks like)

oak blade
#

Some more thoughts) .. so the idea would be to use Mantine components when you can and if you can't it's absolutely fine to use your own thing with css-in-js support provided etc.? To push it to the extreme , even if I use just a handful of "standard elements" of the library and the rest is written with css-in-js and customized from a theme and other features of Mantine then it's still considered a win, right ?