You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new figma libraries release (end of 2025) simplifies our figma libraries down to a reduced set, primarily built around 1 set of components supporting 2 themes–UITK Legacy and JPM Brand.
How do we align the theme in code to mirror what design teams will providing tech teams in their documentation?
Salt will provide two themes (uitk and brand) for technical components.
Changing from these defaults is something a Business Library will own (i.e., i want the brand theme but blue buttons... not a Salt recommendation–technically possible but teams will have to maintain it themselves).
How do we get ourselves to a state where the defaults in code and figma are the same?
Salt Provider – Stays the same
Salt Provider Next – Deprecate
Or add a prop to the Next which changes the defaults
We still wouldn’t have the ‘Next Legacy’ in code though
Salt Provider Brand – Updated to be the same as the brand in Figma
Capability to support a Next Legacy theme but not the Salt recommendation–needs to be owned by the Business Library
Are there any open-source problems if we explicitly name the theme ‘JPM Brand’ and set the defaults to brand? Better as something more generic in code (i.e., ‘Brand’). Check with Sean if this is ok?
Should we consider removing ‘Accent’ from the new provider? Other styling options remain relevant under the hood but ‘accent’ is the difference between the UITK Legacy (blue) and JPM Brand (teal).
The text was updated successfully, but these errors were encountered:
Have we considered just adding support the the current SaltProvider? We have a theme prop that could be set to "brand". This would potentially be more future proof as we'd avoid adding another provider and it might work if they are using SaltProviderNext already.
The new figma libraries release (end of 2025) simplifies our figma libraries down to a reduced set, primarily built around 1 set of components supporting 2 themes–UITK Legacy and JPM Brand.
How do we align the theme in code to mirror what design teams will providing tech teams in their documentation?
Notes from @bhoppers2008 discussion with @origami-z (10 Dec)
Salt will provide two themes (uitk and brand) for technical components.
Changing from these defaults is something a Business Library will own (i.e., i want the brand theme but blue buttons... not a Salt recommendation–technically possible but teams will have to maintain it themselves).
How do we get ourselves to a state where the defaults in code and figma are the same?
Should we consider removing ‘Accent’ from the new provider? Other styling options remain relevant under the hood but ‘accent’ is the difference between the UITK Legacy (blue) and JPM Brand (teal).
The text was updated successfully, but these errors were encountered: