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
The team is now Svelte-ified across everything, including SREPs, so is there any reason why component styles should live separate from the components themselves?
This would gut a lot of the eisbaer theme lib, but also means those styles should be more straightforward for the team to maintain with the Svelte components.
Slight downsides:
Styles for components will be scoped, so overriding them (we do this.... irregularly, I think?) would mean fighting a little more with hierarchy in, say, a global.scss file in the kit.
Components that use SCSS variables (mostly to define font-sizes) won't be override-able. Alternatively, we could use CSS variables for those values, and maybe we should standardise around a root CSS variable style. (Which .... way future ... may open up the door to allowing dynamic injection of style overrides in components.)
The team is now Svelte-ified across everything, including SREPs, so is there any reason why component styles should live separate from the components themselves?
This would gut a lot of the eisbaer theme lib, but also means those styles should be more straightforward for the team to maintain with the Svelte components.
Slight downsides: