Refactor next.config.ts for custom domain setup, removing basePath and assetPrefix. Update package.json to add production build and serve scripts. Clean up deploy.yml by removing unnecessary CNAME configuration.

Author: vukrosic

.github/workflows/deploy.yml

@@ -33,5 +33,4 @@ jobs:
       if: github.ref == 'refs/heads/main'
       with:
         github_token: ${{ secrets.GITHUB_TOKEN }}
-        publish_dir: ./out
-        cname: open-superintelligence-lab.github.io
+        publish_dir: ./out

DEPLOYMENT.md

@@ -0,0 +1,64 @@
+# GitHub Pages Deployment Guide
+
+This Next.js app is configured for deployment to GitHub Pages at `https://open-superintelligence-lab.github.io/Open-Superintelligence-Lab.github.io/`.
+
+## ✅ What's Fixed
+
+1. **Base Path Configuration**: Updated `next.config.ts` with correct `basePath` and `assetPrefix`
+2. **Tailwind CSS**: Verified content paths include `./app/**/*.{js,ts,jsx,tsx,mdx}`
+3. **GitHub Actions**: Created automatic deployment workflow
+4. **Build Process**: Fixed Turbopack issues and PostCSS configuration
+
+## 🚀 Deployment Methods
+
+### Method 1: Automatic (Recommended)
+The GitHub Actions workflow will automatically deploy when you push to the `main` branch:
+
+1. Push your changes to `main`
+2. The workflow will build and deploy automatically
+3. Your site will be available at: `https://open-superintelligence-lab.github.io/Open-Superintelligence-Lab.github.io/`
+
+### Method 2: Manual Deployment
+```bash
+# Build for production
+npm run build:prod
+
+# Serve locally to test
+npm run serve:out
+
+# The built files are in the `out/` directory
+# Push the contents of `out/` to your `gh-pages` branch
+```
+
+## 🔧 Local Testing
+
+To test the production build locally:
+
+```bash
+# Build with production settings
+npm run build:prod
+
+# Serve the built files
+npm run serve:out
+```
+
+## 📁 Key Files
+
+- `next.config.ts` - Contains basePath and assetPrefix configuration
+- `.github/workflows/deploy.yml` - GitHub Actions deployment workflow
+- `tailwind.config.js` - Tailwind CSS configuration with correct content paths
+- `postcss.config.mjs` - PostCSS configuration for CSS processing
+
+## 🐛 Troubleshooting
+
+If CSS is missing on GitHub Pages:
+
+1. ✅ Check `basePath` matches your repo name exactly
+2. ✅ Verify `assetPrefix` has trailing slash
+3. ✅ Ensure Tailwind content paths include all your component directories
+4. ✅ Make sure you're deploying the `out/` folder, not `.next/`
+
+## 🌐 Your Site URL
+
+Once deployed, your site will be available at:
+`https://open-superintelligence-lab.github.io/Open-Superintelligence-Lab.github.io/`

next.config.ts

@@ -6,9 +6,8 @@ const nextConfig: NextConfig = {
   images: {
     unoptimized: true
   },
-  // GitHub Pages configuration
-  basePath: process.env.NODE_ENV === 'production' ? '/Open-Superintelligence-Lab.github.io' : '',
-  assetPrefix: process.env.NODE_ENV === 'production' ? '/Open-Superintelligence-Lab.github.io/' : '',
+  // Custom domain configuration (opensuperintelligencelab.com)
+  // No basePath needed for custom domain
   distDir: 'out',
 };
 

package.json

@@ -7,7 +7,9 @@
     "build": "next build",
     "start": "next start",
     "lint": "eslint",
-    "export": "next build && next export"
+    "export": "next build && next export",
+    "build:prod": "NODE_ENV=production npm run build",
+    "serve:out": "npx serve out"
   },
   "dependencies": {
     "react": "19.1.0",