Missing styles that we need

[robredpath]

Following on from #42 , I think we should compile a list of styling questions that we can work through ourselves, or get help with

@stevieflow @chrisarridge @tillywoodfield - please add to this list!

• Active/hover/visited states for links in paragraphs (styling of links (within a paragraph), including hover-over / active state #42)
• Styling of links not in paragraphs - e.g. in headers, tables and drop down menus (Styling of links not in paragraphs #53)
• Background colour and/or gutters (The all-white background feels very harsh #37)
• Buttons in more contexts than the current styling supports (issue to be created)
• Styling <code> blocks, including a special instance for a reference to an element in the IATI Standard (Add a standard way of presenting references to elements of the standard #29)
• Improve font legibility (changing font weight from "light" to "normal")
• Small buttons suitable for a filter interface (e.g.

)

[stevieflow]

@robredpath is this for the list: #37 ? Thanks

[emmajclegg]

@robredpath - looking at YI's feedback on applying the design system to IATI Publisher, my main observation is that fonts across the tool are now less legible than before. I think @chrisarridge has already suggested a solution for this and I've added it to the list in the description above.

AFTER:

BEFORE:

All standalone links in headers, tables and dropdown menus being underlined also looks slightly odd :

[codemacabre]

@robredpath @stevieflow @chrisarridge @tillywoodfield, please could you add more details or new issues for the remaining items in the list above (the buttons requirements)? Once I have more info, I'll begin implementing them.