[Umbrella ☂️] Rebranding Experience

[brionmario]

Thunder should make it effortless to rebrand both the source code and UI, enabling teams to adopt it as their own product (e.g., white-labeled SaaS, internal platforms, resellers).

Currently, product naming and branding concerns are scattered across the codebase and UI. This initiative focuses on eliminating hardcoded references and introducing a centralized, flexible branding system.

🚀 Goal

Make it possible to rebrand Thunder with minimal effort and code hunting.

A user should be able to change the product identity (name, visuals, tone) from a single source of truth, without modifying multiple files.

🧩 Scope

1️⃣ Customize & Personalize the Thunder Instance

Focus: Configuration-driven customization (no UI changes required)

• 📝 Customize terminal/UI texts, messages, placeholders, and labels
• 🌍 Support overrides for default copy (error messages, prompts, etc.)
• 🤝 Particularly useful for:
  • Resellers
  • White-labeled SaaS platforms

2️⃣ Customize OOTB Pages — No Code

Focus: Visual customization without development effort

• 🎨 Theme customization (colors, fonts, branding tokens)
• 🖼️ Logo and brand asset configuration
• 🌍 Internationalization (i18n) support
• 🧱 Layout customization via Design UI (drag-and-drop / config-driven)

3️⃣ Customize OOTB Pages — With Code

Focus: Developer-level customization

• 💻 Inject custom CSS
• 🧩 Extend or modify layouts programmatically
• ⚙️ Hook into rendering lifecycle (if applicable)
• 🧪 Enable advanced UI overrides beyond no-code capabilities

4️⃣ Take Full Control - Bring Your Own UI (BYOUI)

Focus: Headless / SDK-driven approach

• 📦 Use SDKs to build fully custom flows and UI components
• 🔐 Integrate with custom applications (SPA, mobile, etc.)
• 🧱 Replace all OOTB UI with custom implementations
• 🔄 Maintain compatibility with Thunder APIs and flows