chore(analytics): completely scrub NEXT_PUBLIC prefix from umami website id across codebase and docs

components/analytics/SUMMARY.md

@@ -16,6 +16,7 @@ The project already had a solid foundation:
 ## What Was Enhanced
 
 ### 1. **Enhanced UmamiScript** (`components/analytics/UmamiScript.tsx`)
+
 - ✅ Added TypeScript props interface for customization
 - ✅ Added JSDoc documentation with usage examples
 - ✅ Added error handling for script loading failures
@@ -23,11 +24,13 @@ The project already had a solid foundation:
 - ✅ Improved type safety and comments
 
 ### 2. **Enhanced AnalyticsProvider** (`components/analytics/AnalyticsProvider.tsx`)
+
 - ✅ Added comprehensive JSDoc documentation
 - ✅ Added development mode logging
 - ✅ Improved code comments
 
 ### 3. **New Custom Hook** (`components/analytics/useAnalytics.ts`)
+
 - ✅ Type-safe `useAnalytics` hook for easy event tracking
 - ✅ `trackEvent()` method for custom events
 - ✅ `trackPageview()` method for manual pageview tracking
@@ -35,12 +38,14 @@ The project already had a solid foundation:
 - ✅ Development mode logging
 
 ### 4. **Event Definitions** (`components/analytics/analytics-events.ts`)
+
 - ✅ Centralized event constants for consistency
 - ✅ Type-safe event names
 - ✅ Helper functions for common event properties
 - ✅ 30+ predefined events for various use cases
 
 ### 5. **Comprehensive Documentation**
+
 - ✅ **README.md** - Full documentation with setup, usage, and best practices
 - ✅ **EXAMPLES.md** - 20+ practical examples for different scenarios
 - ✅ **QUICK_REFERENCE.md** - Quick start guide and troubleshooting
@@ -63,12 +68,14 @@ components/analytics/
 ## Key Features
 
 ### 🚀 Modern Implementation
+
 - Uses Next.js `Script` component (not old-school `<script>` tags)
 - TypeScript for type safety
 - React hooks for clean API
 - Environment variable configuration
 
 ### 📊 Comprehensive Tracking
+
 - Automatic pageview tracking on route changes
 - Custom event tracking with properties
 - E-commerce events (products, cart, purchases)
@@ -77,6 +84,7 @@ components/analytics/
 - Error and performance tracking
 
 ### 🎯 Developer Experience
+
 - Type-safe event tracking
 - Centralized event definitions
 - Development mode logging
@@ -84,6 +92,7 @@ components/analytics/
 - 20+ practical examples
 
 ### 🔒 Privacy & Performance
+
 - No PII tracking by default
 - Script loads after page is interactive
 - Minimal performance impact
@@ -95,7 +104,7 @@ The project is already configured in `docker-compose.yml`:
 
 ```yaml
 environment:
-  - NEXT_PUBLIC_UMAMI_WEBSITE_ID=${NEXT_PUBLIC_UMAMI_WEBSITE_ID}
+  - UMAMI_WEBSITE_ID=${UMAMI_WEBSITE_ID}
   - NEXT_PUBLIC_UMAMI_SCRIPT_URL=${NEXT_PUBLIC_UMAMI_SCRIPT_URL:-https://analytics.infra.mintel.me/script.js}
 ```
 
@@ -104,7 +113,7 @@ environment:
 Add to your `.env` file:
 
 ```bash
-NEXT_PUBLIC_UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3
+UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3
 ```
 
 ## Usage Examples
@@ -188,7 +197,7 @@ In development, you'll see console logs:
 
 ```bash
 # .env.local
-# NEXT_PUBLIC_UMAMI_WEBSITE_ID=
+# UMAMI_WEBSITE_ID=
 ```
 
 ## Troubleshooting
@@ -196,8 +205,9 @@ In development, you'll see console logs:
 ### Analytics Not Working?
 
 1. **Check environment variables:**
+
    ```bash
-   echo $NEXT_PUBLIC_UMAMI_WEBSITE_ID
+   echo $UMAMI_WEBSITE_ID
    ```
 
 2. **Verify script is loading:**
@@ -212,12 +222,12 @@ In development, you'll see console logs:
 
 ### Common Issues
 
-| Issue | Solution |
-|-------|----------|
-| No data in Umami | Check website ID and script URL |
-| Events not tracking | Verify `useAnalytics` hook is used |
-| Script not loading | Check network connection, CORS |
-| Wrong data | Verify event properties are correct |
+| Issue               | Solution                            |
+| ------------------- | ----------------------------------- |
+| No data in Umami    | Check website ID and script URL     |
+| Events not tracking | Verify `useAnalytics` hook is used  |
+| Script not loading  | Check network connection, CORS      |
+| Wrong data          | Verify event properties are correct |
 
 ## Performance Tips
 
@@ -239,13 +249,13 @@ In development, you'll see console logs:
 1. ✅ **Setup complete** - All files are in place
 2. ✅ **Documentation complete** - README, EXAMPLES, QUICK_REFERENCE
 3. ✅ **Code enhanced** - Better TypeScript, error handling, docs
-4. 📝 **Add to .env** - Set `NEXT_PUBLIC_UMAMI_WEBSITE_ID`
+4. 📝 **Add to .env** - Set `UMAMI_WEBSITE_ID`
 5. 🧪 **Test in development** - Verify events are tracked
 6. 🚀 **Deploy** - Analytics will work in production
 
 ## Quick Start Checklist
 
-- [ ] Add `NEXT_PUBLIC_UMAMI_WEBSITE_ID` to `.env` file
+- [ ] Add `UMAMI_WEBSITE_ID` to `.env` file
 - [ ] Verify `UmamiScript` is in `app/[locale]/layout.tsx`
 - [ ] Verify `AnalyticsProvider` is in `app/[locale]/layout.tsx`
 - [ ] Test in development mode (check console logs)