mirror of
https://github.com/vector-im/element-call.git
synced 2024-11-21 00:28:08 +08:00
aa628cc63c
As a first step towards adopting the Compound design system and the new Element Call designs, this pulls in Compound's color tokens and applies them to all existing components. I've tried to choose tokens based on the semantics of where they're used, but in some cases, where the new and old design systems differ in semantics, it was necessary to choose tokens based on their resulting color. These hacks can be removed as we implement more of the new designs. There were a set of environment variables that we used for custom themes, but Compound has way too many design tokens for that approach to still be a good idea, so I decided to replace them all with a single environment variable that just lets you write arbitrary custom CSS.
20 lines
785 B
Plaintext
20 lines
785 B
Plaintext
####
|
|
# Build-time app config
|
|
# Environment files are documented here:
|
|
# https://vitejs.dev/guide/env-and-mode.html#env-files
|
|
####
|
|
# Develop backend settings:
|
|
LIVEKIT_KEY="devkey"
|
|
LIVEKIT_SECRET="secret"
|
|
|
|
# Used for determining the homeserver to use for short urls etc.
|
|
# VITE_FALLBACK_STUN_ALLOWED=false
|
|
|
|
# CSS to be injected into the page for the purpose of custom theming.
|
|
# Generally, writing a custom theme involves overriding Compound design tokens,
|
|
# which are documented here:
|
|
# https://compound.element.io/?path=/docs/foundations-design-tokens--docs
|
|
# https://compound.element.io/?path=/docs/tokens-color-palettes--docs
|
|
# https://compound.element.io/?path=/docs/tokens-semantic-colors--docs
|
|
# VITE_CUSTOM_CSS=".cpd-theme-dark.cpd-theme-dark { --cpd-color-theme-bg: #101317; }"
|