Hermes
56c976a935
- Expand SUPPORTED_LANGS from 5 to all 31 languages matching backend - Expand LANG_NAMES to include all 31 native language names - Add RTL_LANGS set (ar, fa, ur) for multi-language RTL support - Fix applyTranslations() to always write resolved value (clears stale translations when switching back to English) - Fix loadTranslations() to clear translations on fetch failure/error - Add monotonic _langRequestId token to prevent out-of-order async resolution race (A->B->A scenario) - Wrap localStorage access in try/catch for privacy mode environments - Validate stored language code against SUPPORTED_LANGS on init - Always set document.documentElement.dir/lang on init (not just RTL) - Add scrollable dropdown for 31 languages (max-height: 320px) - Fix backend i18n route to use LANGUAGE_META instead of hardcoded 5-lang map - Rebuild dist bundles Codex grade: A (urn:ump:kicey7d7dnockmlk547cmm4qbdvygcj3g6waasrqv2yckbzem5bq) 1775/1775 tests pass
DashCaddy Onboarding System
This directory contains the JavaScript modules for the user onboarding tooltip system.
Files
- onboarding.js - Main entry point, initializes the onboarding system
- tour-manager.js - Orchestrates the onboarding flow and manages tour state
- progress-tracker.js - Manages persistent storage of user progress
- tooltip-definitions.js - Defines all tooltip content and positioning
- dns-template-selector.js - Presents DNS server template options
- theme-adapter.js - Ensures tooltips match the current dashboard theme
Load Order
The scripts are loaded in the following order (as defined in status/index.html):
- progress-tracker.js
- theme-adapter.js
- tooltip-definitions.js
- dns-template-selector.js
- tour-manager.js
- onboarding.js (main initialization)
Dependencies
- Driver.js - Loaded from CDN (https://cdn.jsdelivr.net/npm/driver.js@1.3.1/)
- Dashboard CSS variables (for theming)
- Browser localStorage API (for progress tracking)
Integration
The onboarding system integrates with:
- Dashboard theme system (via CSS variables)
- App template selector (for DNS server deployment)
- Local storage (for progress persistence)
Development
Each module is wrapped in an IIFE (Immediately Invoked Function Expression) to avoid global namespace pollution. Modules communicate through well-defined interfaces and the window object where necessary.