Appearance
Languages & themes
Visitors can read the site in their own language and pick light or dark mode and a colour palette. You decide which languages exist, whether visitors may switch theme, and what new visitors see first.
Languages
The platform ships with English plus Japanese, Korean, French, Italian, Spanish, Portuguese, German, Arabic, Russian and Chinese. Add, edit or switch them off in Admin → Languages.
Which language a visitor sees
- Signed in, with a saved language: that language.
- Otherwise, the language they picked in the language menu (remembered in their browser).
- Otherwise, your default language.
When a guest picks a language and then signs in, that choice is saved to their account. Emails are sent in the user's saved language too.
The language menu in the header only appears when Language switcher is on in General settings. With it off, everyone sees the default language.
Right-to-left
For Arabic (and Hebrew, Persian or Urdu, if you add them), the whole site is mirrored: text, menus, tables and the trade screen run right-to-left. The mirrored stylesheets are built automatically (Building assets). The admin panel always stays left-to-right.
Translating
Interface texts are translated in Admin → Languages → translations. Press Sync to publish. Pages and articles have their own language versions (Pages, Articles).
Light, dark and system
Two switches in General settings control the theme:
| Dark mode | Dark by default | New visitors see | Can visitors switch? |
|---|---|---|---|
| Off | – | Light | No, the toggle is hidden |
| On | Off | Their device's setting (light or dark) | Yes |
| On | On | Dark (the default: both switches are on until you change them) | Yes |
Visitors switch with the sun/moon toggle in the header, or in the settings menu (gear icon) under Appearance: Light, Dark or System (follow the device). Their choice is remembered.
Mobile app: the app starts in dark too. Users change it in Settings → Theme (System, Light, Dark); the choice is kept on the device. The default is themeMode in mobile/lib/features/settings/settings_controller.dart.
Colour palettes
The site and the app ship with five palettes. Each one changes the brand colour (buttons, links, highlights) and keeps the same neutral and market colours, so green still means up and red down. Gold (yellow) is the default, and the palette choice is hidden from visitors: everyone sees Gold.
| Palette | Brand colour |
|---|---|
| Gold (default) | ● #F0B90B yellow |
| Ember | ● #FF4F29 orange-red |
| Ocean | ● #1E6FFF blue |
| Violet | ● #7B5CFA violet |
| Mint | ● #13C2C2 teal |
Two .env settings control this (environment):
| Setting | Default | What it does |
|---|---|---|
UI_PALETTE | gold | The palette everyone gets: gold, ember, ocean, violet or mint |
UI_PALETTE_PICKER | false | true shows Color theme in the settings menu (gear icon) again. Visitors' choice is then saved in their browser for a year |
While the picker is off, an old choice saved in a visitor's browser is ignored. The page renders in the palette straight away, without a flash of another colour, and the chart on the trade page follows the palette and theme too.
Mobile app: the app uses Gold and hides Settings → Color palette as well. To change that, edit kDefaultPalette / kPalettePicker in mobile/lib/features/settings/settings_controller.dart and rebuild the app.
Changing the colours (developers)
Palettes are Sass files in resources/sass/Themes/prime/palettes/, one per palette, each with a light and dark set of colours:
- To restyle the whole site, edit
_gold.scss(the default palette). - To add a palette, copy
_gold.scss, rename it, change$name, and register it inpalettes/_index.scssand inresources/js/Themes/prime/palettes.js(id, name and the picker swatch colour). The app's colours are generated from the same files (mobile/lib/core/theme/tokens.dart). - To change the default, set
UI_PALETTEin.env(no rebuild needed for the website; runphp artisan config:cacheagain if you cache the configuration).
Then rebuild the visitor bundle.
Time zone
Every date and time on the website is shown in the visitor's chosen time zone: order and trade history, deposits and withdrawals, reports, P2P orders and chat, articles, launchpad and staking dates, merchant pages, the footer clock and the TradingView chart's time axis. The admin panel follows the admin's own choice too.
- Where: header Settings (gear) → Time zone. Options: Server time (the default), This device (the zone the browser reports) and every IANA time zone, sorted by UTC offset, for example
(UTC+09:00) Asia/Tokyo. - Default: the server's zone,
'timezone'inconfig/app.php(UTC). Keep the server on UTC: the database stores UTC and only the display is converted. - Saved: for signed-in users on the account (
users.timezone), so it follows them to every browser; for guests in atimezonecookie. A changed zone applies at once, without reloading. - Only real IANA zone names are accepted (anything else is refused or ignored), so the setting can't be used to inject anything.
What stays in UTC on purpose: texts that describe when the server does something, such as "Staking rewards are calculated every day at 00:00 UTC". Calendar dates without a time (for example "joined 2026-10-31") are shown as they are.
For developers
Show server times with $dt(value) in templates ('date', 'time', 'datetime-short' styles), or serverDate(value) / this.$toDate(value) in scripts (resources/js/Functions/DateTime.js). Strings without a zone such as 2026-10-31 09:35:47 or 31-10-2026 09:35 are read as server time. Date.prototype.toLocaleString() and friends default to the chosen zone.
Other settings in the menu
On the trade page, the gear menu gets a second tab, Layout, with the layout settings: presets, which panels show, and the side of the trading panel. See Trade layout.
