The short version
- 01
CK Dev did not start as a serious portfolio plan. It was mostly a place for me to practice CSS, build small visual ideas with basic elements, and see how far I could push the frontend skills I had at the time.
- 02
I kept coming back with another theme, animation, interaction, or layout idea and trying to blend it into whatever was already there. Eventually that constant cycle became the identity of the site, so I turned it into my portfolio instead of forcing myself to choose one permanent style.
- 03
It is dated now, but I still like what it represents. The site captured the point where I stopped treating frontend work as only arranging components and started using it as a creative medium.
The problem
I needed somewhere to practice visual development and eventually somewhere to show the projects I was building.
A normal template portfolio would have been faster, but it would not have taught me as much or reflected how exploratory my work felt at the time.
What I built
- Custom portfolio layout
- Multiple visual themes and transitions
- Project showcase sections
- Animated interface experiments
- Responsive frontend styling
Design decisions
Instead of hiding my indecisiveness around one theme, I turned the movement between different styles into part of the experience.
The site was intentionally more expressive than practical. It was a place to test ideas first and a professional portfolio second.
Technical decisions
The code grew organically alongside the visual experiments. That made it useful for learning, but it also meant the structure became harder to maintain as each new idea was layered onto the last one.
Challenges
The hardest part was keeping all of the visual ideas connected enough that the site still felt intentional.
I also learned that adding another interaction is much easier than deciding whether it actually improves navigation, performance, or the way someone understands the work.
The outcome
CK Dev became my first real portfolio and gave me a place to show work before I had a polished professional identity.
More importantly, it helped me learn what kind of designer and developer I wanted to become, even if the current CK Works site now presents that work in a calmer and more focused way.
What I'd improve next
I would not rebuild the same site now. I would preserve a few of the strongest experiments as an archive and let the main portfolio stay simpler, faster, and more centered on the work itself.
Let's Talk
Want something like this for your business?
Whether it's a website, a system, or an idea that still feels a little messy, I can help you figure out what makes sense next.