Operations and updates

Choose skins and fonts

Choose which designs accounts may wear, and add one of your own when the built-in set does not fit.

Choose the skins people can use

Under Settings → System → Skins, select the built-in and custom designs accounts may switch between from the top bar.

With fewer than two allowed, the switcher is hidden and everyone sees the design this deployment is configured with. With nothing allowed, that configured design is all anyone sees.

Add a custom skin

Open Settings → System → Skins → Custom skins and choose Manage custom skins.
Choose Add skin.
Enter a Skin id that starts with custom-; it names the folder the skin lives in.
Enter a Display name and pick the design it repaints in Built on.
Paste a Token sheet with one :root rule that overrides public design tokens.
Select Add skin.

A refused skin reports the token or the line to fix. Adding or removing a skin applies at once, in every page that is open.

What a skin may change

A skin may override public design tokens only, which in practice means the chat colors, the shadows, and the sans or monospace family.

A shadow value accepts none or a comma-separated list, and each shadow takes optional inset, two to four lengths and a color.

Use your own font

Under Custom skins, enter the Font family name.
Choose the WOFF2 file you want to serve.
Select Upload font.
Use the same family in the skin's token sheet, for example --font-sans: "Manrope", sans-serif;.

Each skin holds one normal variable font file up to 2 MiB, and the instance serves it to every viewer, including on the login page.

Note: Keep resource URLs and @font-face out of the token sheet. The instance generates the loading rule itself.

Remove a skin

Remove font takes the uploaded file away, and deleting a skin removes its font with it.

Remove deletes the skin folder from the instance, and anyone wearing that skin moves to the instance design.