fix: Use skipTrailingSlashRedirect to stop Next.js from stripping trailing slashes

Author: GeneAI

website/next.config.ts

@@ -4,32 +4,13 @@ import path from "path";
 const nextConfig: NextConfig = {
   output: 'standalone',
   outputFileTracingRoot: path.join(__dirname, './'),
-  trailingSlash: true,  // Ensure trailing slashes for correct relative path resolution
+  skipTrailingSlashRedirect: true,  // Don't auto-redirect trailing slashes - let middleware handle it
   eslint: {
     // Only run ESLint on these directories during production builds
     dirs: ['app'],
     // Ignore ESLint errors during production builds
     ignoreDuringBuilds: true,
   },
-  async redirects() {
-    return [
-      // Redirect framework-docs paths without trailing slash to include trailing slash
-      {
-        source: '/framework-docs/:path((?!.*\\.).+)',
-        destination: '/framework-docs/:path/',
-        permanent: true,
-      },
-    ];
-  },
-  async rewrites() {
-    return [
-      // Serve index.html for framework-docs directory requests
-      {
-        source: '/framework-docs/:path*/',
-        destination: '/framework-docs/:path*/index.html',
-      },
-    ];
-  },
 };
 
 export default nextConfig;

website/vercel.json

@@ -1,6 +1,4 @@
 {
-  "trailingSlash": true,
-  "cleanUrls": false,
   "headers": [
     {
       "source": "/framework-docs/(.*)",