Kener Docs
llms.txt
Search Documentation
Search through all documentation pages
Core Concepts

Internationalization

Configure language localization, timezone behavior, and date/time formats for your Kener status page.

Kener internationalization has three parts:

  1. Localization (translated UI text)
  2. Timezone handling (how date/time values are displayed)
  3. Date & time format (how dates and times are formatted)

Use this page to configure all three from the admin UI.

Quick setup

  1. Open Manage → Internationalization.
  2. In Languages:
    • select available locales,
    • pick a default locale,
    • click Save Languages.
  3. In Timezone Settings:
    • enable or disable Allow users to switch timezones,
    • click Save Timezone.
  4. In Date & Time Format:
    • set formats for Date + Time, Date Only, and Time Only,
    • click Save Format.

Localization

How it works

  • Locale files are JSON files in src/lib/locales/.
  • Each locale file stores translations under mappings.
  • Admin settings store:
    • selected locales,
    • default locale.

Only selected locales are exposed to users in the language selector.

Add or update translations

  1. Edit the locale file(s) in src/lib/locales/.
  2. Add missing keys under mappings.
  3. Run translation checks.

Example locale shape:

{
    "name": "English",
    "mappings": {
        "Status": "Status",
        "All Systems Operational": "All Systems Operational"
    }
}

Validate localization

Run these from project root:

node scripts/check-translations.js
node scripts/sort-translations.js
  • check-translations reports missing/unused keys.
  • sort-translations normalizes key order in locale files.

Timezone handling

How it works

  • Kener stores timestamps in UTC (Unix seconds).
  • On the client, Kener detects browser timezone automatically.
  • If timezone switching is enabled, users can change timezone manually from the public page controls.

Admin toggle

In Manage → Internationalization, the timezone switch controls whether manual timezone selection is shown to users:

  • ON: users can switch timezones.
  • OFF: users see auto-detected timezone behavior only.

Server timezone variable

Server-side timezone behavior is also affected by TZ.

For setup details, see: /docs/v4/setup/environment-variables#timezone

Date & time format

Kener uses three separate format strings to display dates and times across the status page:

Field Where it is used Default
Date + Time Incident timestamps, maintenance windows, event details PPp
Date Only Day headings, uptime history dates PP
Time Only Monitoring tick tooltips, time-only displays p

Set these in Manage → Internationalization → Date & Time Format. Type a format string directly or click a suggestion badge to fill the input.

Format tokens

Formats use date-fns format tokens. Common examples:

Token Output example Notes
PP Apr 29, 1453 Locale-aware date
PPp Apr 29, 1453, 12:00 AM Locale-aware date + time
yyyy-MM-dd 1453-04-29 ISO date
HH:mm 14:30 24-hour time
p 12:00 AM Locale-aware time

What does "Locale" mean?

Tokens that start with an uppercase P (like PP, PPp) are locale-aware — they automatically adapt to the user's browser language. For example, PP renders as "Apr 29, 2025" in English but "29 avr. 2025" in French. Non-locale tokens like yyyy-MM-dd always produce the same output regardless of language.

Tip

Kener does not display seconds anywhere in the UI. Avoid adding seconds tokens (ss, pp with seconds) to keep the interface clean. Use PPp instead of PPpp, and p or HH:mm instead of pp or HH:mm:ss.

Stored settings reference

Kener saves internationalization settings in site data with keys like:

Key Purpose
i18n.defaultLocale Default locale shown on first visit (unless user already has a language preference).
i18n.locales[] List of available locales and whether each one is selected.
tzToggle Enables/disables manual timezone switching in the public UI.
dateAndTimeFormat JSON object with datePlusTime, dateOnly, and timeOnly format strings.

Verification checklist

  • Language selector shows only selected locales.
  • Default language is used for first-time visits.
  • translation-report.json has no unexpected missing keys.
  • Time values render correctly for your locale/timezone.
  • Timezone selector visibility matches your tzToggle setting.

Troubleshooting

  • Missing translation keys in report

    • Add keys to all required locale files under mappings.
    • Re-run node scripts/check-translations.js.

  • Language not appearing in selector

    • Make sure it is selected in Manage → Internationalization.
    • Save language settings.

  • Timezone selector not visible

    • Enable Allow users to switch timezones and save.

  • Unexpected server-side time behavior