ComponentStyle
ComponentStyle manifests capture styling information for components.
They allow you to centralize typography, colors, spacing, and other visual rules.
Spec outline
Section titled “Spec outline”apiVersion: rainbow.bino.bi/v1alpha1
kind: ComponentStyle
metadata:
name: corporateTheme
spec:
content: {} # object or JSON stringspec.content can be either:
- A YAML object
- A JSON string (useful when copying from front-end configuration)
The exact shape of the content is interpreted by the front-end renderer.
YAML object style
Section titled “YAML object style”---
apiVersion: rainbow.bino.bi/v1alpha1
kind: ComponentStyle
metadata:
name: corporateTheme
spec:
content:
fontFamily: "Inter, system-ui, sans-serif"
headingColor: "#111827"
textColor: "#374151"
accentColor: "#1D4ED8"
table:
headerBackground: "#F3F4F6"
rowStripeBackground: "#F9FAFB"JSON string style
Section titled “JSON string style”---
apiVersion: rainbow.bino.bi/v1alpha1
kind: ComponentStyle
metadata:
name: kpiCardStyle
spec:
content: >-
{"fontFamily":"Inter,system-ui,sans-serif","accentColor":"#22C55E","borderRadius":"8px"}You typically reference styles from layout or component configuration according to your front-end conventions. Use placeholder screenshots in your docs to compare layouts with and without shared styles.