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
By default, when shadcn/ui is installed, it puts default CSS variables for the colours with HSL values. These default variables however has repeated values that doesn't match with the colour context. i.e.: We set the tertiary CSS Variable but instead must be the accent colour, and the accent colour is used outside of his context and some components already has it in use...
There is however a blocker in here, which is to finish the Masterbots' Design System on Figma, and to declare these colour hierarchy. also for an attempt to remove duplicated tailwindCSS classes which on the long run would be beneficial for the compilation time when the app goes bigger.
After getting the Design System:
Compare the colours values and names and set them as HSLA (no HEX nor RGBA). Prior that, Check the HEX and RGBA values on components to see if they are already assigned.
The text was updated successfully, but these errors were encountered:
By default, when shadcn/ui is installed, it puts default CSS variables for the colours with HSL values. These default variables however has repeated values that doesn't match with the colour context. i.e.: We set the
tertiary
CSS Variable but instead must be theaccent
colour, and theaccent
colour is used outside of his context and some components already has it in use...There is however a blocker in here, which is to finish the Masterbots' Design System on Figma, and to declare these colour hierarchy. also for an attempt to remove duplicated tailwindCSS classes which on the long run would be beneficial for the compilation time when the app goes bigger.
After getting the Design System:
Compare the colours values and names and set them as HSLA (no HEX nor RGBA). Prior that, Check the HEX and RGBA values on components to see if they are already assigned.
The text was updated successfully, but these errors were encountered: