Compare commits

...

8 Commits

Author SHA1 Message Date
72711c74ba umami
Some checks failed
Build & Deploy KLZ Cables / deploy (push) Failing after 13m20s
2026-01-24 22:03:06 +01:00
7e94feaf19 sheets 2026-01-24 21:44:14 +01:00
d90d7502c3 sheets 2026-01-23 13:59:35 +01:00
e5e2b646a0 pdf sheets from new excel 2026-01-23 13:10:08 +01:00
899b3c7ed4 schema 2026-01-23 12:16:18 +01:00
1a646282a0 json 2026-01-23 12:09:23 +01:00
84438f1492 json schema 2026-01-23 12:07:11 +01:00
dd5636450c excel 2026-01-22 14:16:18 +01:00
131 changed files with 4152 additions and 103 deletions

5
.env
View File

@@ -1,4 +1,7 @@
WOOCOMMERCE_URL=https://klz-cables.com
WOOCOMMERCE_CONSUMER_KEY=ck_38d97df86880e8fefbd54ab5cdf47a9c5a9e5b39
WOOCOMMERCE_CONSUMER_SECRET=cs_d675ee2ac2ec7c22de84ae5451c07e42b1717759
WORDPRESS_APP_PASSWORD=DlJH 49dp fC3a Itc3 Sl7Z Wz0k
WORDPRESS_APP_PASSWORD=DlJH 49dp fC3a Itc3 Sl7Z Wz0k'
# Umami Analytics
NEXT_PUBLIC_UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3

1
.tmp-mv170126-err.txt Normal file
View File

@@ -0,0 +1 @@
Sheet 1

1
.tmp-mv170126-out.txt Normal file

File diff suppressed because one or more lines are too long

View File

