CLI UI needs aesthetic improvements for users with light colored terminal backgrounds

[eliheuer]

Observed behaviour

When using the CLI with a light colored background the information presented is hard to read and looks broken. See screenshot below:

Expected behaviour

Many(most?) type designers use MacOS which defaults to a white terminal background. I have observed that many type designers also don't spend most of their time using the terminal and never adjust the colors. Therefore, I propose that the graphic elements of the fontbakery CLI should be adjusted so they look aesthetically pleasing, or at least considered, to people using terminals with a light background.

I use a custom dark terminal theme for MacOS, and I would also like to see the forced dark background removed from things like the cupcake artwork. See screenshot below:

[eliheuer]

I might try to make a pull request to fix some of these issues at some point before ATypI. I'm looking at this project as an example of how to do this with python3: https://github.com/sdushantha/neofetch

Maybe defaulting to a set of colors that look nice on white and then having a config file for regular terminal users to switch a dark_mode flag to true would be the best solution?

[davelab6]

ANSI has default background color as a mode, f'sure

[felipesanches]

Yeah, this issue was evident among users at the ATypI 2018 Font Bakery workshop...

[kontur]

In iTerm (Build 3.3.9beta1) with fontbakery at 3caba0e the above is the output on a dark terminal now.

[felipesanches]

you can use --dark-theme

[kontur]

Ah, okay, skimmed over the above too quick

Maybe defaulting to a set of colors that look nice on white and then having a config file for regular terminal users to switch a dark_mode flag to true would be the best solution?

I can certainly live with it, but in this instance fontbakery is called as part of a build script, so I wouldn't overwrite it in there. Could be something for the fontbakery user settings discussed in #2734

Edit: I just saw you already mentioned that, too, in the an above commit. Am running a bit too fast ;)