Portfolio

Why?

I made my first two portfolios/personal sites very early in my programming career. I made the first one right after I graduated college. It was a very basic site using plain HTML/CSS/JS. I took the knowledge I learned from my web development specialization and made it in about a week. The site had a little bit of information about me and my accomplishments in college. It helped me land my first job. The second version of my portfolio was a complete overhaul using Gatsby. I was starting to figure out React and decided to re-do my portfolio for practice. I remember at the time I thought it was so amazing but looking back at it now I can see how much I’ve grown as a developer. The site had very little information about me and links to my projects.

Introducing: Version 3.0

The site that you’re currently on is the latest version! With over a year of experience, I’ve learned so much about SDLC (Software Development Lifecycle) and decided to take this version quite seriously.

Design

I decided to use Figma to create the designs. One of the designers I work with uses Figma when sending me wireframes and I’ve grown to enjoy using the software. It allows me to design components and reuse them throughout my project. It really allowed me to “think in React” straight from the design phase. I had a few different mockups but in the end I decided that I wanted something simple that would speak for itself. For now, the project would be a collection of my work that would link out to a page that further describes the project, similar to a blog.

Build

I decided to use NextJS for this project as SEO and server-side rendering were a must. NextJS is a React framework that offers server-side rendering and easy SEO implementation (along with a lot of other things) for React applications. It let me focus on everything but configuration. Trust me, you have to try out NextJS, it will change your life! I also decided to ditch stylesheets and move onto styled-components. I can confidently say that I love style-components and plan on using it much more in the future. No more class name bugs, very easy conditional styles, themes, and so much more. Aside from that, the site also has a dynamic project page, no class based components/lifecycle methods, and server-side rendering. I thoroughly enjoyed coding this small project and plan on using this tech stack much more in the future. Thanks for checking out my site!

View on Github

|

Home