Rebuilding My Portfolio Website from Scratch

I have decided to omit the detailed implementations of the website as you can easily find them in my GitHub, and the process had been a more important experience to me compared to the actual coding.

By the way, here's the website.

UI Design

This has often been my weak spot in developing the front-end unless there has been an established design system.

References

Being a typical programmer, I explored a lot of other sites for references, this includes portfolio pages from designers, studios and programmers. These few were my favorites, and I’m sure you have seen some of them as they are always used as examples of good websites:

1. Diegovz’s and Kuon Yagi’s had been my references since the second version, I did take some minor references this time.

   

   

2. I watched quite some Design Course’s videos to fill up my UI knowledge, and those certainly brought some inspiration to me, especially his UI Review/Redesign series!

3. Finally, I have decided to take Brittany Chiang’s website as my main reference as it happened to be many’s favorites, so you can see the overall theme and feel that resembled hers a lot.

   

Theme and Color

Referring to Brittany’s website, I knew that I was going to have a dark theme website (I dislike light themes anyways), but diving into the design, I needed to figure out the theme colors.

I know I know, design with black and white first to focus on spacing, etc., but I didn’t plan to spend too long over designing, so nah

Blue — The professional color, but I felt like it’s been a bit overused these days (totally subjective)

Red, Green, and Yellow — On the Rarer side, but they often represent some signals, and I wanted to avoid that. I also skipped turquoise so that my website does not look the same as Brittany’s.

What other colors are there? I looked at the rainbow 🌈, and right away, violet came into my eyes.

Violet — Pretty unique, huh? Not as striking as pink, not as enthusiastic as orange, kinda premium, and they said it’s a sign of wisdom. That’s it, purple!

I then took the base variants of my purple from Tailwinds 😆 (with some adjustments, of course)

Logo

Settling the theme color means that I can come up with my logo!

Since I wasn’t good at art, I decided to just use the “S” of my name, but how should the S look like?

This time, I was inspired by one of the developers I looked up to, Prometheus’ blog logo, I wanted a flame of S too. A purple flame that looks like S!

I started to google for some samples, opened up my good o’ Inkscape and doodled out this logo. (I remember referring to some images, but couldn’t find them anymore 😞)

Prototyping

Finally, it’s time for Figma! 🎨

Combining the references, some tips from here and there, as well as some of my touches, here it goes

A very rough design, as I decided to touch up when I code, oh and I only included the hero section here

Some other considerations and references I made here are:

1. Using some background watermarks to make my hero section less empty

2. I saw quite a few places advising to put a face on Hero section, and I wanted to make it less formal, so yeah a funny me should drop from the side

3. I really like PocketBase’s Gopher interaction, so I copied over the interaction

   

4. I also wanted to dedicate a full section to my skills and tools used

Phew, finally done with designing, I think it took me about a week or two of on’s and off’s for this whole process.

Admittedly, this isn’t been the best design, but I’m pretty satisfied with what I have 😍

Development

So, here’s the real part, again, I won’t dive into the nitty-gritty of coding, but here’s a general overview of it.

Techs and Frameworks

I built my previous version with Vue + Nuxt, pretty neat, but I didn’t like Vuetify as much now due to its heavy presets, and I had the best experience with Chakra UI now, so my final decision is:

React + Next.js + Chakra UI

I avoided vanilla React since it has many issues and Next.js is awesome!

Aside from those, I also added Typescript to showcase my knowledge since Javascript is simply incomplete without types. Likewise, I added support for Sass for a better development experience.

Finally, I figured out that I needed a store for my modals since we all know that useContext is bad, and I preferred Zustand over Redux due to its simpler interface (and who doesn't like bear? 🐻).

Animations

To make the website more interactive and livelier, I introduced several animations into it.

Coding plain animation in CSS is really tedious, especially the part of managing a never-ending list of classes, so I resorted to using Framer Motion due to its simplicity.

The primary types of animations were scroll-triggered, which can be done easily through Framer Motion’s whileInView props, and so I defined a list of fade-in animations for this purpose.

Yeah, I’m aware of the Animate On Scroll library, but I don’t feel like using it.

One of the best parts of Framer Motion was the ability to trigger the animation programmatically and the Spring transition, both of which have been used on my website.

Lastly, I also used Lottie for some quick and nice animation.

Page Content

In the second version, the content was stored separately in each component, which made it hard to modify (not exactly hard, but kinda tedious to find where are the values), so I dedicated a folder for the contents of each section & page.

This has made my life much easier to insert and edit any text on my website!

Clean Codes

Finally, I also made some effort into ensuring the cleanliness of the codes, so that they can be maintained and updated easily.

Here are some principles / decisions I took:

1. The use of Barrel Files (The index.ts to import and re-export everything from the same folder) — Just an experiment by myself in using this structure, and I kinda enjoy it since it simplifies my imports

2. Small Components — I also tried my best to minimize the number of lines in a component for readability, and I managed to keep most components within 50 - 100 lines!

3. Minimize Repetition — I didn’t want my codes to be long and ugly, so I added some wrapper components & utility functions, like ImgurImage, one of my favorite components I wrote

   

Summary

This has been an amazing experience 🤩 I certainly recommend every starting programmer build something fully on their own. The feeling of developing something from scratch is different from developing on top of an existing program.