ericjokl.com
The site itself is a work sample: strict TypeScript, no suppressed build errors, and structured content driven from one typed source.
- My role
- Designed and built it, including everything you are looking at.
- Stack
- Next.jsReact 19TypeScript (strict)Tailwind CSS v4Framer Motion
The problem
A portfolio that talks about engineering standards while quietly disabling its own type checking is arguing against itself.
What I built
A Next.js App Router site where every project is described in one typed data module and rendered from it, so no claim exists in two places and drifts. Build errors are not suppressed, images are optimised, canonical host and HTTPS are enforced at the edge, and the rendering is server-side by default.
The hard part
Restraint. The previous version shipped a full Three.js city scene on the homepage. It was fun to build and it cost real load time to prove nothing. Removing it was the right engineering decision and the harder one.
Evidence
- SourceRestrictedThe repository for this site is private. Happy to walk through any part of it.
- The site itselfOpen dev tools. The console is clean and the markup is semantic.
Questions about how this was built, or want something like it?