Overview

The uhg theme will be removed in Abyss V2.

Why is the UHG theme being removed?

The uhg theme does not have an official set of design tokens, which means it cannot be aligned to design standards.

Migration

All teams currently using the uhg theme should migrate to the uhc theme as soon as possible.

Note: All actions in this guide can/should be implemented now in Abyss V1.

The uhg and uhc themes are very close in appearance. If UHG-specific styling is required, you can override using tokens.

Step by-step migration instructions are provided below.

Step 1: Update the theme used in your application from uhg to uhc.

// Old usage
const theme = createTheme('uhg');

// New usage
const theme = createTheme('uhc');

Step 2: Pass the enterpriseFont flag in the theme override object to maintain the Enterprise Sans font

const themeOverride = {
  enterpriseFont: true,
};

const theme = createTheme('uhc', themeOverride);

Step 3: If you are using Brandmark or IconBrand components, update them to use the brand prop.

<IconBrand
  icon="music"
  size={48}
  brand="uhg" // If you don't set this, it will default to your current theme (uhc)
/>

Note: Teams are welcome to use the uhc theme assets (logos, icons) if they prefer the updated branding.

Step 4: Override tokens (if needed)

If you need to preserve specific UHG token styling from V1, you can override tokens when creating your theme.

To learn more about overriding tokens, see the Flatten Tokens and Create Theme documentation.

Step 5: Test your application to ensure all components have the desired appearance.

As stated above the uhg and uhc themes are very similar, so minimal changes should be needed. However, it's important to verify that everything looks correct after the migration.

Note: Many teams may find the uhc theme meets their visual and functional needs without additional customization. Unless your team has specific styling requirements or a business request for a different look, you should expect little to no changes beyond the theme switch.

Smooth upgrade to V2

By completing the steps outlined above now in Abyss V1, you will have already addressed all uhg changes.

When Abyss V2 is officially released, your application should have no uhg-specific breaking issues, allowing for a smooth upgrade process.

Future of the UHG theme

There is a possibility that a fully defined UHG theme - with its own complete set of design tokens - may be created in the future. However, this is not currently planned and should not be expected in the near term.

Teams should use the uhc theme moving forward.