How I Built My Own Portfolio Website with Next.js, Tailwind CSS, and Codex

When I decided to build my own portfolio website, I did not want it to feel like a generic template with a name, a job title, and a few links. I wanted something that actually reflected how I work. I wanted one place where I could showcase my projects, technical documentation, resume, and the kind of IT and systems work I enjoy doing. I also wanted the website itself to become part of the portfolio instead of just being a container for it. If someone visited it, I wanted them to see not only what I have done, but also how I think about organization, layout, iteration, and polish. If you want to see the finished result, you can view my portfolio here: dev.hunterryskoski.com Why I Chose to Build It Myself A lot of portfolio sites feel interchangeable. They look fine, but they do not really say much about the person behind them. I wanted mine to feel more personal and more practical. My work has continued to grow across documentation, endpoint management, reporting, and project write-ups,