StrataKit MUI modifications
Section titled “StrataKit MUI modifications”- The
font-familyhas been changed toInterVariable. See self-hosting fonts. - The typography scale has been adjusted to better align with StrataKit’s more compact visual language.
- The default
variantis now"body2"instead of"body1". - A warning will be logged during development if a heading variant is used without explicitly setting the
renderprop. - The
"secondary"color value has been removed. A"textTertiary"color value has been added.
Examples
Section titled “Examples”Heading
Section titled “Heading”Heading variants of the Typography will render the respective <h1> to <h6> heading elements. You should use the render prop to override the rendered element and maintain proper heading structure in your application. When the render prop is not set, StrataKit will log a warning during development.
Variants
Section titled “Variants”All of the stock MUI Typography variants are available, with sizing adjusted to fit StrataKit’s more compact visual language.
Colors
Section titled “Colors”By default, the Typography component inherits the ancestor’s color. Use the color prop to explicitly set the text color.
The following color are available for the color prop:
"textPrimary""textSecondary""textTertiary""textDisabled""primary""error""info""success""warning"
- Use the
variantprop of the Typography component to affect the visual presentation of the text. - Use the
renderprop to set the most semantically appropriate element. This is especially important for heading variants.
🚫 Don’t
Section titled “🚫 Don’t”- Don’t use Typography to disrupt or flatten the visual hierarchy.
- Don’t render a heading element when you simply want to grab attention.