May 2026
Personal Portfolio Website
A self-hosted portfolio built with Next.js, Drizzle, and a Neon Postgres database, deployed with Dokploy on my own server. The site you are looking at right now.
Challenges
Going from empty repo to a finished portfolio meant lots of design iteration. Picking the right palette and font, getting the project taxonomy down to filters that actually help a recruiter, finding real images for every project, and writing all the project copy in a voice that sounds like me. Each pass made it cleaner.
Skills used
- Next.js
- Postgres and Drizzle
- Tailwind CSS 4
- TypeScript
- Authentication
- Docker and server deployment
- Claude Code
- Information architecture
- Visual design
Current status
Version 2 went live on kaanazaklioglu.com on 2026-11-01. It replaced the first Astro version, which is kept at the git tag v1-astro.
Brief
The site you are looking at. A self-hosted portfolio that collects every project I have built and every season I have spent in robotics into one place. The brief was my own. I wanted something I could show to colleges, recruiters, and friends, that loaded fast, looked distinctive, and made my work easy to scan.
Process
Stack. Version 2 is a Next.js app with TypeScript, Drizzle, Better Auth, and a Neon Postgres database. It is deployed with Dokploy and Traefik on the same Hostinger server that runs my other projects, and a push to the main branch redeploys it. Version 1 was Astro 5, a static site on a shared Plesk host. It is kept at the git tag v1-astro. I moved to Next.js with a database so I could update the site from a browser instead of with a commit.
Architecture. Projects, robotics seasons, and competition results live in the database. The public pages read from it through a cache, and the admin page writes to it. Version 1 kept every project as a Markdown file in the repository, which meant every change was a commit and a build.
Iteration cycles. This was the most-iterated project I have built. Color palette started as Solar Forge amber-gold, went through a Fraunces editorial serif phase, and ended on the current Anton condensed industrial direction with brass-gold accent. Fonts cycled from Inter to Space Grotesk to Newsreader to Fraunces to Audiowide to the current Anton plus JetBrains Mono pair. Each pass dropped something and committed harder to a single visual direction.
Filters. The /projects page has a filter system that was redesigned three times. First version had every granular tag as a filter button. Too noisy. Second version had six focus areas. Still too many. Final version has two filters (Hardware and Software) plus a granular tag chip system on each card that surfaces specific techniques (CAD, Onshape, Arduino, woodworking) without being filterable. The split between filter granularity and card detail granularity is the single biggest UX improvement on the site.
Accessibility pass. A full a11y review covering keyboard focus rings, prefers-reduced-motion, skip-to-content link, aria-current on nav, descriptive link labels on cards (so screen readers do not read every card’s contents as one giant link name), and a contrast bump on muted text. The accessibility work is invisible in screenshots but it is the difference between a portfolio that works for everyone and one that does not.
Voice. Every project’s copy went through a rewrite to sound like me, not like a press release. The robotics page especially got a team-player rewrite so the achievements read as the team’s wins, not as mine.
Skills built
- Next.js and a real database. Moving a content site from Markdown files to Postgres, with typed queries through Drizzle and a cached public side. Version 1 taught me Astro end to end first, which made the move easier to plan.
- Tailwind CSS 4. New @theme syntax, CSS variable theming, the Vite plugin, utility composition. Comfortable using Tailwind for fast visual iteration without it becoming a maintenance problem.
- Typed content. Zod schemas validate every project and result before it is written, so a missing image URL or a wrong value gets caught before it reaches the page. Competition facts are migrated by script so they cannot be mistyped.
- Information architecture. Deciding what goes on the homepage versus the projects page versus the project detail page. What surfaces and what hides until clicked.
- Visual design discipline. Picking one aesthetic direction and committing instead of mashing influences. The Anton condensed industrial direction is intentional and applied across every page consistently.
- Accessibility engineering. WCAG-aligned focus, motion, and labeling. Not optional. Default.
- Claude Code as a coding partner. Same workflow I used on the Cup Pong firmware and the trading bot. Describe the goal, review the output, iterate. The site exists because the iteration loop with Claude Code lets me try ideas faster than I could implement them solo from scratch.
Where it stands
- Version 2 is live on kaanazaklioglu.com since 2026-11-01. The domain’s DNS still runs on the old Plesk host, and moving it to the registrar is the last step of the cutover.
- Real project photos. Most images are stock right now. Swapping them for my actual project shots is the biggest content task left.
- Resume PDF generation and linking from the About page.
- A final copy pass to catch anything that still sounds like a robot wrote it.
Why this is on the site
A portfolio that lists a portfolio site as one of its projects is a slightly recursive move. It is on here because building the site itself was the biggest software project I have done so far. Every decision (palette, type, filter taxonomy, accessibility, voice) is documented in the commit history and visible in the result. The site is its own case study.