-
Notifications
You must be signed in to change notification settings - Fork 2
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
Design #62
Design #62
Conversation
I dislike it, honestly. It is way too wide, and functionality is affected by it. Smidgh is also I guess not defined shortcut too. |
Well, it's better, but still:
![]()
Let's work on this better and without rush. |
One thing I didn't see mentioned is the color choice. I think the "really dark green" and "slightly less dark, but still really dark green" don't have enough contrast between them. I had to turn up the brightness on my display because I wasn't even sure it was two different colors... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've reviewed the figma files and left some feedback there. Once the final layout established and implemented here, I will check this PR as well.
textTransform="uppercase" | ||
fontSize="xx-small" | ||
variant="ghostGreen" | ||
fontSize={{ base: '18px', md: '22px' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use named sizes instead of pixels, e.g.:
fontSize={{ base: '18px', md: '22px' }} | |
fontSize={{ base: 'lg', md: 'x-large' }} |
variants: { | ||
green, | ||
ghostGreen, | ||
white, | ||
ghostWhite, | ||
whiteModal, | ||
whiteOutline, | ||
danger, | ||
outline, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it is a good solution.
Chakra's theme system supposed that there is variants.
For buttons it is solid
, outline
, link
and ghost
.
And then if you want to have different styles — use colorCheme
. It provides a variety of different colors, but for the branding we need less, so in this case it might be good to name them like primary
, secondary
, danger
, and mb primaryDark
for cases when buttons on dark bg should be different...
But here we have a mix of these, and names are not very clear when which to use. And as I said above, I don't like that all the buttons have the same accents, for example "Add party" and "Add account" looks the same, and which is even more confusing "Cancel" and "Next" the same as well :)
To sum up, I'd like to have:
- clear naming,
- probably separate variants and colors (if it make sense to avoid having a big amount of variants),
- default styles for every component, so we don't need to put
variant="whiteModal"
in every component
borderColor="gray.200" | ||
bg={isOver ? 'blackAlpha.700' : 'blackAlpha.50'} | ||
p={hasWordInside ? 0 : 2} | ||
bg={hasWordInside ? '#0B221C' : 'brand.darkGreen'} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw, now slot does not react when you drag a word over it...
Please bring back the usage of isOver
and ensure that the color is differ from bg...
I still dislike it, but since we really need to officially release it and we need to have it "branded" — I'm merging it. |
styling and layout according to the design at https://www.figma.com/design/bLEBwz5KSP6CNRZ2ooyJto/Light-wallet-files?node-id=0-1&t=ZOgYNwfzZScZwOrO-0