You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Designers don't learn anything about value, and so, when they talk about the "monochrome" parts of the visual experience they fumble around. Take any blog post about "do design in black and white" and search for "value": https://curioelectro.com/black-and-white-logo-design/ … Nothing.
Search all over the design blog world and not a single mention of value. Even though it's a central concept in all visual arts, and without it you can't render anything, I haven't ran into one book or author who uses the word or even knows the concept. Why's that important?
If design had value CSS would be value first, color second. You'd indicate the monochrome levels of every element, then simply give a color scheme assignment to each element and your design would be about 90% right. Artists always say "get the values and color can be anything."
When you are told "pick 3 colors to make your color scheme!" You're being lied to. You need to pick 3 colors, AND give each element a value from light to dark with that color to do a *real* color scheme. That solves your context. In fact, color doesn't matter.
In the color scheme style of painting they basically prove this. You first have to do a fairly accurate monochrome underpainting so that you know where the values are, then you can literally put any colors on as long as they match the values.
If you paint with pigments that let you accurately match the color of what you see then your values are handled for you automatically. But, if you want to use a color scheme you have to rely on a good monochrome rendering to keep things straight. That was my big mistake.
I was used to just mixing the color for what I see, then painting it. So I was trying to do extra duty by mixing the color scheme, trying to work out the values, and trying to balance where it went, and it was too damn hard. A monochrome painting solved it easily.
Which would also work for design, especially CSS, if designers knew about and focused on values first the way artists do. Color isn't important, and should be easily malleable. An idea CSS would let you assign values, then kind of randomly choose colors until you like it.
The ideal workflow would then be: 1. Do the whole design in monochrome so that it is easily comprehended. 2. *Without changing any value assignments*, add the color scheme or try several to find a good one. 3. Then refine the colors and values to solve interactions between them.
Or: 1. Do the fully rendered drawing. 2. Figure out the color scheme. 3. Paint it in the design while maintaining the values. Then it'd be way simpler than the current design method of "pick a color scheme then randomly place things on a grid and alter it until you like it."
Finally, another way to put it is that CSS (and designer) color understanding is too complex because it's not broken down into the logical components that matter to human comprehension: value, hue, intensity so that you can manipulate them independently of each other.
Without an ability to manipulate value, hue, intensity efficiently on their own CSS designs are as difficult as my earlier painting failures when I was trying to juggle all three in my head at once before I used values, then color.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
