Portfolio Site — 2026 Rebuild
A site bringing my work together in one place. My previous portfolio needed a code change for every new project; this one is updated from an admin screen.
Overview
A portfolio site bringing my work together in one place. I rebuilt my previous site from scratch and handled all of it myself — planning, design, the frontend build, and the CMS architecture. About 15 days from start to finish. On the old site, adding a single project meant writing the data into the code and pushing to GitHub before anything appeared. This version has a Sanity admin screen where projects are added and edited directly. Content and presentation are separated, so the site can keep growing without touching the implementation. The Japanese and English versions are not translations of one another. The people reading them are looking for different things, so each is written on its own.
Points
- Adding a project no longer means touching code. The old site needed a data edit and a push; this one uses Sanity, so work is added and edited from an admin screen. Separating content from the implementation keeps the site easy to run as it grows
- Early on I tried to work out the visual direction together with AI, but the closer I followed its suggestions, the more generic and AI-made it looked, and the direction never settled. I scrapped it, researched sites whose style I wanted to learn from, and drew the wireframes myself in Figma. Deciding the direction first and then bringing AI in as an implementation partner got the main structure built in about a week
- Rebuilding from scratch let me look at the architecture from the very start — where each component sits, and how much any one of them should be responsible for. How easy something is to extend later is mostly decided right there
