## Description

When importing the TitleBar component in a NextJS app utilizing Server Side Rendering, it will produce an error that "useEffect" can only be run on the client side.

## Additional context

Looks like this component was overlooked from the 1.4.2 release that added the 'use client' directive to components using useEffect.


Minerva 1.5.0

TitleBar doesn't work with SSR

## Background

The case for link accent is more for dark mode and high contrast areas as a way to allow crimson 300 to be used for things like borders and UI elements that may otherwise be turned white simply because text links need to be white for contrast purposes.

The case for background--info-alt, background--negative-alt, and background--positive-alt is to provide what would essentially be background--element within those contexts. It's possible to dispute the naming of these variables to follow the "surface, element, chip" schema, especially since this solution still wouldn't provide an acceptable color for chip within that context. That being said, I think these contexts are used so infrequently and with much control, and it is incredibly unlikely to need a chip color for each context.

## Mockups / Proposed solution

Add the following tokens to the design system:

- ua_color-text--link-accent
- ua_color-background--info-alt
- ua_color-background--negative-alt
- ua_color-background--positive-alt


enhancement

Proposal: new color variables text--link-accent and background--context-alt

## Background

The College of Arts and Sciences reached out to me and Kyle about a dark theme for some of their websites that usually have a darker aesthetic, and wanted to see how that could fit with the minerva design language.

## Description

Implement support for a dark or inverse theme

## Workarounds

`ua_contrast--most` can be added to a wrapper around most page content and things work reasonably well. However, more contrast sections and some components respond poorly to this


Add support for dark mode

Reported by Heather Baker on the web forum (heather.a.baker@ua.edu)

## Description

Are there any plans to update (or include alternate colors via classes) duotone colors for font awesome icons with numbers or symbols in them? Some of our departments requested to use link boxes with icons instead of steps blocks, but the [number icons](https://fontawesome.com/search?o=r&c=numbers&s=solid&ip=duotone) with circles or squares around them end up with insufficient color contrast due to the current red text on red background duotone colors. (Attached is an example of the different styles of font awesome numbers in duotone.)

## Screenshots

![image](https://github.com/user-attachments/assets/8ff7edd0-914b-4fcd-8627-d6562fbc5fd8)


An issue related to an accessibility concern

Roadmap

Milestones

Minerva 1.5.0