chore(umami): commit the 6 umami-removal edits left dirty after the earlier reset

These landing/legal/shared-utils edits are part of the umami decommission
(Umami → no-op / 'kein Web-Analytics', dated 2026-05-26) but were left
uncommitted in the working tree after the concurrent git-reset incident.
Pure rewording — no behaviour change, tracking was already dead.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Till JS 2026-05-26 16:16:20 +02:00
parent bffb5be345
commit 5f5287d0e9
6 changed files with 19 additions and 24 deletions

View file

@ -26,5 +26,5 @@ export * from './cache';
// Natural Language Parsers
export * from './parsers';
// Umami Analytics
// Event-API (No-op — Web-Analytics entfernt 2026-05-26)
export * from './analytics';

View file

@ -1,8 +1,10 @@
/**
* Web Vitals Umami Integration
* Web Vitals tracking
*
* Tracks Core Web Vitals (LCP, CLS, INP) and additional metrics (FCP, TTFB)
* as Umami events. Call `trackWebVitals()` once on app startup.
* Misst Core Web Vitals (LCP, CLS, INP) + FCP/TTFB und reicht sie an die
* `trackEvent`-API weiter. Hinweis: Web-Analytics-Versand ist entfernt
* (2026-05-26) die Werte gehen aktuell in einen No-op.
* Call `trackWebVitals()` once on app startup.
*
* @example
* ```typescript