Branding and style guidelines are provided by the user experience group once approved. The approval process has many layers and currently results in a specification established in Figma for usage, design, and content. In development, styling is heavily based off Bootstrap and PRISM extends it under the hood.
This means, the class names provided by Bootstrap are likely available to be
used in your applications including the utility classes such as
text. Some Bootstrap class
names have also been made into modules such as
@prism/col for the Grid system.
When working with the ordering of different layers, keeping track of each individual position can be taxing. Below is a list of starting indexes based on the role of the component. Ranges are incremented in thousands to allow plenty of room for the number of things applications can hold.
Note, this list is different from the z-index variables Bootstrap provides. These variables are fine to use within the application as they will fall well below the ranges defined. The ranges defined here are standardized and used across several applications and shared services and influence the components built within the PRISM library. Stacking conflicts can likely be avoided by adhering to these ranges as well.
As of version
1.10.0, PRISM has one theme known as the "Manheim" theme. This
is the current face of PRISM. Other themes are in development to support other
brands and usage requirements. Themes are built and published through the
@prism/styles package. This package,
detailed here, contains built
files useful to style components within an application. Component sytles are
both bundled and separated within the theme directories published.