Unlayered CSS always wins over Tailwind's @layer utilities, so the
bare * { margin: 0 } reset was overriding mx-auto everywhere. Moving
it into @layer base restores correct cascade order.
1.7 KiB
1.7 KiB
lerko96 portfolio
Personal portfolio site. Live at lerkolabs.com — self-hosted, deployed and maintained through my own operation.
Source lives on my Gitea at gitea.lerkolabs.com. GitHub is a backup mirror, not the primary.
Stack: Next.js 16 · React 19 · TypeScript · Tailwind v4
Branches
dev— source code, all work happens heremaster— built output only; what GitHub Pages serves for the backup mirror. don't touch this manually.
Commands
npm run dev # dev server at localhost:3000
npm run build # static export into out/
npm run deploy # build + push out/ to master (GitHub mirror)
How it deploys
npm run deploy runs predeploy (build) then pushes the out/ directory to master via gh-pages. That's what feeds the GitHub Pages backup mirror.
postbuild drops out/.nojekyll so GitHub Pages doesn't ignore _next/ assets.
Project layout
src/
app/
layout.tsx # root layout, fonts, ThemeProvider
page.tsx # home: hero, skills, project cards
homelab/page.tsx # homelab page: VLANs, services, ADRs
archive/page.tsx # older projects grid
globals.css # full design system (Tailwind v4 CSS-first, all tokens here)
components/ # Nav, Footer, Hero, ThemeScript, etc.
context/
ThemeContext.tsx # dark mode provider + useTheme hook
data/
projects.ts # all projects, featured + archive split
services.ts # homelab services with categories
public/ # static assets copied into out/ on build
Tailwind v4 is CSS-first — no
tailwind.config.ts. All custom tokens live inglobals.cssunder@theme {}.