compodio VS onyxia-ui

Components that need to incorporating global styles like colour schemes, breakpoints, border radius, scss mixins is where I've found it tricky to fully decouple. In these instances I've resorted to using global custom properties that I can reference inside css modules and importing commonly used scss mixins. This is an example of a search box component incorporating global things.

Currently working on compodio in my free time. A website that makes it easier to find, and subscribe to community radio shows as a podcast. It uses NextJS, Python, PHP, MySQL

I used it here in a function that constructs a string of hex colours for a css gradient from an array. I spend more time in python than JS, and looking at this code again now I see it certainly isn't perfect.

I feel like now that I'm developing mostly with react, which has everyone rethinking how to think about separation of concerns, I'm still figuring things out again. In a current project, I have global styles sheets for the site as a whole, then I try to bundle css modules for components of a site in a folder with other files related to the component (ex. a main menu component). The aspiration being that some components will be generic enough that I could just copy one folder and have everything I need (css, js, etc) to add that feature to another project.

Impressive. I've been working on something similar, but much simpler. I settled for just organizing colours by lightness. I just might borrow your ant colony optimization.

This is an in progress component I'm working on that always expects to receive an array of available image sizes, that jpg/webp are always available.

Then You can pretty much do the same thing I did with the next page link here.

My advice if you don't have a multi-million budget and you only need to support React is to start from MUI components. Components like Date pickers, or Autocomplete are complex and time consuming to code from scratch. First thing you want to do is to build a custom theme for MUI (example DSFR, Example OnyxiaUI) this will make the MUI components roughly match your design system out of the box. Then you can create your own components that are wrapper around MUI components and customize them until they match your design (Example). Trust me, we always underestimate the complexity of building base component from scratch. There are tons of things to consider, I don't even mention the accessibility concerns... Customizing MUI components is the quick win route.

Shameless plug of our design toolkit: onyxia-ui. But it's good!

We are working on a UI toolkit that let you define what is the expected screen size. If you put 1920 for example and the screen is bigger than that it will stretch everything up. If the screen is smaller it shrinks everything down. It's not a perfect solution but it garanties that your app will look exactly the same no matter the screen size of your users. You can check it out here

Actually we are working on an alternative typescript first ui toolkit. tss-react is part of it. You can check it out it's onyxia-ui it rocks. It's still under active development but it's usable already. Also what's cool about it is that our salary are paid by the French tax payer so it's MIT, no strings attached.