Description of problem:

So there are a few bits of text in the nav area of Anaconda both on the hub, spoke, and standalone windows:

- the name of the screen
- the name of the product
- (optional) the beta/alpha/testing status of the product

This text right now in CSS isn't really style-able in CSS because each individual text item doesn't have an ID you can use to access it, plus some of the properties of the text are hard coded in such a way CSS can't override it:

https://github.com/rhinstaller/anaconda/blob/rhel7-branch/widgets/src/BaseWindow.c#L795

The issue causing us to need to change this text was the theming for the Gluster Storage 3 product that uses RHEL 7.2, which involved the bright red 'testing' text running over a bright orange background color and being pretty mean on the eyes. If I could have toned down the red a bit, it would have helped, but there was no way to do it.

(Here's an example of some of the playing around we had to do to get the text to look better. You can see how eye-cheese-grating the red can be given particular background colors in the theme! http://file.bos.redhat.com/duffy/temp/anaconda-gray.gif )

In experimenting with various potential ways to try to solve the problem in CSS alone given the current constraints, I also thought that adding a (very subtle!) drop shadow to the name of the screen and the name of the product might look nice for future versions of anaconda. Unfortunately, without IDs to address only those bits of text, the drop shadow gets applied to the testing status text line as well, and since that line is bold the dropshadow gets bolded too and looks really bad.

So here's what I would like very much as a future anaconda enhancement to make theming easier for us :)  -

- removing the hard-coded styling in BaseWindow.c and instead implementing those styling decisions in the CSS
- adding IDs to each of those text bits such that individual chunks of text in the nav area can be addressed individually with CSS selectors.
- my suggested ids for the text bits (since they correspond to the GtkWidget variable names in the C I thought these would be most intuitive):
  - name-label (for screen name)
  - distro-label (for product name)
  - beta-label (for testing status)