Portfolio

Context
This is the fifth version of this site. The first one went up early in university with almost nothing on it, and this one is being built at the end of that degree with four rebuilds behind it. Not one of them was replaced because it had broken.
The early problem was skill. I could tell the difference between a design I liked and one I did not, and my taste was running some way ahead of what I could actually build. The later versions got closer to something I wanted to look at, and the lessons moved on to accessibility, structure, consistency, and whether any of it held up on a phone.
The version before this one is the first I have been properly happy with. It shows my work, it says who I am, and it does both clearly. It just never felt special, and that is what kept gnawing at me until I started again.
Details
- Role
- Designer and Developer
- Team
- Solo
- Timeline
- 2024 — present
- Deliverables
- This finished portfolio site
- Status
- Complete, at yurikorolev.com
Final artifacts


Key design moments
It sat there for seventeen months with nothing on it
The first version was hand written HTML with a turquoise rule under every heading, and it stayed exactly as it was for seventeen months. The one project on it, a Connect4 game, got commented out at some point and replaced with the word WIP. Three of the four links in the nav pointed nowhere. None of that was a coding problem. I had nothing worth showing yet and I was putting my time into the wrong parts of the thing, and because my taste was improving faster than my skills were, I could see clearly that what I had was not good enough to put in front of anyone. So I did not put it in front of anyone. I left it alone and I did not share it for a very long time.

Nobody could work out how to use it
The next version borrowed a navigation idea I had liked on another site. You clicked and dragged the heading on the hero and a carousel of projects opened under it. I was pleased enough with it to send it round to friends, and most of them either could not work out how to move through it or found it behaved badly on whatever they were holding. I had not thought about any of that while I was building it. The commit history for that version is mostly me going back and patching it afterwards: keyboard support, a hold and drag gesture because a plain tap kept firing by accident on phones, a contact form that stopped being usable the second a mobile keyboard opened over it. Accessibility is not a pass you make once the interesting part is finished.

Trying to copy a site I loved
After that I started again on something modelled very closely on ning-h.com. I liked that site enormously, and what I was really doing was rebuilding it and calling it mine. I never got it to the same standard, and the nearer it got the more obvious it was that the parts I liked best were not my ideas. It lasted sixteen days and it never went live on my domain. I would still do it again. Working through somebody else's decisions taught me more than reading about them would have, as long as the copy is not the thing you end up shipping.

Impact
This version starts from an open source WebGL ring rather than an empty folder. I made it work on a phone, built the plain view beside it so that anyone who has asked their system for less motion or whose machine cannot start WebGL gets the same twelve projects as a list, and shaped the rest of it around my own work. There is no number at the end of a personal site that means very much. The measure is whether it was worth the visit and whether you came away knowing what I make, and that is a question for whoever is reading this rather than for me.
Reflections
Accessibility matters as much as the design and the content do. Somebody arriving should have to think as little as possible about how the page works, and it should hold up on whatever they happen to be holding, both in how it performs and in whether they can use it at all. Pushing at what a layout or a navigation can be is fine. Making a visitor solve it is not.
The other half of it is being happy with the thing myself. A site can work perfectly well and still eat away at me until I rebuild it, which is most of the story above. It can also be good looking and barely usable, or usable and completely forgettable. I am fairly sure this version does not show my projects in the most direct way it could, and there is less about me on it than there was on the last one. I would rather have that problem than the one I had before, and I would not bet against a sixth version.