-
Notifications
You must be signed in to change notification settings - Fork 29
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
Suggestion: Add lighter blue color for more dynamic syntax #41
Comments
I like this screenshot. I think bluegreen and light blue, or maybe a darker blue would be nice for sure. |
|
I was thinking a darker color maybe? Although, lot's of things going on at once..(like I wanna edit both the red and orange too) We haven't written it anywhere explicitly yet, but we updated the current cyan/blue color. My apologies, but I was thinking just adding a turqouise and a darker blue maybe, what do you think? 🤔 Side note, I love how github generates the little color bubbles next to the hex -> |
Ah, OK. That's cool, makes sense. As for the coloring, I like the new cyan/turquoise/"dark blue", but I think the key is making sure their expected usage is clearly defined in the spec. Like, the "main vibe" to me of the theme is a dark purple grounded theme, with purple accents and pops of color; that way in things that aren't like exact syntax that you can define a hard spec for, it keeps the overall "vibe" consistent (like the atom-ui colors, etc). Kinda curious what you're thinking for the red/orange now too though hehe |
Yeah I think that’s it. I tend to associate red with errors so it should be used least sparingly I think. But orange is more permissible just not as much as green/purple. |
Example: VSCode default color scheme
The text was updated successfully, but these errors were encountered: