replace next-sitemap with custom sitemap using translation registry

Author: pettinarip

.github/labeler.yml

@@ -17,7 +17,6 @@
 "config ⚙️":
   - i18n.config.json
   - next.config.js
-  - next-sitemap.config.js
   - tsconfig.json
   - .nvmrc
   - .eslintignore

CLAUDE.md

@@ -137,7 +137,7 @@ pnpm events-import         # Import community events
 
 ## SEO & Meta
 
-- Sitemap generation with `next-sitemap`
+- Sitemap generation in `app/sitemap.ts`
 - Meta tags and Open Graph optimization
 - Structured data for search engines
 - Security headers (X-Frame-Options: DENY)
@@ -210,26 +210,28 @@ The site uses a GDPR-compliant, cookie-less A/B testing system integrated with M
 ### Adding a New A/B Test
 
 1. **Create experiment in Matomo dashboard**:
+
    - Go to Experiments → Manage Experiments
    - Create new experiment with desired name (e.g., "HomepageHero")
    - Add variations with weights (original is implicit)
    - Set status to "running"
 
 2. **Implement in component**:
+
    ```tsx
    import ABTestWrapper from "@/components/AB/TestWrapper"
-   
-   <ABTestWrapper
-     testKey="HomepageHero"  // Must match Matomo experiment name exactly
+   ;<ABTestWrapper
+     testKey="HomepageHero" // Must match Matomo experiment name exactly
      variants={[
-       <OriginalComponent key="current-hero" />,     // Index 0: Original
-       <NewComponent key="redesigned-hero" />        // Index 1: Variation
+       <OriginalComponent key="current-hero" />, // Index 0: Original
+       <NewComponent key="redesigned-hero" />, // Index 1: Variation
      ]}
      fallback={<OriginalComponent />}
    />
    ```
 
 **Important**:
+
 - Variants matched by **array index**, not names
 - Array order must match Matomo experiment order exactly
 - JSX `key` props become debug panel labels: `"redesigned-hero"` → `"Redesigned Hero"`
@@ -244,6 +246,7 @@ The site uses a GDPR-compliant, cookie-less A/B testing system integrated with M
 ### Environment Variables
 
 Required for Matomo integration:
+
 - `NEXT_PUBLIC_MATOMO_URL` - Matomo instance URL
 - `NEXT_PUBLIC_MATOMO_SITE_ID` - Site ID in Matomo
 - `MATOMO_API_TOKEN` - API token with experiments access

app/sitemap.ts

@@ -0,0 +1,41 @@
+import type { MetadataRoute } from "next"
+
+import { getFullUrl } from "@/lib/utils/url"
+
+import { DEFAULT_LOCALE } from "@/lib/constants"
+
+import { getAllPagesWithTranslations } from "@/lib/i18n/translationRegistry"
+
+export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
+  const pages = await getAllPagesWithTranslations()
+
+  const entries: MetadataRoute.Sitemap = []
+
+  for (const { slug, translatedLocales } of pages) {
+    const normalizedSlug = slug.startsWith("/") ? slug : `/${slug}`
+
+    for (const locale of translatedLocales) {
+      const url = getFullUrl(locale, normalizedSlug)
+
+      // Drop the `/en` root entry to avoid duplicating `/`
+      // This happens when slug is "/" and locale is default
+      if (
+        locale === DEFAULT_LOCALE &&
+        (normalizedSlug === "/" || normalizedSlug === "")
+      ) {
+        continue
+      }
+
+      const isDefaultLocale = locale === DEFAULT_LOCALE
+
+      entries.push({
+        url,
+        changeFrequency: isDefaultLocale ? "weekly" : "monthly",
+        priority: isDefaultLocale ? 0.7 : 0.5,
+        lastModified: new Date(),
+      })
+    }
+  }
+
+  return entries
+}

next-sitemap.config.js

@@ -6,7 +6,6 @@
   "scripts": {
     "dev": "next dev",
     "build": "next build",
-    "postbuild": "next-sitemap",
     "start": "next start",
     "lint": "next lint",
     "lint:fix": "next lint --fix",
@@ -82,7 +81,6 @@
     "next": "^14.2.32",
     "next-intl": "^3.26.3",
     "next-mdx-remote": "^5.0.0",
-    "next-sitemap": "^4.2.3",
     "next-themes": "^0.3.0",
     "prism-react-renderer": "1.1.0",
     "prismjs": "^1.30.0",