@@ -1,5 +1,7 @@
import { notFound } from 'next/navigation';
import Script from 'next/script';
import JsonLd from '@/components/JsonLd';
import { getBreadcrumbSchema, SITE_URL, LOGO_URL } from '@/lib/schema';
import { MDXRemote } from 'next-mdx-remote/rsc';
import { getPostBySlug, getAdjacentPosts, getReadingTime, getHeadings } from '@/lib/blog';
import { Metadata } from 'next';
@@ -321,31 +323,58 @@ export default async function BlogPost({ params: { locale, slug } }: BlogPostPro
</div>
{/* Structured Data */}
<Script
<JsonLd
id={`jsonld-${slug}`}
type="application/ld+json"
dangerouslySetInnerHTML={{
__html: JSON.stringify({
'@context': 'https://schema.org',
'@type': 'BlogPosting',
headline: post.frontmatter.title,
datePublished: post.frontmatter.date,
image: post.frontmatter.featuredImage ? `https://klz-cables.com${post.frontmatter.featuredImage}` : undefined,
author: {
'@type': 'Organization',
name: 'KLZ Cables',
url: 'https://klz-cables.com',
data={{
'@context': 'https://schema.org',
'@type': 'BlogPosting',
headline: post.frontmatter.title,
datePublished: post.frontmatter.date,
dateModified: post.frontmatter.date,
image: post.frontmatter.featuredImage ? `https://klz-cables.com${post.frontmatter.featuredImage}` : undefined,
author: {
'@type': 'Organization',
name: 'KLZ Cables',
url: 'https://klz-cables.com',
logo: 'https://klz-cables.com/logo.png'
},
publisher: {
'@type': 'Organization',
name: 'KLZ Cables',
logo: {
'@type': 'ImageObject',
url: 'https://klz-cables.com/logo.png',
},
publisher: {
'@type': 'Organization',
name: 'KLZ Cables',
logo: {
'@type': 'ImageObject',
url: 'https://klz-cables.com/logo.png',
},
},
description: post.frontmatter.excerpt,
mainEntityOfPage: {
'@type': 'WebPage',
'@id': `https://klz-cables.com/${locale}/blog/${slug}`,
},
articleSection: post.frontmatter.category,
wordCount: post.content.split(/\s+/).length,
timeRequired: `PT${getReadingTime(post.content)}M`
}}
/>
<JsonLd
id={`breadcrumb-${slug}`}
data={{
'@context': 'https://schema.org',
'@type': 'BreadcrumbList',
itemListElement: [
{
'@type': 'ListItem',
position: 1,
name: 'Blog',
item: `https://klz-cables.com/${locale}/blog`,
},
description: post.frontmatter.excerpt,
}),
{
'@type': 'ListItem',
position: 2,
name: post.frontmatter.title,
item: `https://klz-cables.com/${locale}/blog/${slug}`,
},
],
}}
/>
</article>

View File

@@ -1,6 +1,8 @@
import { useTranslations } from 'next-intl';
import { getTranslations } from 'next-intl/server';
import { Metadata } from 'next';
import JsonLd from '@/components/JsonLd';
import { getBreadcrumbSchema, SITE_URL, LOGO_URL } from '@/lib/schema';
import { Section, Container, Button, Heading, Card, Input, Textarea, Label } from '@/components/ui';
interface ContactPageProps {
@@ -37,9 +39,66 @@ export async function generateMetadata({ params: { locale } }: ContactPageProps)
export default function ContactPage() {
const t = useTranslations('Contact');
const locale = t('locale') || 'en'; // Fallback if needed, but usually passed via params
return (
<div className="flex flex-col min-h-screen bg-neutral-light">
<JsonLd
id="breadcrumb-contact"
data={{
'@context': 'https://schema.org',
'@type': 'BreadcrumbList',
itemListElement: [
{
'@type': 'ListItem',
position: 1,
name: t('title'),
item: `https://klz-cables.com/${locale}/contact`,
},
],
}}
/>
<JsonLd
id="local-business-contact"
data={{
'@context': 'https://schema.org',
'@type': 'LocalBusiness',
name: 'KLZ Cables',
image: 'https://klz-cables.com/logo.png',
'@id': 'https://klz-cables.com',
url: 'https://klz-cables.com',
telephone: '+49 881 92537298',
address: {
'@type': 'PostalAddress',
streetAddress: 'Trifthofstraße 57',
addressLocality: 'Weilheim i. OB',
postalCode: '82362',
addressCountry: 'DE',
},
geo: {
'@type': 'GeoCoordinates',
latitude: 47.8407,
longitude: 11.1421,
},
openingHoursSpecification: [
{
'@type': 'OpeningHoursSpecification',
dayOfWeek: [
'Monday',
'Tuesday',
'Wednesday',
'Thursday',
'Friday'
],
opens: '08:00',
closes: '17:00'
}
],
sameAs: [
'https://www.linkedin.com/company/klz-cables'
]
}}
/>
{/* Hero Section */}
<section className="bg-primary-dark text-white py-20 md:py-32 relative overflow-hidden">
<div className="absolute inset-0 opacity-20">

View File

@@ -6,6 +6,8 @@ import Footer from '@/components/Footer';
import UmamiScript from '@/components/analytics/UmamiScript';
import AnalyticsProvider from '@/components/analytics/AnalyticsProvider';
import { Metadata, Viewport } from 'next';
import JsonLd from '@/components/JsonLd';
import { getOrganizationSchema, SITE_URL } from '@/lib/schema';
export async function generateMetadata({params: {locale}}: {params: {locale: string}}): Promise<Metadata> {
const t = await getTranslations({locale, namespace: 'Index.meta'});

View File

@@ -1,4 +1,6 @@
import Hero from '@/components/home/Hero';
import JsonLd from '@/components/JsonLd';
import { getBreadcrumbSchema } from '@/lib/schema';
import ProductCategories from '@/components/home/ProductCategories';
import WhatWeDo from '@/components/home/WhatWeDo';
import RecentPosts from '@/components/home/RecentPosts';
@@ -13,6 +15,12 @@ import Reveal from '@/components/Reveal';
export default function HomePage({ params: { locale } }: { params: { locale: string } }) {
return (
<div className="flex flex-col min-h-screen">
<JsonLd
id="breadcrumb-home"
data={getBreadcrumbSchema([
{ name: 'Home', item: `/${locale}` },
])}
/>
<Hero />
<Reveal><ProductCategories /></Reveal>
<Reveal><WhatWeDo /></Reveal>

View File

@@ -1,4 +1,6 @@
import Script from 'next/script';
import JsonLd from '@/components/JsonLd';
import { getBreadcrumbSchema, SITE_URL } from '@/lib/schema';
import ProductSidebar from '@/components/ProductSidebar';
import ProductTabs from '@/components/ProductTabs';
import ProductTechnicalData from '@/components/ProductTechnicalData';
@@ -228,6 +230,18 @@ export default async function ProductPage({ params }: ProductPageProps) {
notFound();
}
// Extract technical data for schema
const technicalDataMatch = product.content.match(/technicalData=\{<ProductTechnicalData data=\{(.*?)\}\s*\/>\}/s);
let technicalItems = [];
if (technicalDataMatch) {
try {
const data = JSON.parse(technicalDataMatch[1]);
technicalItems = data.technicalItems || [];
} catch (e) {
console.error('Failed to parse technical data for schema', e);
}
}
const datasheetPath = getDatasheetPath(productSlug, locale);
const isFallback = (product.frontmatter as any).isFallback;
const categorySlug = slug[0];

View File

@@ -1,6 +1,8 @@
import { useTranslations } from 'next-intl';
import { getTranslations } from 'next-intl/server';
import { Metadata } from 'next';
import JsonLd from '@/components/JsonLd';
import { getBreadcrumbSchema, SITE_URL } from '@/lib/schema';
import { Section, Container, Heading, Badge, Button } from '@/components/ui';
import Image from 'next/image';
import Reveal from '@/components/Reveal';
@@ -42,6 +44,46 @@ export default function TeamPage() {
return (
<div className="flex flex-col min-h-screen bg-neutral-light">
<JsonLd
id="breadcrumb-team"
data={getBreadcrumbSchema([
{ name: t('hero.subtitle'), item: `/team` },
])}
/>
<JsonLd
id="person-michael"
data={{
'@context': 'https://schema.org',
'@type': 'Person',
name: t('michael.name'),
jobTitle: t('michael.role'),
worksFor: {
'@type': 'Organization',
name: 'KLZ Cables',
},
sameAs: [
'https://www.linkedin.com/in/michael-bodemer-33b493122/'
],
image: `${SITE_URL}/uploads/2024/12/DSC07768-Large.webp`
}}
/>
<JsonLd
id="person-klaus"
data={{
'@context': 'https://schema.org',
'@type': 'Person',
name: t('klaus.name'),
jobTitle: t('klaus.role'),
worksFor: {
'@type': 'Organization',
name: 'KLZ Cables',
},
sameAs: [
'https://www.linkedin.com/in/klaus-mintel-b80a8b193/'
],
image: `${SITE_URL}/uploads/2024/12/DSC07963-Large.webp`
}}
/>
{/* Hero Section */}
<section className="relative flex items-center justify-center overflow-hidden bg-primary-dark pt-32 pb-24 md:pt-[14%] md:pb-[12%]">
<div className="absolute inset-0 z-0">

16
components/JsonLd.tsx Normal file
View File

@@ -0,0 +1,16 @@
import Script from 'next/script';
interface JsonLdProps {
id?: string;
data: any;
}
export default function JsonLd({ id, data }: JsonLdProps) {
return (
<Script
id={id || `jsonld-${Math.random().toString(36).substr(2, 9)}`}
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}
/>
);
}

View File

@@ -4,16 +4,40 @@ import { useEffect } from 'react';
import { usePathname, useSearchParams } from 'next/navigation';
import { getAppServices } from '@/lib/services/create-services';
// Minimal client-side hook that sends Umami pageviews on route changes.
/**
* AnalyticsProvider Component
*
* Automatically tracks pageviews on client-side route changes.
* This component should be placed inside your layout to handle navigation events.
*
* @example
* ```tsx
* // In your layout.tsx
* <NextIntlClientProvider messages={messages} locale={locale}>
* <UmamiScript />
* <Header />
* <main>{children}</main>
* <Footer />
* <AnalyticsProvider />
* </NextIntlClientProvider>
* ```
*/
export default function AnalyticsProvider() {
const pathname = usePathname();
const searchParams = useSearchParams();
useEffect(() => {
if (!pathname) return;
const services = getAppServices();
const url = `${pathname}${searchParams?.size ? `?${searchParams.toString()}` : ''}`;
// Track pageview with the full URL
services.analytics.trackPageview(url);
if (process.env.NODE_ENV === 'development') {
console.log('[Umami] Tracked pageview:', url);
}
}, [pathname, searchParams]);
return null;

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,166 @@
# Umami Analytics Quick Reference
## Setup Checklist
- [ ] Add `NEXT_PUBLIC_UMAMI_WEBSITE_ID` to `.env` file
- [ ] Verify `UmamiScript` is in your layout
- [ ] Verify `AnalyticsProvider` is in your layout
- [ ] Test in development mode
- [ ] Check Umami dashboard for data
## Environment Variables
```bash
# Required
NEXT_PUBLIC_UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3
# Optional (defaults to https://analytics.infra.mintel.me/script.js)
NEXT_PUBLIC_UMAMI_SCRIPT_URL=https://analytics.infra.mintel.me/script.js
```
## Quick Usage Examples
### Track an Event
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function MyComponent() {
const { trackEvent } = useAnalytics();
const handleClick = () => {
trackEvent(AnalyticsEvents.BUTTON_CLICK, {
button_id: 'my-button',
page: 'homepage',
});
};
return <button onClick={handleClick}>Click Me</button>;
}
```
### Track a Pageview
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
function MyComponent() {
const { trackPageview } = useAnalytics();
const navigate = () => {
trackPageview('/custom-path');
// Navigate...
};
return <button onClick={navigate}>Go to Page</button>;
}
```
### Track E-commerce Events
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function ProductCard({ product }) {
const { trackEvent } = useAnalytics();
const addToCart = () => {
trackEvent(AnalyticsEvents.PRODUCT_ADD_TO_CART, {
product_id: product.id,
product_name: product.name,
price: product.price,
});
};
return <button onClick={addToCart}>Add to Cart</button>;
}
```
## Common Events
| Event | When to Use | Example Properties |
|-------|-------------|-------------------|
| `pageview` | Page loads | `{ url: '/products/123' }` |
| `button_click` | Button clicked | `{ button_id: 'cta', page: 'homepage' }` |
| `form_submit` | Form submitted | `{ form_id: 'contact', form_name: 'Contact Us' }` |
| `product_view` | Product page viewed | `{ product_id: '123', price: 99.99 }` |
| `product_add_to_cart` | Add to cart | `{ product_id: '123', quantity: 1 }` |
| `search` | Search performed | `{ search_query: 'cable', results: 42 }` |
| `user_login` | User logged in | `{ user_email: 'user@example.com' }` |
| `error` | Error occurred | `{ error_message: 'Something went wrong' }` |
## Testing
### Development Mode
In development, you'll see console logs:
```
[Umami] Tracked event: button_click { button_id: 'my-button' }
[Umami] Tracked pageview: /products/123
```
### Disable Analytics (Development)
```bash
# .env.local
# NEXT_PUBLIC_UMAMI_WEBSITE_ID=
```
## Troubleshooting
### Analytics Not Working?
1. **Check environment variables:**
```bash
echo $NEXT_PUBLIC_UMAMI_WEBSITE_ID
```
2. **Verify script is loading:**
- Open DevTools → Network tab
- Look for `script.js` request
- Check Console for errors
3. **Check Umami dashboard:**
- Log into Umami
- Verify website ID matches
- Check if data is being received
### 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 |
## Performance Tips
1. **Use `useCallback` for event handlers** to prevent unnecessary re-renders
2. **Debounce high-frequency events** (like search input)
3. **Don't track every interaction** - focus on meaningful events
4. **Use environment variables** to disable analytics in development
## Privacy & Compliance
- ✅ Don't track PII (personally identifiable information)
- ✅ Don't track sensitive data (passwords, credit cards)
- ✅ Follow GDPR and other privacy regulations
- ✅ Use anonymized IDs where possible
- ✅ Provide cookie consent if required
## Next Steps
1. Read [`README.md`](README.md) for detailed documentation
2. Check [`EXAMPLES.md`](EXAMPLES.md) for more use cases
3. Review [`analytics-events.ts`](analytics-events.ts) for event definitions
4. Explore [`useAnalytics.ts`](useAnalytics.ts) for the hook implementation

View File

@@ -0,0 +1,443 @@
# Umami Analytics Integration
This project uses [Umami Analytics](https://umami.is/) for privacy-focused website analytics. The implementation is modern, clean, and follows Next.js best practices.
## Overview
The analytics system consists of:
1. **`UmamiScript`** - Loads the Umami tracking script
2. **`AnalyticsProvider`** - Tracks pageviews on route changes
3. **`useAnalytics`** - Custom hook for tracking custom events
4. **`analytics-events.ts`** - Centralized event definitions
5. **`UmamiAnalyticsService`** - Service layer for analytics operations
## Setup
### Environment Variables
Add these to your `.env` file:
```bash
# Required: Your Umami website ID
NEXT_PUBLIC_UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3
# Optional: Custom Umami script URL (defaults to https://analytics.infra.mintel.me/script.js)
NEXT_PUBLIC_UMAMI_SCRIPT_URL=https://analytics.infra.mintel.me/script.js
```
### Docker Compose
The `docker-compose.yml` already includes the environment variables:
```yaml
environment:
- NEXT_PUBLIC_UMAMI_WEBSITE_ID=${NEXT_PUBLIC_UMAMI_WEBSITE_ID}
- NEXT_PUBLIC_UMAMI_SCRIPT_URL=${NEXT_PUBLIC_UMAMI_SCRIPT_URL:-https://analytics.infra.mintel.me/script.js}
```
## Usage
### 1. Automatic Pageview Tracking
The `AnalyticsProvider` component automatically tracks pageviews on client-side route changes. It's already included in your layout:
```tsx
// app/[locale]/layout.tsx
<NextIntlClientProvider messages={messages} locale={locale}>
<UmamiScript />
<Header />
<main>{children}</main>
<Footer />
<AnalyticsProvider />
</NextIntlClientProvider>
```
### 2. Tracking Custom Events
Use the `useAnalytics` hook to track custom events:
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function ProductCard({ product }) {
const { trackEvent } = useAnalytics();
const handleAddToCart = () => {
trackEvent(AnalyticsEvents.PRODUCT_ADD_TO_CART, {
product_id: product.id,
product_name: product.name,
product_category: product.category,
price: product.price,
});
};
return (
<button onClick={handleAddToCart}>
Add to Cart
</button>
);
}
```
### 3. Tracking Pageviews Manually
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
function CustomNavigation() {
const { trackPageview } = useAnalytics();
const navigateToCustomPage = () => {
// Track a custom pageview
trackPageview('/custom-path?param=value');
// Then perform navigation
window.location.href = '/custom-path?param=value';
};
return <button onClick={navigateToCustomPage}>Go to Custom Page</button>;
}
```
### 4. Using Predefined Events
The `analytics-events.ts` file provides a centralized list of events:
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents, AnalyticsEventProperties } from '@/components/analytics/analytics-events';
function ContactForm() {
const { trackEvent } = useAnalytics();
const handleSubmit = (formData: FormData) => {
// Track form submission
trackEvent(AnalyticsEvents.CONTACT_FORM_SUBMIT, {
form_id: 'contact-form',
form_name: 'Contact Us',
form_fields: {
name: formData.get('name'),
email: formData.get('email'),
message: formData.get('message'),
},
});
};
return <form onSubmit={handleSubmit}>{/* form fields */}</form>;
}
```
### 5. E-commerce Tracking Example
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function ProductPage({ product }) {
const { trackEvent } = useAnalytics();
// Track product view on page load
useEffect(() => {
trackEvent(AnalyticsEvents.PRODUCT_VIEW, {
product_id: product.id,
product_name: product.name,
product_category: product.category,
price: product.price,
});
}, [product]);
const handleAddToCart = () => {
trackEvent(AnalyticsEvents.PRODUCT_ADD_TO_CART, {
product_id: product.id,
product_name: product.name,
product_category: product.category,
price: product.price,
quantity: 1,
});
};
const handlePurchase = () => {
trackEvent(AnalyticsEvents.PRODUCT_PURCHASE, {
product_id: product.id,
product_name: product.name,
product_category: product.category,
price: product.price,
transaction_id: 'TXN-12345',
currency: 'EUR',
});
};
return (
<div>
<h1>{product.name}</h1>
<p>{product.description}</p>
<button onClick={handleAddToCart}>Add to Cart</button>
<button onClick={handlePurchase}>Buy Now</button>
</div>
);
}
```
### 6. Search & Filter Tracking
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function ProductFilter() {
const { trackEvent } = useAnalytics();
const handleFilterChange = (filters: Record<string, unknown>) => {
trackEvent(AnalyticsEvents.FILTER_APPLY, {
filter_type: 'category',
filter_value: filters.category,
filter_count: Object.keys(filters).length,
});
};
const handleSearch = (query: string) => {
trackEvent(AnalyticsEvents.SEARCH, {
search_query: query,
search_results_count: 42, // You'd get this from your search results
});
};
return (
<div>
<input onChange={(e) => handleSearch(e.target.value)} />
<select onChange={(e) => handleFilterChange({ category: e.target.value })}>
{/* filter options */}
</select>
</div>
);
}
```
### 7. User Account Events
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function LoginForm() {
const { trackEvent } = useAnalytics();
const handleLogin = (email: string) => {
trackEvent(AnalyticsEvents.USER_LOGIN, {
user_email: email,
login_method: 'email',
});
};
const handleLogout = () => {
trackEvent(AnalyticsEvents.USER_LOGOUT, {
user_id: 'user-123',
});
};
return (
<div>
<button onClick={() => handleLogin('user@example.com')}>Login</button>
<button onClick={handleLogout}>Logout</button>
</div>
);
}
```
### 8. Error Tracking
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function ErrorBoundary({ children }) {
const { trackEvent } = useAnalytics();
const handleError = (error: Error, errorInfo: React.ErrorInfo) => {
trackEvent(AnalyticsEvents.ERROR, {
error_message: error.message,
error_stack: error.stack,
error_component: errorInfo.componentStack,
});
};
return (
<ErrorBoundary onError={handleError}>
{children}
</ErrorBoundary>
);
}
```
## Event Reference
### Common Events
| Event Name | Description | Example Properties |
|------------|-------------|-------------------|
| `pageview` | Page view | `{ url: '/products/123' }` |
| `button_click` | Button clicked | `{ button_id: 'cta-primary', page: 'homepage' }` |
| `link_click` | Link clicked | `{ link_url: '/products', link_text: 'View Products' }` |
| `form_submit` | Form submitted | `{ form_id: 'contact-form', form_name: 'Contact Us' }` |
| `product_view` | Product page viewed | `{ product_id: '123', product_name: 'Cable', price: 99.99 }` |
| `product_add_to_cart` | Product added to cart | `{ product_id: '123', quantity: 1 }` |
| `product_purchase` | Product purchased | `{ product_id: '123', transaction_id: 'TXN-123' }` |
| `search` | Search performed | `{ search_query: 'cable', search_results_count: 42 }` |
| `filter_apply` | Filter applied | `{ filter_type: 'category', filter_value: 'high-voltage' }` |
| `user_login` | User logged in | `{ user_email: 'user@example.com' }` |
| `user_signup` | User signed up | `{ user_email: 'user@example.com' }` |
| `error` | Error occurred | `{ error_message: 'Something went wrong' }` |
### Custom Events
You can create any custom event by passing a string name:
```tsx
trackEvent('custom_event_name', {
custom_property: 'value',
another_property: 123,
});
```
## Best Practices
### 1. Use Centralized Event Definitions
Always use the `AnalyticsEvents` constant for consistency:
```tsx
// ✅ Good
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
trackEvent(AnalyticsEvents.PRODUCT_ADD_TO_CART, { ... });
// ❌ Avoid
trackEvent('product_add_to_cart', { ... }); // Typo risk!
```
### 2. Include Relevant Context
Add context to your events to make them more useful:
```tsx
// ✅ Good
trackEvent(AnalyticsEvents.BUTTON_CLICK, {
button_id: 'cta-primary',
page: 'homepage',
section: 'hero',
user_type: 'guest',
});
// ❌ Less useful
trackEvent(AnalyticsEvents.BUTTON_CLICK, {
button_id: 'cta-primary',
});
```
### 3. Track Meaningful Events
Focus on business-critical events:
- ✅ Product views, add to cart, purchases
- ✅ Form submissions (contact, newsletter, quote requests)
- ✅ Search queries and filter usage
- ✅ User authentication events
- ✅ Error occurrences
- ❌ Every mouse move
- ❌ Every scroll event (unless specifically needed)
- ❌ Every hover state change
### 4. Respect Privacy
- Don't track personally identifiable information (PII)
- Don't track sensitive data (passwords, credit cards, etc.)
- Use anonymized IDs where possible
- Follow GDPR and other privacy regulations
### 5. Test in Development
The analytics system includes development mode logging:
```bash
# In development, you'll see console logs:
[Umami] Tracked event: product_add_to_cart { product_id: '123' }
[Umami] Tracked pageview: /products/123
```
## Troubleshooting
### Analytics Not Working
1. **Check environment variables:**
```bash
echo $NEXT_PUBLIC_UMAMI_WEBSITE_ID
```
2. **Verify the script is loading:**
- Open browser DevTools
- Check Network tab for `script.js` request
- Check Console for any errors
3. **Check Umami dashboard:**
- Log into your Umami instance
- Verify the website ID matches
- Check if data is being received
### Development Mode
In development mode, you'll see console logs for all tracked events. This helps you verify that events are being tracked correctly without affecting your production analytics.
### Disabling Analytics
To disable analytics (e.g., for local development), simply remove the `NEXT_PUBLIC_UMAMI_WEBSITE_ID` environment variable:
```bash
# .env.local (not committed to git)
# NEXT_PUBLIC_UMAMI_WEBSITE_ID=
```
## Performance
The analytics implementation is optimized for performance:
- ✅ Uses Next.js `Script` component with `afterInteractive` strategy
- ✅ Script loads after page is interactive
- ✅ No blocking of critical rendering path
- ✅ Minimal JavaScript bundle size
- ✅ Automatic cleanup on route changes
## Security
- ✅ Environment variables are not exposed to the client (except `NEXT_PUBLIC_` prefixed ones)
- ✅ Script URL can be customized for self-hosted Umami instances
- ✅ Error handling prevents analytics from breaking your app
- ✅ Type-safe event tracking with TypeScript
## Additional Resources
- [Umami Documentation](https://umami.is/docs)
- [Next.js Script Component](https://nextjs.org/docs/app/api-reference/components/script)
- [Analytics Best Practices](https://umami.is/docs/best-practices)
## Support
For issues or questions about the analytics implementation, check:
1. This README for usage examples
2. The component source code for implementation details
3. The Umami documentation for platform-specific questions

View File

@@ -0,0 +1,268 @@
# Umami Analytics Implementation Summary
## ✅ Implementation Status: COMPLETE
Your project now has a **modern, clean, and comprehensive** Umami analytics implementation.
## What Was Already Implemented
The project already had a solid foundation:
1. **`UmamiScript.tsx`** - Next.js Script component for loading analytics
2. **`AnalyticsProvider.tsx`** - Automatic pageview tracking on route changes
3. **`UmamiAnalyticsService.ts`** - Service layer for event tracking
4. **Environment variables** in `docker-compose.yml`
## 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
- ✅ Added development mode warnings
- ✅ 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
-`useCallback` optimization for performance
- ✅ 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
-**SUMMARY.md** - This file
## File Structure
```
components/analytics/
├── UmamiScript.tsx # Script loader component
├── AnalyticsProvider.tsx # Route change tracker
├── useAnalytics.ts # Custom hook for event tracking
├── analytics-events.ts # Event definitions and helpers
├── README.md # Full documentation
├── EXAMPLES.md # Practical examples
├── QUICK_REFERENCE.md # Quick start guide
└── SUMMARY.md # This summary
```
## 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)
- User authentication events
- Search and filter tracking
- Error and performance tracking
### 🎯 Developer Experience
- Type-safe event tracking
- Centralized event definitions
- Development mode logging
- Comprehensive documentation
- 20+ practical examples
### 🔒 Privacy & Performance
- No PII tracking by default
- Script loads after page is interactive
- Minimal performance impact
- Easy to disable in development
## Environment Variables
The project is already configured in `docker-compose.yml`:
```yaml
environment:
- NEXT_PUBLIC_UMAMI_WEBSITE_ID=${NEXT_PUBLIC_UMAMI_WEBSITE_ID}
- NEXT_PUBLIC_UMAMI_SCRIPT_URL=${NEXT_PUBLIC_UMAMI_SCRIPT_URL:-https://analytics.infra.mintel.me/script.js}
```
### Required Setup
Add to your `.env` file:
```bash
NEXT_PUBLIC_UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3
```
## Usage Examples
### Basic Event Tracking
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function MyComponent() {
const { trackEvent } = useAnalytics();
const handleClick = () => {
trackEvent(AnalyticsEvents.BUTTON_CLICK, {
button_id: 'my-button',
page: 'homepage',
});
};
return <button onClick={handleClick}>Click Me</button>;
}
```
### E-commerce Tracking
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
function ProductCard({ product }) {
const { trackEvent } = useAnalytics();
const addToCart = () => {
trackEvent(AnalyticsEvents.PRODUCT_ADD_TO_CART, {
product_id: product.id,
product_name: product.name,
price: product.price,
});
};
return <button onClick={addToCart}>Add to Cart</button>;
}
```
### Custom Pageview Tracking
```tsx
'use client';
import { useAnalytics } from '@/components/analytics/useAnalytics';
function CustomNavigation() {
const { trackPageview } = useAnalytics();
const navigate = () => {
trackPageview('/custom-path');
// Navigate...
};
return <button onClick={navigate}>Go to Page</button>;
}
```
## Testing & Development
### Development Mode
In development, you'll see console logs:
```
[Umami] Tracked event: button_click { button_id: 'my-button' }
[Umami] Tracked pageview: /products/123
```
### Disable Analytics (Development)
```bash
# .env.local
# NEXT_PUBLIC_UMAMI_WEBSITE_ID=
```
## Troubleshooting
### Analytics Not Working?
1. **Check environment variables:**
```bash
echo $NEXT_PUBLIC_UMAMI_WEBSITE_ID
```
2. **Verify script is loading:**
- Open DevTools → Network tab
- Look for `script.js` request
- Check Console for errors
3. **Check Umami dashboard:**
- Log into Umami
- Verify website ID matches
- Check if data is being received
### 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 |
## Performance Tips
1. **Use `useCallback`** - The hook is already optimized
2. **Debounce high-frequency events** - See EXAMPLES.md
3. **Don't track every interaction** - Focus on meaningful events
4. **Use environment variables** - Disable in development
## Privacy & Compliance
- ✅ Don't track PII (personally identifiable information)
- ✅ Don't track sensitive data (passwords, credit cards)
- ✅ Follow GDPR and other privacy regulations
- ✅ Use anonymized IDs where possible
- ✅ Provide cookie consent if required
## Next Steps
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`
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
- [ ] Verify `UmamiScript` is in `app/[locale]/layout.tsx`
- [ ] Verify `AnalyticsProvider` is in `app/[locale]/layout.tsx`
- [ ] Test in development mode (check console logs)
- [ ] Check Umami dashboard for data
- [ ] Review EXAMPLES.md for specific use cases
- [ ] Start tracking custom events with `useAnalytics`
## Summary
Your Umami analytics implementation is now **production-ready** with:
-**Modern Next.js approach** (Script component, not old-school tags)
-**Type-safe API** (TypeScript throughout)
-**Comprehensive tracking** (pageviews, events, e-commerce, errors)
-**Excellent documentation** (README, examples, quick reference)
-**Developer-friendly** (hooks, helpers, development mode)
-**Performance optimized** (async loading, minimal impact)
-**Privacy conscious** (no PII, easy to disable)
The implementation is clean, maintainable, and follows Next.js best practices. You can now track any user interaction or business event with just a few lines of code.

View File

@@ -1,18 +1,59 @@
import Script from 'next/script';
export default function UmamiScript() {
const websiteId = process.env.NEXT_PUBLIC_UMAMI_WEBSITE_ID;
if (!websiteId) return null;
interface UmamiScriptProps {
/**
* Custom website ID to override the environment variable
*/
websiteId?: string;
/**
* Custom script URL to override the environment variable
*/
scriptUrl?: string;
}
const src =
/**
* Umami Analytics Script Component
*
* Loads the Umami analytics script only when a website ID is available.
* Uses Next.js Script component with 'afterInteractive' strategy for optimal performance.
*
* @example
* ```tsx
* // Uses environment variables automatically
* <UmamiScript />
*
* // Or provide custom values
* <UmamiScript websiteId="custom-id" scriptUrl="https://custom.analytics.com/script.js" />
* ```
*/
export default function UmamiScript({ websiteId, scriptUrl }: UmamiScriptProps) {
// Use provided website ID or fall back to environment variable
const finalWebsiteId = websiteId ?? process.env.NEXT_PUBLIC_UMAMI_WEBSITE_ID;
// If no website ID is available, don't render the script
if (!finalWebsiteId) {
if (process.env.NODE_ENV === 'development') {
console.warn('[Umami] NEXT_PUBLIC_UMAMI_WEBSITE_ID is not set. Analytics will be disabled.');
}
return null;
}
// Use provided script URL or fall back to environment variable or default
const finalScriptUrl = scriptUrl ??
process.env.NEXT_PUBLIC_UMAMI_SCRIPT_URL ??
'https://analytics.infra.mintel.me/script.js';
return (
<Script
src={src}
data-website-id={websiteId}
id="umami-analytics"
src={finalScriptUrl}
data-website-id={finalWebsiteId}
strategy="afterInteractive"
defer
// Add error handling for script loading failures
onError={(error) => {
console.error('[Umami] Failed to load analytics script:', error);
}}
/>
);
}

View File

@@ -0,0 +1,130 @@
/**
* Analytics Events Utility
*
* Centralized definitions for common analytics events and their properties.
* This helps maintain consistency across the application and makes it easier
* to track meaningful events.
*
* @example
* ```tsx
* import { useAnalytics } from '@/components/analytics/useAnalytics';
* import { AnalyticsEvents } from '@/components/analytics/analytics-events';
*
* function ProductPage() {
* const { trackEvent } = useAnalytics();
*
* const handleAddToCart = (productId: string, productName: string) => {
* trackEvent(AnalyticsEvents.PRODUCT_ADD_TO_CART, {
* product_id: productId,
* product_name: productName,
* page: 'product-detail'
* });
* };
*
* return <button onClick={() => handleAddToCart('123', 'Cable')}>Add to Cart</button>;
* }
* ```
*/
export const AnalyticsEvents = {
// Page & Navigation Events
PAGE_VIEW: 'pageview',
PAGE_SCROLL: 'page_scroll',
PAGE_EXIT: 'page_exit',
// User Interaction Events
BUTTON_CLICK: 'button_click',
LINK_CLICK: 'link_click',
FORM_SUBMIT: 'form_submit',
FORM_START: 'form_start',
FORM_ERROR: 'form_error',
// E-commerce Events
PRODUCT_VIEW: 'product_view',
PRODUCT_ADD_TO_CART: 'product_add_to_cart',
PRODUCT_REMOVE_FROM_CART: 'product_remove_from_cart',
PRODUCT_PURCHASE: 'product_purchase',
PRODUCT_WISHLIST_ADD: 'product_wishlist_add',
PRODUCT_WISHLIST_REMOVE: 'product_wishlist_remove',
// Search & Filter Events
SEARCH: 'search',
FILTER_APPLY: 'filter_apply',
FILTER_CLEAR: 'filter_clear',
// User Account Events
USER_SIGNUP: 'user_signup',
USER_LOGIN: 'user_login',
USER_LOGOUT: 'user_logout',
USER_PROFILE_UPDATE: 'user_profile_update',
// Content Events
BLOG_POST_VIEW: 'blog_post_view',
VIDEO_PLAY: 'video_play',
VIDEO_PAUSE: 'video_pause',
VIDEO_COMPLETE: 'video_complete',
DOWNLOAD: 'download',
// UI Interaction Events
MODAL_OPEN: 'modal_open',
MODAL_CLOSE: 'modal_close',
TOGGLE_SWITCH: 'toggle_switch',
ACCORDION_TOGGLE: 'accordion_toggle',
TAB_SWITCH: 'tab_switch',
// Error & Performance Events
ERROR: 'error',
PERFORMANCE: 'performance',
API_ERROR: 'api_error',
API_SUCCESS: 'api_success',
// Custom Business Events
QUOTE_REQUEST: 'quote_request',
CONTACT_FORM_SUBMIT: 'contact_form_submit',
NEWSLETTER_SUBSCRIBE: 'newsletter_subscribe',
BROCHURE_DOWNLOAD: 'brochure_download',
} as const;
/**
* Type-safe event properties for common events
*/
export type AnalyticsEventName = (typeof AnalyticsEvents)[keyof typeof AnalyticsEvents];
/**
* Common event property helpers
*/
export const AnalyticsEventProperties = {
/**
* Create properties for a product event
*/
product: (productId: string, productName: string, category?: string) => ({
product_id: productId,
product_name: productName,
product_category: category,
}),
/**
* Create properties for a form event
*/
form: (formId: string, formName: string, fields?: Record<string, unknown>) => ({
form_id: formId,
form_name: formName,
form_fields: fields,
}),
/**
* Create properties for a search event
*/
search: (query: string, filters?: Record<string, unknown>) => ({
search_query: query,
search_filters: filters,
}),
/**
* Create properties for a navigation event
*/
navigation: (from: string, to: string) => ({
from_page: from,
to_page: to,
}),
} as const;

View File

@@ -0,0 +1,77 @@
'use client';
import { useCallback } from 'react';
import { getAppServices } from '@/lib/services/create-services';
import type { AnalyticsEventProperties } from '@/lib/services/analytics/analytics-service';
/**
* Custom hook for tracking analytics events with Umami.
*
* Provides a convenient way to track custom events throughout your application.
*
* @example
* ```tsx
* import { useAnalytics } from '@/components/analytics/useAnalytics';
*
* function MyComponent() {
* const { trackEvent, trackPageview } = useAnalytics();
*
* const handleButtonClick = () => {
* trackEvent('button_click', {
* button_id: 'cta-primary',
* page: 'homepage'
* });
* };
*
* return <button onClick={handleButtonClick}>Click me</button>;
* }
* ```
*
* @example
* ```tsx
* // Track a custom pageview
* const { trackPageview } = useAnalytics();
* trackPageview('/custom-path?param=value');
* ```
*/
export function useAnalytics() {
const services = getAppServices();
/**
* Track a custom event with optional properties.
*
* @param eventName - The name of the event to track
* @param properties - Optional event properties (metadata)
*/
const trackEvent = useCallback(
(eventName: string, properties?: AnalyticsEventProperties) => {
services.analytics.track(eventName, properties);
if (process.env.NODE_ENV === 'development') {
console.log('[Umami] Tracked event:', eventName, properties);
}
},
[services]
);
/**
* Track a pageview (useful for custom navigation or SPA routing).
*
* @param url - The URL to track (defaults to current location)
*/
const trackPageview = useCallback(
(url?: string) => {
services.analytics.trackPageview(url);
if (process.env.NODE_ENV === 'development') {
console.log('[Umami] Tracked pageview:', url ?? 'current location');
}
},
[services]
);
return {
trackEvent,
trackPageview,
};
}

Binary file not shown.

171
faber-kabel-data.json Normal file
View File

@@ -0,0 +1,171 @@
[
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-N2XS-FL-2Y/",
"verwendung": "Zur Verlegung in Erde, in Wasser, im Freien, in Innenräumen und Kabelkanälen für EVU-Netze, Industrie- und Verteilernetze. Bei Verlegung in Kabelkanälen und Innenräumen muss berücksichtigt werden, dass der PE-Mantel nach DIN VDE 0482-332-1 nicht flammwidrig ist. Das Kabel ist für ungünstige Einsatzbedingungen geeignet, insbesondere wenn nach mechanischen Beschädigungen das Eindringen von Wasser in Quer- und Längsrichtung vermieden werden soll.",
"technischeDaten": {
"Zolltarifnummer (Warennummer)": "85446010900000000",
"Norm": "VDE 0276-620",
"Leitermaterial": "Cu, blank",
"Leiterklasse": "Kl.2 = mehrdrähtig",
"Aderisolation": "VPE DIX8",
"Feldsteuerung": "innere und äußere Leitschicht aus halbleitendem Kunststoff (Dreifachextrusion)",
"Schirm": "Cu-Drahtumspinnung + Querleitwendel",
"Mantelmaterial": "Polyethylen DMP2",
"Schichtenmantel": "ja",
"Kabel querwasserdicht": "ja",
"Kabel längswasserdicht": "ja",
"Mantelfarbe": "schwarz",
"UV-beständig": "ja",
"Als Außenkabel zulässig": "ja",
"Max. zulässige Leitertemperatur, °C": "90 °C",
"Zul. Kabelaußentemperatur, fest verlegt, °C": "70 °C",
"Zul. Kabelaußentemperatur, in Bewegung, °C": "-20 - +70 °C",
"Min. Biegeradius, fest verlegt": "15 x Ø",
"Aderzahl": "1",
"Mantelwanddicke": "2.1 mm",
"Metallbasis Cu (de)": "0 EUR/100 kg",
"Maßeinheit": "Meter"
}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-N2XS2Y/",
"verwendung": "Zur Verlegung in Erde, in Wasser, im Freien, in Innenräumen und Kabelkanälen für Kraftwerks-, Industrie- und Verteilernetze. Bei Verlegung in Kabelkanälen und Innenräumen muss berücksichtigt werden, dass der PE-Mantel halogenfrei ist, jedoch nicht flammwidrig nach DIN VDE 0482-332-1. Das Kabel kann infolge des widerstandsfähigen PE-Mantels bei der Verlegung und im Betrieb stark mechanisch beansprucht werden.",
"technischeDaten": {
"Norm": "VDE 0276-620",
"Leitermaterial": "Cu, blank",
"Leiterklasse": "Kl.2 = mehrdrähtig",
"Aderisolation": "VPE DIX8",
"Feldsteuerung": "innere und äußere Leitschicht aus halbleitendem Kunststoff (Dreifachextrusion)",
"Schirm": "Cu-Drahtumspinnung + Querleitwendel",
"Mantelmaterial": "Polyethylen DMP2",
"Mantelfarbe": "schwarz",
"Flammwidrigkeit": "keine",
"UV-beständig": "ja",
"Als Außenkabel zulässig": "ja",
"Max. zulässige Leitertemperatur, °C": "90 °C",
"Zul. Kabelaußentemperatur, fest verlegt, °C": "70 °C",
"Zul. Kabelaußentemperatur, in Bewegung, °C": "-20 - +70 °C",
"Min. Biegeradius, fest verlegt": "15 x Ø",
"Leiterform": "rund",
"Aderzahl": "1",
"Mantelwanddicke": "2.1 mm",
"Metallbasis Cu (de)": "0 EUR/100 kg",
"Maßeinheit": "Meter"
}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-N2XSF2Y/",
"verwendung": "",
"technischeDaten": {}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-N2XSY/",
"verwendung": "Zur Verlegung in Erde, in Wasser, im Freien, in Innenräumen und Kabelkanälen für Kraftwerks-, Industrie- und Verteilernetze. Das Kabel lässt sich aufgrund der guten Verlegeeigenschaften auch bei schwieriger Trassenführung leicht verlegen. Gemäß VDE 0276 müssen die Kabel vor direkter Sonneneinstrahlung geschützt sein.",
"technischeDaten": {
"Zolltarifnummer (Warennummer)": "85446010900000000",
"Norm": "VDE 0276-620",
"Leitermaterial": "Cu, blank",
"Leiterklasse": "Kl.2 = mehrdrähtig",
"Aderisolation": "VPE DIX8",
"Feldsteuerung": "innere und äußere Leitschicht aus halbleitendem Kunststoff (Dreifachextrusion)",
"Schirm": "Cu-Drahtumspinnung + Querleitwendel",
"Mantelmaterial": "PVC DMV6",
"Mantelfarbe": "rot",
"Flammwidrigkeit": "VDE 0482-332-1-2/IEC 60332-1-2",
"Als Außenkabel zulässig": "ja",
"Max. zulässige Leitertemperatur, °C": "90 °C",
"Zul. Kabelaußentemperatur, fest verlegt, °C": "70 °C",
"Zul. Kabelaußentemperatur, in Bewegung, °C": "-5 - +70 °C",
"Min. Biegeradius, fest verlegt": "15 x Ø",
"Leiterform": "rund",
"Aderzahl": "1",
"Metallbasis Cu (de)": "0 EUR/100 kg",
"Maßeinheit": "Meter"
}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-NA2XS2Y/",
"verwendung": "Zur Verlegung in Erde, in Wasser, im Freien, in Innenräumen und Kabelkanälen für Kraftwerks-, Industrie- und Verteilernetze. Bei Verlegung in Kabelkanälen und Innenräumen muss berücksichtigt werden, dass der PE-Mantel halogenfrei ist, jedoch nicht flammwidrig nach DIN VDE 0482-332-1. Das Kabel kann infolge des widerstandsfähigen PE-Mantels bei der Verlegung und im Betrieb stark mechanisch beansprucht werden.",
"technischeDaten": {
"Zolltarifnummer (Warennummer)": "85446090000000000",
"Norm": "VDE 0276-620",
"Leitermaterial": "Aluminium",
"Leiterklasse": "Kl.2 = mehrdrähtig",
"Aderisolation": "VPE DIX8",
"Feldsteuerung": "innere und äußere Leitschicht aus halbleitendem Kunststoff (Dreifachextrusion)",
"Schirm": "Cu-Drahtumspinnung + Querleitwendel",
"Mantelmaterial": "Polyethylen DMP2",
"Mantelfarbe": "schwarz",
"Flammwidrigkeit": "keine",
"UV-beständig": "ja",
"Als Außenkabel zulässig": "ja",
"Max. zulässige Leitertemperatur, °C": "90 °C",
"Zul. Kabelaußentemperatur, fest verlegt, °C": "70 °C",
"Zul. Kabelaußentemperatur, in Bewegung, °C": "-20 - +70 °C",
"Min. Biegeradius, fest verlegt": "15 x Ø",
"Aderzahl": "1",
"Metallbasis Al (de)": "0 EUR/100 kg",
"Metallbasis Cu (de)": "0 EUR/100 kg",
"Maßeinheit": "Meter"
}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-NA2XSF2Y/",
"verwendung": "",
"technischeDaten": {}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-NA2XS-FL-2Y/",
"verwendung": "Zur Verlegung in Erde, in Wasser, im Freien, in Innenräumen und Kabelkanälen für EVU-Netze, Industrie- und Verteilernetze. Bei Verlegung in Kabelkanälen und Innenräumen muss berücksichtigt werden, dass der PE-Mantel nach DIN VDE 0482-332-1 nicht flammwidrig ist. Das Kabel ist für ungünstige Einsatzbedingungen geeignet, insbesondere wenn nach mechanischen Beschädigungen das Eindringen von Wasser in Quer- und Längsrichtung vermieden werden soll.",
"technischeDaten": {
"Zolltarifnummer (Warennummer)": "85446090000000000",
"Norm": "VDE 0276-620",
"Leitermaterial": "Aluminium",
"Leiterklasse": "Kl.2 = mehrdrähtig",
"Aderisolation": "VPE DIX8",
"Mantelmaterial": "Polyethylen DMP2",
"Schichtenmantel": "ja",
"Kabel querwasserdicht": "ja",
"Kabel längswasserdicht": "ja",
"Mantelfarbe": "schwarz",
"Flammwidrigkeit": "keine",
"UV-beständig": "ja",
"Als Außenkabel zulässig": "ja",
"Max. zulässige Leitertemperatur, °C": "90 °C",
"Zul. Kabelaußentemperatur, fest verlegt, °C": "70 °C",
"Zul. Kabelaußentemperatur, in Bewegung, °C": "-20 - +70 °C",
"Min. Biegeradius, fest verlegt": "15 x Ø",
"Leiterform (Faber)": "RMv",
"Aderzahl": "1",
"Metallbasis Al (de)": "0 EUR/100 kg",
"Metallbasis Cu (de)": "0 EUR/100 kg",
"Maßeinheit": "Meter"
}
},
{
"url": "https://shop.faberkabel.de/Starkstromkabel-1-30-kV/Mittelspannungskabel/Mittelspannungskabel-NA2XSY/",
"verwendung": "Zur Verlegung in Erde, in Wasser, im Freien, in Innenräumen und Kabelkanälen für Kraftwerks-, Industrie- und Verteilernetze. Das Kabel lässt sich aufgrund der guten Verlegeeigenschaften auch bei schwieriger Trassenführung leicht verlegen. Gemäß VDE 0276 müssen die Kabel vor direkter Sonneneinstrahlung geschützt sein.",
"technischeDaten": {
"Zolltarifnummer (Warennummer)": "85446090000000000",
"Norm": "VDE 0276-620",
"Leitermaterial": "Aluminium",
"Leiterklasse": "Kl.2 = mehrdrähtig",
"Aderisolation": "VPE DIX8",
"Feldsteuerung": "innere und äußere Leitschicht aus halbleitendem Kunststoff (Dreifachextrusion)",
"Schirm": "Cu-Drahtumspinnung + Querleitwendel",
"Mantelmaterial": "PVC DMV6",
"Mantelfarbe": "rot",
"Flammwidrigkeit": "VDE 0482-332-1-2/IEC 60332-1-2",
"Als Außenkabel zulässig": "ja",
"Max. zulässige Leitertemperatur, °C": "90 °C",
"Zul. Kabelaußentemperatur, fest verlegt, °C": "70 °C",
"Zul. Kabelaußentemperatur, in Bewegung, °C": "-5 - +70 °C",
"Min. Biegeradius, fest verlegt": "15 x Ø",
"Leiterform (Faber)": "RMv",
"Aderzahl": "1",
"Metallbasis Al (de)": "0 EUR/100 kg",
"Metallbasis Cu (de)": "0 EUR/100 kg",
"Maßeinheit": "Meter"
}
}
]

33
lib/schema.ts Normal file
View File

@@ -0,0 +1,33 @@
import { getTranslations } from 'next-intl/server';
export const SITE_URL = 'https://klz-cables.com';
export const LOGO_URL = `${SITE_URL}/logo.png`;
export const getOrganizationSchema = () => ({
'@context': 'https://schema.org',
'@type': 'Organization',
name: 'KLZ Cables',
url: SITE_URL,
logo: LOGO_URL,
sameAs: [
'https://www.linkedin.com/company/klz-cables',
],
contactPoint: {
'@type': 'ContactPoint',
telephone: '+49-881-92537298',
contactType: 'customer service',
email: 'info@klz-vertriebs-gmbh.com',
availableLanguage: ['German', 'English']
}
});
export const getBreadcrumbSchema = (items: { name: string; item: string }[]) => ({
'@context': 'https://schema.org',
'@type': 'BreadcrumbList',
itemListElement: items.map((item, index) => ({
'@type': 'ListItem',
position: index + 1,
name: item.name,
item: item.item.startsWith('http') ? item.item : `${SITE_URL}${item.item}`,
})),
});

View File

@@ -0,0 +1,430 @@
# Analytics Service Layer
This directory contains the service layer implementation for analytics tracking in the KLZ Cables application.
## Overview
The analytics service layer provides a clean abstraction over different analytics implementations (Umami, Google Analytics, etc.) while maintaining a consistent API.
## Architecture
```
lib/services/analytics/
├── analytics-service.ts # Interface definition
├── umami-analytics-service.ts # Umami implementation
├── noop-analytics-service.ts # No-op fallback implementation
└── README.md # This file
```
## Components
### 1. AnalyticsService Interface (`analytics-service.ts`)
Defines the contract for all analytics services:
```typescript
export interface AnalyticsService {
track(eventName: string, props?: AnalyticsEventProperties): void;
trackPageview(url?: string): void;
}
```
**Key Features:**
- Type-safe event properties
- Consistent API across implementations
- Well-documented with JSDoc comments
### 2. UmamiAnalyticsService (`umami-analytics-service.ts`)
Implements the `AnalyticsService` interface for Umami analytics.
**Features:**
- Type-safe event tracking
- Automatic pageview tracking
- Browser environment detection
- Graceful error handling
- Comprehensive JSDoc documentation
**Usage:**
```typescript
import { UmamiAnalyticsService } from '@/lib/services/analytics/umami-analytics-service';
const service = new UmamiAnalyticsService({ enabled: true });
service.track('button_click', { button_id: 'cta' });
service.trackPageview('/products/123');
```
### 3. NoopAnalyticsService (`noop-analytics-service.ts`)
A no-op implementation used as a fallback when analytics are disabled.
**Features:**
- Maintains the same API as other services
- Safe to call even when analytics are disabled
- No performance impact
- Comprehensive JSDoc documentation
**Usage:**
```typescript
import { NoopAnalyticsService } from '@/lib/services/analytics/noop-analytics-service';
const service = new NoopAnalyticsService();
service.track('button_click', { button_id: 'cta' }); // Does nothing
service.trackPageview('/products/123'); // Does nothing
```
## Service Selection
The service layer automatically selects the appropriate implementation based on environment variables:
```typescript
// In lib/services/create-services.ts
const umamiEnabled = Boolean(process.env.NEXT_PUBLIC_UMAMI_WEBSITE_ID);
const analytics = umamiEnabled
? new UmamiAnalyticsService({ enabled: true })
: new NoopAnalyticsService();
```
## Environment Variables
### Required for Umami
```bash
NEXT_PUBLIC_UMAMI_WEBSITE_ID=59a7db94-0100-4c7e-98ef-99f45b17f9c3
```
### Optional (defaults provided)
```bash
NEXT_PUBLIC_UMAMI_SCRIPT_URL=https://analytics.infra.mintel.me/script.js
```
## API Reference
### AnalyticsService Interface
#### `track(eventName: string, props?: AnalyticsEventProperties): void`
Track a custom event with optional properties.
**Parameters:**
- `eventName` - The name of the event to track
- `props` - Optional event properties (metadata)
**Example:**
```typescript
service.track('product_add_to_cart', {
product_id: '123',
product_name: 'Cable',
price: 99.99,
quantity: 1,
});
```
#### `trackPageview(url?: string): void`
Track a pageview.
**Parameters:**
- `url` - The URL to track (defaults to current location)
**Example:**
```typescript
// Track current page
service.trackPageview();
// Track custom URL
service.trackPageview('/products/123?category=cables');
```
### UmamiAnalyticsService
#### Constructor
```typescript
new UmamiAnalyticsService(options: UmamiAnalyticsServiceOptions)
```
**Options:**
- `enabled: boolean` - Whether analytics are enabled
**Example:**
```typescript
const service = new UmamiAnalyticsService({ enabled: true });
```
### NoopAnalyticsService
#### Constructor
```typescript
new NoopAnalyticsService()
```
**Example:**
```typescript
const service = new NoopAnalyticsService();
```
## Type Definitions
### AnalyticsEventProperties
```typescript
type AnalyticsEventProperties = Record<
string,
string | number | boolean | null | undefined
>;
```
**Example:**
```typescript
const properties: AnalyticsEventProperties = {
product_id: '123',
product_name: 'Cable',
price: 99.99,
quantity: 1,
in_stock: true,
discount: null,
};
```
### UmamiAnalyticsServiceOptions
```typescript
type UmamiAnalyticsServiceOptions = {
enabled: boolean;
};
```
## Best Practices
### 1. Use the Service Layer
Always use the service layer instead of calling Umami directly:
```typescript
// ✅ Good
import { getAppServices } from '@/lib/services/create-services';
const services = getAppServices();
services.analytics.track('button_click', { button_id: 'cta' });
// ❌ Avoid
(window as any).umami?.track('button_click', { button_id: 'cta' });
```
### 2. Check Environment
The service layer automatically handles environment detection:
```typescript
// ✅ Safe - works in both server and client
const services = getAppServices();
services.analytics.track('event', { prop: 'value' });
// ❌ Unsafe - may fail in server environment
if (typeof window !== 'undefined') {
window.umami?.track('event', { prop: 'value' });
}
```
### 3. Use Type-Safe Events
Import events from the centralized definitions:
```typescript
import { AnalyticsEvents } from '@/components/analytics/analytics-events';
// ✅ Type-safe
services.analytics.track(AnalyticsEvents.BUTTON_CLICK, {
button_id: 'cta',
});
// ❌ Prone to typos
services.analytics.track('button_click', {
button_id: 'cta',
});
```
### 4. Handle Disabled Analytics
The service layer gracefully handles disabled analytics:
```typescript
// When NEXT_PUBLIC_UMAMI_WEBSITE_ID is not set:
// - NoopAnalyticsService is used
// - All calls are safe (no-op)
// - No errors are thrown
const services = getAppServices();
services.analytics.track('event', { prop: 'value' }); // Safe, does nothing
```
## Testing
### Mocking for Tests
```typescript
// __tests__/analytics-mock.ts
export const mockAnalytics = {
track: jest.fn(),
trackPageview: jest.fn(),
};
jest.mock('@/lib/services/create-services', () => ({
getAppServices: () => ({
analytics: mockAnalytics,
}),
}));
// Usage in tests
import { mockAnalytics } from './analytics-mock';
test('tracks button click', () => {
// ... test code ...
expect(mockAnalytics.track).toHaveBeenCalledWith('button_click', {
button_id: 'cta',
});
});
```
### Development Mode
In development, the service layer logs to console:
```bash
# Console output:
[Umami] Tracked event: button_click { button_id: 'cta' }
[Umami] Tracked pageview: /products/123
```
## Error Handling
The service layer includes built-in error handling:
1. **Environment Detection** - Checks for browser environment
2. **Service Availability** - Checks if Umami is loaded
3. **Graceful Degradation** - Falls back to NoopAnalyticsService if needed
```typescript
// These are all safe:
const services = getAppServices();
services.analytics.track('event', { prop: 'value' }); // Works or does nothing
services.analytics.trackPageview('/path'); // Works or does nothing
```
## Performance
### Singleton Pattern
The service layer uses a singleton pattern for performance:
```typescript
// First call creates the singleton
const services1 = getAppServices();
// Subsequent calls return the cached singleton
const services2 = getAppServices();
// services1 === services2 (same instance)
```
### Lazy Initialization
Services are only created when first accessed:
```typescript
// Services are not created until getAppServices() is called
// This keeps initial bundle size minimal
```
## Integration with Components
### Client Components
```typescript
'use client';
import { getAppServices } from '@/lib/services/create-services';
function MyComponent() {
const handleClick = () => {
const services = getAppServices();
services.analytics.track('button_click', { button_id: 'my-button' });
};
return <button onClick={handleClick}>Click Me</button>;
}
```
### Server Components
```typescript
import { getAppServices } from '@/lib/services/create-services';
async function MyServerComponent() {
const services = getAppServices();
// Note: Analytics won't work in server components
// Use client components for analytics tracking
// But you can still access other services like cache
const data = await services.cache.get('key');
return <div>{data}</div>;
}
```
## Troubleshooting
### Analytics Not Working
1. **Check environment variables:**
```bash
echo $NEXT_PUBLIC_UMAMI_WEBSITE_ID
```
2. **Verify service selection:**
```typescript
import { getAppServices } from '@/lib/services/create-services';
const services = getAppServices();
console.log(services.analytics); // Should be UmamiAnalyticsService
```
3. **Check Umami dashboard:**
- Log into Umami
- Verify website ID matches
- Check if data is being received
### Common Issues
| Issue | Solution |
|-------|----------|
| No data in Umami | Check website ID and script URL |
| Events not tracking | Verify service is being used |
| Script not loading | Check network connection, CORS |
| Wrong data | Verify event properties are correct |
## Related Files
- [`components/analytics/useAnalytics.ts`](../components/analytics/useAnalytics.ts) - Custom hook for easy event tracking
- [`components/analytics/analytics-events.ts`](../components/analytics/analytics-events.ts) - Event definitions
- [`components/analytics/UmamiScript.tsx`](../components/analytics/UmamiScript.tsx) - Script loader component
- [`components/analytics/AnalyticsProvider.tsx`](../components/analytics/AnalyticsProvider.tsx) - Route change tracker
- [`lib/services/create-services.ts`](../lib/services/create-services.ts) - Service factory
## Summary
The analytics service layer provides:
-**Type-safe API** - TypeScript throughout
-**Clean abstraction** - Easy to switch analytics providers
-**Graceful degradation** - Safe no-op fallback
-**Comprehensive documentation** - JSDoc comments and examples
-**Performance optimized** - Singleton pattern, lazy initialization
-**Error handling** - Safe in all environments
This layer is the foundation for all analytics tracking in the application.

View File

@@ -1,10 +1,77 @@
/**
* Type definition for analytics event properties.
*
* @example
* ```typescript
* const properties: AnalyticsEventProperties = {
* product_id: '123',
* product_name: 'Cable',
* price: 99.99,
* quantity: 1,
* in_stock: true,
* };
* ```
*/
export type AnalyticsEventProperties = Record<
string,
string | number | boolean | null | undefined
>;
/**
* Interface for analytics service implementations.
*
* This interface defines the contract for all analytics services,
* allowing for different implementations (Umami, Google Analytics, etc.)
* while maintaining a consistent API.
*
* @example
* ```typescript
* // Using the service directly
* const service = new UmamiAnalyticsService({ enabled: true });
* service.track('button_click', { button_id: 'cta' });
* service.trackPageview('/products/123');
* ```
*
* @example
* ```typescript
* // Using the useAnalytics hook (recommended)
* const { trackEvent, trackPageview } = useAnalytics();
* trackEvent('button_click', { button_id: 'cta' });
* trackPageview('/products/123');
* ```
*/
export interface AnalyticsService {
/**
* Track a custom event with optional properties.
*
* @param eventName - The name of the event to track
* @param props - Optional event properties (metadata)
*
* @example
* ```typescript
* track('product_add_to_cart', {
* product_id: '123',
* product_name: 'Cable',
* price: 99.99,
* });
* ```
*/
track(eventName: string, props?: AnalyticsEventProperties): void;
/**
* Track a pageview.
*
* @param url - The URL to track (defaults to current location)
*
* @example
* ```typescript
* // Track current page
* trackPageview();
*
* // Track custom URL
* trackPageview('/products/123?category=cables');
* ```
*/
trackPageview(url?: string): void;
}

View File

@@ -1,11 +1,67 @@
import type { AnalyticsEventProperties, AnalyticsService } from './analytics-service';
/**
* No-op Analytics Service Implementation.
*
* This service implements the AnalyticsService interface but does nothing.
* It's used as a fallback when analytics are disabled or not configured.
*
* @example
* ```typescript
* // Service creation (usually done by create-services.ts)
* const service = new NoopAnalyticsService();
*
* // These calls do nothing but are safe to execute
* service.track('button_click', { button_id: 'cta' });
* service.trackPageview('/products/123');
* ```
*
* @example
* ```typescript
* // Automatic fallback in create-services.ts
* const umamiEnabled = Boolean(process.env.NEXT_PUBLIC_UMAMI_WEBSITE_ID);
* const analytics = umamiEnabled
* ? new UmamiAnalyticsService({ enabled: true })
* : new NoopAnalyticsService(); // Fallback when no website ID
* ```
*/
export class NoopAnalyticsService implements AnalyticsService {
/**
* No-op implementation of track.
*
* This method does nothing but maintains the same signature as other
* analytics services for consistency.
*
* @param _eventName - Event name (ignored)
* @param _props - Event properties (ignored)
*
* @example
* ```typescript
* // Safe to call even when analytics are disabled
* service.track('button_click', { button_id: 'cta' });
* // No error, no action taken
* ```
*/
track(_eventName: string, _props?: AnalyticsEventProperties) {
// intentionally noop
// intentionally noop - analytics are disabled
}
/**
* No-op implementation of trackPageview.
*
* This method does nothing but maintains the same signature as other
* analytics services for consistency.
*
* @param _url - URL to track (ignored)
*
* @example
* ```typescript
* // Safe to call even when analytics are disabled
* service.trackPageview('/products/123');
* // No error, no action taken
* ```
*/
trackPageview(_url?: string) {
// intentionally noop
// intentionally noop - analytics are disabled
}
}

View File

@@ -1,16 +1,74 @@
import type { AnalyticsEventProperties, AnalyticsService } from './analytics-service';
/**
* Type definition for the Umami global object.
*
* This represents the `window.umami` object that the Umami script exposes.
* The `track` function can accept either an event name or a URL.
*/
type UmamiGlobal = {
track?: (eventOrUrl: string, props?: AnalyticsEventProperties) => void;
};
/**
* Configuration options for UmamiAnalyticsService.
*
* @property enabled - Whether analytics are enabled
*/
export type UmamiAnalyticsServiceOptions = {
enabled: boolean;
};
/**
* Umami Analytics Service Implementation.
*
* This service implements the AnalyticsService interface for Umami analytics.
* It provides type-safe event tracking and pageview tracking.
*
* @example
* ```typescript
* // Service creation (usually done by create-services.ts)
* const service = new UmamiAnalyticsService({ enabled: true });
*
* // Track events
* service.track('button_click', { button_id: 'cta' });
* service.trackPageview('/products/123');
* ```
*
* @example
* ```typescript
* // Using through the service layer (recommended)
* import { getAppServices } from '@/lib/services/create-services';
*
* const services = getAppServices();
* services.analytics.track('product_add_to_cart', {
* product_id: '123',
* price: 99.99,
* });
* ```
*/
export class UmamiAnalyticsService implements AnalyticsService {
constructor(private readonly options: UmamiAnalyticsServiceOptions) {}
/**
* Track a custom event with optional properties.
*
* This method checks if analytics are enabled and if we're in a browser environment
* before attempting to track the event.
*
* @param eventName - The name of the event to track
* @param props - Optional event properties
*
* @example
* ```typescript
* service.track('product_add_to_cart', {
* product_id: '123',
* product_name: 'Cable',
* price: 99.99,
* quantity: 1,
* });
* ```
*/
track(eventName: string, props?: AnalyticsEventProperties) {
if (!this.options.enabled) return;
if (typeof window === 'undefined') return;
@@ -19,6 +77,26 @@ export class UmamiAnalyticsService implements AnalyticsService {
umami?.track?.(eventName, props);
}
/**
* Track a pageview.
*
* This method checks if analytics are enabled and if we're in a browser environment
* before attempting to track the pageview.
*
* Umami treats `track(url)` as a pageview override, so we can use the same
* `track` function for both events and pageviews.
*
* @param url - The URL to track (defaults to current location)
*
* @example
* ```typescript
* // Track current page
* service.trackPageview();
*
* // Track custom URL
* service.trackPageview('/products/123?category=cables');
* ```
*/
trackPageview(url?: string) {
if (!this.options.enabled) return;
if (typeof window === 'undefined') return;

View File

@@ -5,22 +5,80 @@ import { MemoryCacheService } from './cache/memory-cache-service';
import { GlitchtipErrorReportingService } from './errors/glitchtip-error-reporting-service';
import { NoopErrorReportingService } from './errors/noop-error-reporting-service';
/**
* Singleton instance of AppServices.
*
* In Next.js, module singletons are per-process (server) and per-tab (client).
* This is sufficient for a small service layer and provides better performance
* than creating new instances on every request.
*
* @private
*/
let singleton: AppServices | undefined;
/**
* Get the application services singleton.
*
* This function creates and caches the application services, including:
* - Analytics service (Umami or no-op)
* - Error reporting service (GlitchTip/Sentry or no-op)
* - Cache service (in-memory)
*
* The services are configured based on environment variables:
* - `NEXT_PUBLIC_UMAMI_WEBSITE_ID` - Enables Umami analytics
* - `NEXT_PUBLIC_SENTRY_DSN` - Enables client-side error reporting
* - `SENTRY_DSN` - Enables server-side error reporting
*
* @returns {AppServices} The application services singleton
*
* @example
* ```typescript
* // Get services in a client component
* import { getAppServices } from '@/lib/services/create-services';
*
* const services = getAppServices();
* services.analytics.track('button_click', { button_id: 'cta' });
* ```
*
* @example
* ```typescript
* // Get services in a server component or API route
* import { getAppServices } from '@/lib/services/create-services';
*
* const services = getAppServices();
* await services.cache.set('key', 'value');
* ```
*
* @example
* ```typescript
* // Automatic service selection based on environment
* // If NEXT_PUBLIC_UMAMI_WEBSITE_ID is set:
* // services.analytics = UmamiAnalyticsService
* // If not set:
* // services.analytics = NoopAnalyticsService (safe no-op)
* ```
*
* @see {@link UmamiAnalyticsService} for analytics implementation
* @see {@link NoopAnalyticsService} for no-op fallback
* @see {@link GlitchtipErrorReportingService} for error reporting
* @see {@link MemoryCacheService} for caching
*/
export function getAppServices(): AppServices {
// In Next.js, module singletons are per-process (server) and per-tab (client).
// This is good enough for a small service layer.
// Return cached instance if available
if (singleton) return singleton;
// Determine which services to enable based on environment variables
const umamiEnabled = Boolean(process.env.NEXT_PUBLIC_UMAMI_WEBSITE_ID);
const sentryClientEnabled = Boolean(process.env.NEXT_PUBLIC_SENTRY_DSN);
const sentryServerEnabled = Boolean(process.env.SENTRY_DSN);
// Create analytics service (Umami or no-op)
const analytics = umamiEnabled
? new UmamiAnalyticsService({ enabled: true })
: new NoopAnalyticsService();
// Enable GlitchTip/Sentry only when a DSN is present for the active runtime.
// Create error reporting service (GlitchTip/Sentry or no-op)
// Server-side and client-side have separate DSNs
const errors =
typeof window === 'undefined'
? sentryServerEnabled
@@ -35,6 +93,7 @@ export function getAppServices(): AppServices {
// Use [`getServerAppServices()`](lib/services/create-services.server.ts:1) on the server.
const cache = new MemoryCacheService();
// Create and cache the singleton
singleton = new AppServices(analytics, errors, cache);
return singleton;
}

7
package-lock.json generated
View File

@@ -30,6 +30,7 @@
"react-dom": "^18.3.1",
"redis": "^4.7.1",
"resend": "^3.5.0",
"schema-dts": "^1.1.5",
"sharp": "^0.34.5",
"svg-to-pdfkit": "^0.1.8",
"tailwind-merge": "^3.4.0",
@@ -13148,6 +13149,12 @@
"loose-envify": "^1.1.0"
}
},
"node_modules/schema-dts": {
"version": "1.1.5",
"resolved": "https://registry.npmjs.org/schema-dts/-/schema-dts-1.1.5.tgz",
"integrity": "sha512-RJr9EaCmsLzBX2NDiO5Z3ux2BVosNZN5jo0gWgsyKvxKIUL5R3swNvoorulAeL9kLB0iTSX7V6aokhla2m7xbg==",
"license": "Apache-2.0"
},
"node_modules/schema-utils": {
"version": "4.3.3",
"resolved": "https://registry.npmjs.org/schema-utils/-/schema-utils-4.3.3.tgz",

View File

@@ -22,6 +22,7 @@
"react-dom": "^18.3.1",
"redis": "^4.7.1",
"resend": "^3.5.0",
"schema-dts": "^1.1.5",
"sharp": "^0.34.5",
"svg-to-pdfkit": "^0.1.8",
"tailwind-merge": "^3.4.0",

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Some files were not shown because too many files have changed in this diff Show More