The runtime CDN (cdn.tailwindcss.com) is not production-grade: FOUC, no
purging, and an external request that is slow/blocked from some networks.
- Add Tailwind v3 build (package.json `npm run build`) with two scoped configs:
public (accent + zinc) -> wwwroot/css/tailwind.css, and admin (dark base/
electric/violet/emerald, separate to avoid the emerald flat-vs-scale clash)
-> wwwroot/css/tailwind-admin.css. Both minified + content-purged.
- Layouts now link the built CSS instead of the CDN script; built artifacts
are committed so Docker/CI need no Node step. node_modules stays ignored.
- Verified: utilities (incl. arbitrary values like aspect-[16/9], grid-cols-
[8rem_1fr]) resolve; public + admin render; no console errors.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Full rewrite of the portfolio site from Next.js 14 to .NET 10:
- ASP.NET Core 10 Razor Pages, no Node.js dependency
- EF Core 10 + SQLite (same schema as before — data survives upgrade)
- Cookie authentication (same single-password model)
- Resend contact form via HttpClient
- Bilingual FA/EN via locale cookie + BasePageModel
- All UI ported to Razor Pages with Tailwind CDN + custom CSS
- Vanilla JS: particles, typewriter, cursor, animations, portfolio modal
- Dockerfile: SDK 10.0-alpine → aspnet 10.0-alpine (no npm/Node needed)
- CI/CD: dropped NPM_TOKEN, ADMIN_SESSION_SECRET — pure dotnet publish
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
soroush.asadi