Why a CMS?

I used to develop my portfolio from scratch, but after a while I decided that I’d much rather put my energy toward projects that inspire a zest for life! It’s way too easy to stress out over the way to present yourself, so instead I chose a CMS that provides a lot of flexibility in a pinch so I can experiment easily. Truth be told, there are a lot of places where the alignments or code restrictions drive me absolutely nuts! Maybe that will finally push me into developing my own again.

A lot of portfolios I’ve run across for quite a while now use a tiled image system, where you have to click into an image to even see what’s going on with it. The design system I’m using is older, but takes into consideration a limited amount of time and lets you quickly scroll through to get the gist. What do you think works best?

Gettin' Started!

So, why add a “blog” section?

Designers all do different things for a variety of reasons, which is why it’s a great idea to include process work in a portfolio. The natural extension of that is to have some form of general thoughts that are less project specific for the more studious hiring managers to dig into. Also compared to most portfolios I’ve seen, mine may be toeing the line of content overload (something I’m continuously working to balance) and it’s definitely worth it to keep additional thoughts out of the way of the skimmers out there. It’s just another tiny step toward getting my portfolio to more actively reflect my thought patterns and what it’d be like to work with me. Welcome!