diff --git a/site/docs/themes/index.mdx b/site/docs/themes/index.mdx
index 2483b1065c6..691601b6872 100644
--- a/site/docs/themes/index.mdx
+++ b/site/docs/themes/index.mdx
@@ -8,325 +8,203 @@ sidebar:
## What is a Salt theme
-Salt theme is a collection of defined visual styles that shape the overall look-and-feel of a digital product. This encompasses elements like color, typography, spacing, and corner radius, ensuring a consistent and cohesive appearance throughout the product.
+A Salt theme is a collection of defined visual styles that shape the overall look-and-feel of a digital product. This encompasses elements like color, typography, spacing, and corner radius, ensuring a consistent and cohesive appearance throughout the product.
A theme in Salt enables delivery teams to streamline the process of creating a consistent design language across their business domain, platforms or products.
-### Design tokens
+Salt uses themes to style its technical components and recommended libraries (such as AG Grid and Highcharts). Keeping styles separate to components makes it easy to switch between themes, without breaking or altering the underlying application build.
-Salt themes are defined by design tokens that are organized into 3 groups. Each group of tokens has a specific purpose:
+
-1. **[Characteristics](/salt/themes/characteristic-tokens)**: Semantically grouped tokens that are used to style components.
-2. **Palette**: Consolidated view of values used in Characteristic tokens – the simplest entry point to modify the theme.
-3. **Foundations**: Ramps of tokens for the raw values that underpin the design system.
+## Design tokens
-**Example: Status Characteristic Token in Toast component**
+Salt styles its components and patterns using design tokens. A design token is a text reference (or alias) for a specific value (px, %, pt, #, etc) which is used to style a component attribute (border color, border thickness, fill color, etc).
-Toast use status tokens to denote status with color, such as green for success.
+Salt themes are defined by design tokens that are organized into 3 levels:
-- Characteristic Token: `--salt-status-success-foreground-decorative`
-- Palette Token: `--salt-palette-success-foreground`
-- Foundation Token: `--salt-color-green-400` (default: `rgb(48, 156, 90)`)
+### Foundation tokens
-To keep tokens manageable, Salt doesn't create tokens for every style attribute of a component. Instead, Salt provides tokens that reflect component design decisions. This means we can maintain the quality of interaction design patterns and accessibility.
+Foundation tokens are the base level of the theme. They reference the raw values that underpin the design system. For instance, a color such as --green-100 references rgb(93, 189, 116) and --green-900 references rgb(35, 52, 43).
-## Supported themes
+These tokens can be used directly to define spacing and size of components and patterns.
-As of Q3 2024, Salt offers two themes: the current theme, that reflects the UI Toolkit (UITK) design language, and the new J.P. Morgan (JPM) brand-endorsed Salt Next theme.
+### Palette tokens
-In Salt's architecture, theme styles (known as design tokens) are kept separate from components. Regardless of the chosen theme (the look-and-feel), the underlying components remain the same. This separation makes it easy to switch between themes, without breaking or altering the underlying application build.
+Palette tokens are a subset of the most frequently used Foundation tokens, and are referenced by Characteristics tokens.
-
-
-## Salt Next theme
-
-Salt Next is a new theme for Salt which is built on new design foundations endorsed by the J.P. Morgan Corporate Brand team. It is a non-breaking update to the Salt library which officially brings 'styling options' and 'theming' capability to Salt components.
-
-Salt design system does not recommend customizing the look-and-feel of the current Salt theme.
-
-## Customizing with Salt Next
-
-There are two ways to customize the look-and-feel of components:
-
-1. **System-wide 'styling options'**: Choose from a selection of predefined design choices.
-2. **Theming**: Change the value of supported design tokens.
-
-### Styling options
-
-Styling options make it easy to adjust the design of Salt components across the system for a user group or use case:
-
-#### Density
-
-Relates to the amount of content that can fit on a screen based on the size and spacing of components. The four densities are high, medium, low, and touch.
-
-
-
-#### Accent / Mode
-
-Determines the dominant color – blue (aligned to the current theme) or teal (aligned to the Salt Next theme inline with the JP Morgan MasterBrand Styleguide) for light or dark mode.
-
-
-
-#### Corner radius
-
-Sets predefined corners in certain components to sharp or round.
-
-
-
-#### Font
-
-Displays heading and/or action fonts as Amplitude or Open Sans.
+A palette token can reference more than one foundational token–this capability enables components to toggle between ‘modes’ (e.g., light or dark). For example, the palette token --palette-positive-weak is --color-green-100 in light mode or --color-green-900 in dark mode.
-
+The palette level is the simplest point to define or modify a theme. Changing one token here can impact many characteristic tokens (and therefore components).
-### Theme recipe
+Never use a palette token to style components and patterns directly.
-Styling options can be combined as a 'theme recipe' to create design languages which are optimized for a specific context, for example:
+### Characteristics tokens
-**Example #1**: An external application is infrequently for limited data input An LOB define their design language to be low density, light mode, round corners, amplitude font, teal accent.
+A ‘Characteristic’ is a group of tokens that share the same purpose (or semantic). For example, the Status characteristic groups any tokens used to style error, warning or success component states.
-
+[Characteristic tokens](/salt/themes/characteristic-tokens) reference palette tokens. For instance, the characteristic token --salt-status-success-background references the palette token --salt-palette-positive-weak.
-**Example #2**: An established internal application is frequently to handling vast amounts of data. An LOB define their design language to be high density, dark mode, sharpcorners, open sans font, blue accent.
+These tokens can be used directly to color your components and patterns.
-
+### Banner example
-**Example #3**: An internal application is frequently to handle operational tasks. An LOB define their design language to be medium density, light mode, sharp corners, open sans font, teal accent.
+Banner gets its background color from the Status characteristic tokens.
-
+Characteristic: `--status-success-background`
+Palette: `--positive-weak`
+Foundation: `--color-green-100` (light mode) or `--color-green-900` (dark mode)
-There are several benefits to using styling options:
+
-- Allows easy modifications within predefined parameters.
-- Ensures a consistent look-and-feel across LOBs, products, or user groups.
-- Design languages can be easily updated as new styling options are released.
+### Design token intent
-Individual products within the LOB can customize their LOB design languages further if needed.
+To keep the number of design tokens in the Salt system manageable, Salt doesn't have tokens for every attribute of every component and every state.
-### Theming
+Instead, Salt provides tokens that reflect the design intent of the system. For example, if all Container borders are 1px thick then Salt provides a single --size-border token which updates all borders. This means we can maintain the cohesive systematic nature of the system as well as the quality of interaction design patterns and accessibility.
-If styling options alone don't achieve your desired visual design, you can create a new theme by changing the values of foundational, palette, or characteristic design tokens. This requires a deep understanding of the system, and significant design effort and increased cost. Possible use-cases for theming include:
+## Salt themes
-- Differentiating products while maintaining alignment with J.P. Morgan, e.g. unique accent bar colors for each product in a platform.
-- Aligning with an alternate design system to support migration to Salt.
-- Achieving greater parity with a brand other than J.P. Morgan, such as Chase.
+Salt has two themes:
-For example, you may choose to use a custom primary color in your app. Here the blue is replaced by a custom magenta (and checked to ensure 4.5:1 color contrast).
+1. JPM Brand theme
+2. Legacy UITK theme
-Any theme changes outside of 'styling options' mean you assume certain responsibilities from Salt. For example, if you change a token for a background color, you must ensure it meets accessibility standards for contrast ratios.
+### Legacy (UITK) theme
-Most design tokens are used across multiple components, so you need to understand the impact and test changes thoroughly across the product. In Figma, create and publish custom components independently of the provided Salt libraries. In code, create a centralized CSS stylesheet with the changes to be imported alongside the Salt theme.
+We understand that application migration journeys from the UITK system will vary in time and complexity. To enable phased migration of more complex applications, Salt can be used with its Legacy (UITK) theme together with UITK components.
-By modifying the theme, you own the cost of the change and are responsible for maintaining it.
+J.P. Morgan employees can read more about migration journeys and comparisons between the two systems.
-## White labelling isn't supported
+### JPM Brand theme
-White labelling allows the design system to be fully customized. It means you can take the base code and make it look completely different. It enables external companies to follow their own brand guidelines or mimic an alternate design system as closely as possible without having to build a design system from scratch.
+The JPM Brand theme (previously the Salt Next theme) brings the JPM Brand identity to CIB (Commercial & Investment Bank) digital applications and is the long-term visual identity of the Salt system.
-In code, each component would need to be wrapped and published as a new component, and from a design perspective a new set of libraries would need to be created and maintained.
+Working with Corporate Brand, CIB Marketing and LOB delivery teams, the Salt design system has adopted key styles to ensure visual alignment to the JPM Brand. Although not an exact match, these changes have been approved by both parties to address the complexities of desktop and web applications across the CIB. This brand theme will continue to evolve and grow as core requirements are fed back into the Salt system.
-White labelling requires significant changes and investment, and therefore is not supported by the Salt team.
+Due to the benefits of improved accessibility and brand alignment, Salt recommends that delivery teams plan to switch to the JPM Brand theme. If you’re a J.P. Morgan employee you can read more about the JPM Brand theme and if you should use it.
-## Component-level styling options
+#### Mode and densities
-In addition to the Salt Next theme, Salt is beginning to provide further component-level styling options for full borders (where the border is considered decorative) and drop shadows. The options are on a component-by-component basis and not a system-wide styling option. You can choose whether to have these options on each part of the application.
-
-Optional border support is already being rolled out across Salt's form control components (i.e., Input, Multiline, Combo Box). This feature can be combined with 'Corner' and 'Accent' styling option to provide the capability of Form Fields with full borders and rounded corners (a long request feature), aligned to brand.
+Supports light and dark modes across four densities, with teal serving as the primary accent color across the system–reflecting the JPM brand.
-## JPM brand endorsement
-
-Salt Next brings the [JPM brand](https://jpmcbrandtoolbox.com/) identity to CIB (Commercial & Investment Bank) digital applications.
+#### Color palette
-Working with Corporate Brand and CIB Marketing, the Salt design system has adopted key styles to ensure visual alignment to the JPM brand with the Salt Next theme. Although not an exact match, these changes have been approved by both parties to address the complexities of desktop and web applications across the CIB.
+The foundational color palette has been refreshed with updated shades of the same general colors found in UITK (gray, blue, teal, purple, red, orange, and green). These new colors are derived from the hue and saturation values in the JPM MasterBrand Styleguide.
-### Color palette
+The updated palette creates a lighter and brighter look suitable for both institutional and consumer experiences.
-The Salt Next foundational color palette has been refreshed with updated shades of the same general colors found in Salt and UITK (gray, blue, teal, purple, red, orange, and green). These new colors are derived from the hue and saturation values in the JPM MasterBrand Styleguide. The updated palette creates a lighter and brighter look suitable for both institutional and consumer experiences.
-
-
+
To address the many unused colors in the previous palette, the new color ramps have been reduced to nine swatches per ramp, with 500 as the shared middle value. We call this mode agnostic, meaning the color remains the same when switching between light and dark modes. The rest of the palette is based on 'equivalents,' where the ramp is inverted for dark mode—for example, blue-100 in light mode is equivalent to blue-900 in dark mode and vice versa.
-
+
The 500 series swatches have been carefully selected to ensure that primary text—white or black—achieves a minimum contrast ratio of 4.5:1 when placed on any of them. These swatches serve as the base color value for each ramp, with four lighter and four darker swatches on either side.
-
+
Primary, secondary, and tertiary backgrounds have been created as standalone swatches and are no longer tied to the color ramps. This includes snow, marble and limestone for light mode; and jet, granite and leather for dark mode.
-
-
-In addition to the foundational ramp, a revamped categorical color palette has been added, expanding from 20 to 40 color options per mode. The first 20 colors are mode agnostic, following the same principle as the 500 series in the foundational palette, ensuring primary text (white or black) meets a minimum contrast ratio of 4.5:1 when placed on any of these colors.
-
-
-
-### Amplitude font
+
-Salt Next introduces the Amplitude typeface, taken directly from the CIB Brand Guidelines, for use in header and display sizes as well as button labels. Open Sans remains the primary typeface for body copy text sizes and smaller in the Salt Next type ramps.
+A revamped categorical color palette has been added, expanding from 20 to 40 color options per mode. Colors 1 to 20 are mode agnostic (for use in both light and dark mode), following the same principle as the 500 series in the foundational palette, ensuring primary text (white or black) meets a minimum contrast ratio of 4.5:1 when placed on any of these colors.
-
-
-### Corner ramps
-
-Salt Next includes the ability to apply predefined corner radiuses to specified components. This rounded corner feature, from the CIB Brand Guidelines, allows designers to create a softer, more consumer-friendly look-and-feel in their products. Each density includes four different radiuses, which help achieve a sense of visual nesting when used together.
+
-
-
-## When to use the Salt Next theme
+#### Amplitude font
-Before using the Salt Next theme in design or development you should align with your Product team and check which theme to use, and when an appropriate time to switch themes is.
+The JPM Brand theme introduces the Amplitude typeface, taken directly from the CIB Brand Guidelines, for use in header and display sizes as well as button labels. Open Sans remains the primary typeface for body copy and smaller type.
-Due to the benefits of improved accessibility and brand alignment, and the ability to easily tailor look-and-feel to use cases, Salt recommends that delivery teams plan to switch to the Salt Next theme.
+
-## Guidance on using the current Salt theme
+#### Corner ramps
-We understand the importance of the current theme for products migrating from UI Toolkit. We will continue to ensure the availability of the current theme for Salt components.
+Corner radii have been systematically defined for specific components. Each density includes four different radii, which help achieve a sense of complementary visual nesting when used together.
-The current theme offers limited styling options except for density and mode. Customizing the look-and-feel of the current theme is not recommended. Please note that any customizations made to this theme are your responsibility to maintain.
+
-**If you are a designer**, be aware that if your product team is continuing to use the current theme you need to continue using the Salt Light and Dark Component Figma libraries, and associated Figma libraries. In H2 2024 we will include current theme support in the new Salt Next [variable-driven Figma library](#new-variable-driven-libraries).
+## Using themes in Figma
-## Guidance on using the Salt Next theme
+As of 2025, Salt provides a single Figma component and pattern library which supports both themes. This new library uses Figma variables to enable a choice of:
-The Salt Next theme is now stable and available in both Figma and code to use in your production delivery.
+1. **Mode:** Light, Dark
+2. **Density:** High, Medium, Low, Touch
+3. **Theme:** JPM Brand, Legacy (UITK)
-### Figma
+The Salt libraries you need to install into your projects are:
-To provide 'styling options' and theming capability the new Salt Next Figma libraries implement Salt design tokens as Figma [variables](https://help.figma.com/hc/en-us/sections/14506605769879-Variables) to define all the visual attributes of components.
+1. Salt DS Components and Patterns
+2. Salt DS Themes
+3. Salt DS Assets
-#### New variable-driven libraries
+_Optional_
-Using Figma variables enables us to reduce the number of Figma libraries we need to provide. Salt Next has the following libraries:
+1. Salt DS Legacy (UITK) Colors
+2. Salt DS JPM Brand Colors
+3. Salt DS JPMC Logo
-1. Salt (Next) Components & Patterns
-2. Salt (Next) Style Library
-3. Salt (Next) Color Library
+If you are a J.P. Morgan employee, you can read more about the [new libraries and how to start using them](https://go/salt-ds-internal/news/updates/20241203-new-figma-libraries).
-The 'Salt Icons' library has been updated with variable support to work with Salt Next components.
+### Installing the libraries
-To access the libraries:
+To install the libraries:
1. Go to the Assets panel in your Figma file.
2. Tap on the Libraries icon (open book icon).
-
+
-3. Search for 'Salt Next'.
+3. Search for 'Salt DS’.
-
+
-4. Add the three available libraries (referenced above) to your file.
+4. Add the libraries referenced above to your file.
-#### Using the style library
+### Using the Salt DS Themes library
-The style library includes all the Figma variables needed to design for Salt. It includes the semantic palette, category colors, size and spacing values, corner radiuses, typographic styles and more. Using Style Library variables to style your components automatically adds 'styling options' to your components.
+The Themes library includes all the Figma variables needed to style with Salt. It includes the semantic palette, category colors, size and spacing values, corner radii, typographic styles and more.
-The variables are set up to match our tokens in code. When inspecting a design in Figma's [Dev Mode](https://help.figma.com/hc/en-us/sections/15023066873239-Dev-Mode), you can see references that match our tokens, such as size and spacing values (e.g., `--spacing-100` in Figma maps to `--salt-spacing-100` in code).
+The variables are set up to match our tokens in code. When inspecting a design in Figma's Dev Mode, you can see references that match our tokens, such as size and spacing values (e.g., `--spacing-100` in Figma maps to`--salt-spacing-100` in code).
-
-
-#### Using the colors library
-
-The colors library provides access to all foundational color ramps (e.g., `--blue-100` to `--blue-900`). These colors are linked to the semantic styles in the Salt Next Styles library.
-
-You don't need to add these colors to your project unless you want to use them directly. For consistency across components and to benefit from 'styling options', Salt recommends only applying variables from the [Salt Next Style library](#using-the-style-library) to your project.
+Note: In code, all tokens are prefixed with ‘--salt-’, e.g., --salt-spacing-100.
-#### Using the component and pattern library
+
-The new variable-driven component and pattern library functions similarly to the current Salt component library but with key differences:
+### Using the Colors libraries
-- No need to switch between light and dark mode libraries.
-- No need to set density at the component level.
-- Access to new 'styling options' like round corners, accent color, and Amplitude as a heading and/or action font.
+The Colors libraries provides access to all foundational color ramps (e.g., `--blue-100` to `--blue-900`) for Legacy (UITK) and JPM Brand themes. These colors are linked to the semantic styles in the Salt DS Themes library.
-#### Using component 'styling options' in Figma
+You don't need to add these colors to your project unless you want to use them directly. For consistency across components, Salt recommends only applying variables from the Salt Themes library to your project.
-1. Add components: Drag from the Assets panel.
-2. Access 'styling options': In the right sidebar, click 'Change variable mode' (double hexagon) icon in the Layer panel to see all available options.
+### Using component modes in Figma
-
+1. Add components: Drag from the Assets panel.
+2. In the right sidebar, click ‘Apply variable mode' (swatch icon) button in the Layer panel to see all available options.
-3. For Pages, Groups, Sections, Frames or Components:
+
- 1. **Accent / Mode**: Set teal or blue (default) accent color (e.g., indicators in Tabs, CTA buttons) in light or dark mode.
- 1. **Corner**: Switch between sharp (default) and round corners.
- 1. **Density**: Change the size, spacing, corner radius and type size of elements for high (default), medium, low or touch density.
- 1. **Heading Font**: Set display and H1-H4 type styles as Open Sans or Amplitude.
- 1. **Action Font**: Set action components (mostly Buttons) type styles as Open Sans or Amplitude.
+3. For Pages, Groups, Sections, Frames or Components:
-#### Setting a theme recipe in Figma
+a. **Mode:** Light, Dark
+b. **Density:** High, Medium, Low, Touch
+c. **Theme:** Legacy (UITK), JPM Brand
-While you can set styling options for individual components, we recommend setting the required options for a product / LOB design language at a Figma Page level. This ensures consistency and avoids setting variables component-by-component. Options can be adjusted further at a nested Frame or Component level where you need to mix styling options.
+### Using themes in Code
-### Code
+You can define themes in code using the following components:
-The new Salt Provider, `SaltProviderNext`, offers new styling options like rounded corners and balanced color palettes. It extends the existing Salt Provider, keeping current options (light / dark modes, density levels) with new props for new options.
-To use it, replace the existing `SaltProvider` with `SaltProviderNext` and import the new theme CSS.
+- SaltProvider component provides the UITK (Legacy) theme
+- SaltProviderNext component provides the JPM Brand theme
```diff
// Swap out existing SaltProvider(s)
@@ -340,13 +218,13 @@ To use it, replace the existing `SaltProvider` with `SaltProviderNext` and impor
+ import "@salt-ds/theme/css/theme-next.css";
```
-The new provider adds `.salt-theme-next` to the root or provider element, along with any needed data attributes (e.g., `data-corner`). All values in `theme-next.css` are scoped to `.salt-theme-next` to override any existing values.
+SaltProviderNext adds `.salt-theme-next` to the root or provider element, along with any needed data attributes (e.g., data-corner). All values in `theme-next.css` are scoped to `.salt-theme-next` to override any existing values.
-#### Apply styling options
+#### Set SaltProviderNext as JPM Brand theme
-You can apply styling options as corresponding props to `SaltProviderNext` –
+To display components in the JPM Brand theme, you currently need to configure the styling option props of `SaltProviderNext`. You will need to configure the following attributes.
-```javascript
+```jsx
```
+
+A theme recipe is a defined selection of styling options for your theme. You can use an npm package to ensure consistency. For example, a team can encapsulate preferred presets, allowing product teams to use them without needing detailed knowledge of the options.
+
+```jsx
+
+```
+
+### Theming design tokens
+
+If styling options alone don't achieve your desired visual design, you can create a new theme by changing the values of the Foundation, Palette or Characteristic tokens. This requires a deep understanding of the system, and significant design effort and increased cost. Possible use-cases for theming include:
+
+- Differentiating products while maintaining alignment with J.P. Morgan, e.g. unique accent bar colors for each product in a platform.
+- Aligning with an alternate design system to support migration to Salt.
+- Achieving greater parity with a brand other than J.P. Morgan, such as Chase.
+
+For example, you may choose to use a custom primary color in your app. Here the blue is replaced by a custom magenta (and checked to ensure 4.5:1 color contrast).
+
+
+
+Any theme changes mean you assume certain responsibilities from Salt. For example, if you change a token for a background color, you must ensure it meets accessibility standards for contrast ratios.
+
+Most design tokens are used across multiple components, so you need to understand the impact and test changes thoroughly across the product. In Figma, create and publish custom components independently of the provided Salt libraries. In code, create a centralized CSS stylesheet with the changes to be imported alongside the Salt theme.
+
+By modifying the theme, you own the cost of the change and are responsible for maintaining it.
+
+### What about the current theme?
+
+We do not recommend customising the look-and-feel of the current theme. The design token structure has not been optimized for theming. Any customizations made to this theme are your responsibility to maintain.
+
+## White labelling isn't supported
+
+White labelling allows the design system to be fully customized. It means you can take the base code and make it look completely different. It enables external companies to follow their own brand guidelines or mimic an alternate design system as closely as possible without having to build a design system from scratch.
+
+In code, each component would need to be wrapped and published as a new component, and from a design perspective a new set of libraries would need to be created and maintained.
+
+White labelling requires significant changes and investment, and therefore is not supported by the Salt team.
diff --git a/site/public/img/theming/brand-endorsed-color-palette.png b/site/public/img/theming/brand-endorsed-color-palette.png
deleted file mode 100644
index 6a2d8d18dfe..00000000000
Binary files a/site/public/img/theming/brand-endorsed-color-palette.png and /dev/null differ
diff --git a/site/public/img/theming/color-contrast-ensured-500-color-series.png b/site/public/img/theming/color-contrast-ensured-500-color-series.png
deleted file mode 100644
index a1d29379c0b..00000000000
Binary files a/site/public/img/theming/color-contrast-ensured-500-color-series.png and /dev/null differ
diff --git a/site/public/img/theming/figma-next-library-add-to-file.png b/site/public/img/theming/figma-next-library-add-to-file.png
deleted file mode 100644
index 79da13e3bb7..00000000000
Binary files a/site/public/img/theming/figma-next-library-add-to-file.png and /dev/null differ
diff --git a/site/public/img/theming/figma-next-library-libraries-icon.png b/site/public/img/theming/figma-next-library-libraries-icon.png
deleted file mode 100644
index ce9d43e06ca..00000000000
Binary files a/site/public/img/theming/figma-next-library-libraries-icon.png and /dev/null differ
diff --git a/site/public/img/theming/figma-next-library-next-dev-mode.png b/site/public/img/theming/figma-next-library-next-dev-mode.png
deleted file mode 100644
index ee1f504d0f9..00000000000
Binary files a/site/public/img/theming/figma-next-library-next-dev-mode.png and /dev/null differ
diff --git a/site/public/img/theming/figma-next-library-variable-mode-switch.png b/site/public/img/theming/figma-next-library-variable-mode-switch.png
deleted file mode 100644
index f73e5963053..00000000000
Binary files a/site/public/img/theming/figma-next-library-variable-mode-switch.png and /dev/null differ
diff --git a/site/public/img/theming/input-border-styling-options.png b/site/public/img/theming/input-border-styling-options.png
deleted file mode 100644
index 94cc3adbdbe..00000000000
Binary files a/site/public/img/theming/input-border-styling-options.png and /dev/null differ
diff --git a/site/public/img/theming/mode-agnostic-blue-colors.png b/site/public/img/theming/mode-agnostic-blue-colors.png
deleted file mode 100644
index 959f9f6fc8c..00000000000
Binary files a/site/public/img/theming/mode-agnostic-blue-colors.png and /dev/null differ
diff --git a/site/public/img/theming/new-amplitude-typeface.png b/site/public/img/theming/new-amplitude-typeface.png
deleted file mode 100644
index 1cf3f76c45d..00000000000
Binary files a/site/public/img/theming/new-amplitude-typeface.png and /dev/null differ
diff --git a/site/public/img/theming/new-corner-ramps.png b/site/public/img/theming/new-corner-ramps.png
deleted file mode 100644
index e6db53f0599..00000000000
Binary files a/site/public/img/theming/new-corner-ramps.png and /dev/null differ
diff --git a/site/public/img/theming/revamped-categorical-color-palette.png b/site/public/img/theming/revamped-categorical-color-palette.png
deleted file mode 100644
index aa9f973008d..00000000000
Binary files a/site/public/img/theming/revamped-categorical-color-palette.png and /dev/null differ
diff --git a/site/public/img/theming/salt-technology-stack.png b/site/public/img/theming/salt-technology-stack.png
deleted file mode 100644
index 681b4176b57..00000000000
Binary files a/site/public/img/theming/salt-technology-stack.png and /dev/null differ
diff --git a/site/public/img/theming/standalone-background-colors.png b/site/public/img/theming/standalone-background-colors.png
deleted file mode 100644
index d08e24cdfc1..00000000000
Binary files a/site/public/img/theming/standalone-background-colors.png and /dev/null differ
diff --git a/site/public/img/theming/styling-options-button-accent-mode-example.png b/site/public/img/theming/styling-options-button-accent-mode-example.png
deleted file mode 100644
index 88d68d95a46..00000000000
Binary files a/site/public/img/theming/styling-options-button-accent-mode-example.png and /dev/null differ
diff --git a/site/public/img/theming/styling-options-button-corner-example.png b/site/public/img/theming/styling-options-button-corner-example.png
deleted file mode 100644
index e0e74aebeb7..00000000000
Binary files a/site/public/img/theming/styling-options-button-corner-example.png and /dev/null differ
diff --git a/site/public/img/theming/styling-options-button-densities-example.png b/site/public/img/theming/styling-options-button-densities-example.png
deleted file mode 100644
index e73ffef5d13..00000000000
Binary files a/site/public/img/theming/styling-options-button-densities-example.png and /dev/null differ
diff --git a/site/public/img/theming/styling-options-button-font-example.png b/site/public/img/theming/styling-options-button-font-example.png
deleted file mode 100644
index dbed3a3c020..00000000000
Binary files a/site/public/img/theming/styling-options-button-font-example.png and /dev/null differ
diff --git a/site/public/img/theming/theme-recipe-hd-dark-sharp-open-sans-blue.png b/site/public/img/theming/theme-recipe-hd-dark-sharp-open-sans-blue.png
deleted file mode 100644
index 132a27bdf02..00000000000
Binary files a/site/public/img/theming/theme-recipe-hd-dark-sharp-open-sans-blue.png and /dev/null differ
diff --git a/site/public/img/theming/theme-recipe-ld-light-round-amplitude-teal.png b/site/public/img/theming/theme-recipe-ld-light-round-amplitude-teal.png
deleted file mode 100644
index 2ee873fa2f7..00000000000
Binary files a/site/public/img/theming/theme-recipe-ld-light-round-amplitude-teal.png and /dev/null differ
diff --git a/site/public/img/theming/theme-recipe-md-light-sharp-open-sans-teal.png b/site/public/img/theming/theme-recipe-md-light-sharp-open-sans-teal.png
deleted file mode 100644
index d1f8f2654ae..00000000000
Binary files a/site/public/img/theming/theme-recipe-md-light-sharp-open-sans-teal.png and /dev/null differ
diff --git a/site/public/img/theming/theme-v2-01.png b/site/public/img/theming/theme-v2-01.png
new file mode 100644
index 00000000000..6eabec839f4
Binary files /dev/null and b/site/public/img/theming/theme-v2-01.png differ
diff --git a/site/public/img/theming/theme-v2-02.png b/site/public/img/theming/theme-v2-02.png
new file mode 100644
index 00000000000..7bc6e412ed2
Binary files /dev/null and b/site/public/img/theming/theme-v2-02.png differ
diff --git a/site/public/img/theming/theme-v2-03.png b/site/public/img/theming/theme-v2-03.png
new file mode 100644
index 00000000000..c3ecd2caae3
Binary files /dev/null and b/site/public/img/theming/theme-v2-03.png differ
diff --git a/site/public/img/theming/theme-v2-04.png b/site/public/img/theming/theme-v2-04.png
new file mode 100644
index 00000000000..69ec787ef65
Binary files /dev/null and b/site/public/img/theming/theme-v2-04.png differ
diff --git a/site/public/img/theming/theme-v2-05.png b/site/public/img/theming/theme-v2-05.png
new file mode 100644
index 00000000000..9fa5e5e9856
Binary files /dev/null and b/site/public/img/theming/theme-v2-05.png differ
diff --git a/site/public/img/theming/theme-v2-06.png b/site/public/img/theming/theme-v2-06.png
new file mode 100644
index 00000000000..c8ce04d92d3
Binary files /dev/null and b/site/public/img/theming/theme-v2-06.png differ
diff --git a/site/public/img/theming/theme-v2-07.png b/site/public/img/theming/theme-v2-07.png
new file mode 100644
index 00000000000..1b4823a251a
Binary files /dev/null and b/site/public/img/theming/theme-v2-07.png differ
diff --git a/site/public/img/theming/theme-v2-08.png b/site/public/img/theming/theme-v2-08.png
new file mode 100644
index 00000000000..96e1fcf3902
Binary files /dev/null and b/site/public/img/theming/theme-v2-08.png differ
diff --git a/site/public/img/theming/theme-v2-09.png b/site/public/img/theming/theme-v2-09.png
new file mode 100644
index 00000000000..aac997a4c04
Binary files /dev/null and b/site/public/img/theming/theme-v2-09.png differ
diff --git a/site/public/img/theming/theme-v2-10.png b/site/public/img/theming/theme-v2-10.png
new file mode 100644
index 00000000000..88512769b29
Binary files /dev/null and b/site/public/img/theming/theme-v2-10.png differ
diff --git a/site/public/img/theming/theme-v2-11.png b/site/public/img/theming/theme-v2-11.png
new file mode 100644
index 00000000000..d5147b01f8e
Binary files /dev/null and b/site/public/img/theming/theme-v2-11.png differ
diff --git a/site/public/img/theming/theme-v2-12.png b/site/public/img/theming/theme-v2-12.png
new file mode 100644
index 00000000000..909ec4b5458
Binary files /dev/null and b/site/public/img/theming/theme-v2-12.png differ
diff --git a/site/public/img/theming/theme-v2-13.png b/site/public/img/theming/theme-v2-13.png
new file mode 100644
index 00000000000..db5fa232a27
Binary files /dev/null and b/site/public/img/theming/theme-v2-13.png differ
diff --git a/site/public/img/theming/theme-v2-14.png b/site/public/img/theming/theme-v2-14.png
new file mode 100644
index 00000000000..1dd1306a2ef
Binary files /dev/null and b/site/public/img/theming/theme-v2-14.png differ
diff --git a/site/public/img/theming/theme-v2-15.png b/site/public/img/theming/theme-v2-15.png
new file mode 100644
index 00000000000..52ecfad071a
Binary files /dev/null and b/site/public/img/theming/theme-v2-15.png differ
diff --git a/site/public/img/theming/theme-v2-16.png b/site/public/img/theming/theme-v2-16.png
new file mode 100644
index 00000000000..cf93faf5ce1
Binary files /dev/null and b/site/public/img/theming/theme-v2-16.png differ
diff --git a/site/public/img/theming/theming-custom-primary-color-example.png b/site/public/img/theming/theming-custom-primary-color-example.png
deleted file mode 100644
index ef10d5cdbb9..00000000000
Binary files a/site/public/img/theming/theming-custom-primary-color-example.png and /dev/null differ