Why? I built it for myself. Not for what I thought recruiters/employers wanted to see. I simply wanted a place to collect some of the projects I work on. And more importantly one that captured my personality a bit. It's not perfect, I look at it and see a ton things I'd refactor. But it get's people to laugh or start a conversation about something I've done. That to me makes it all worth it.
My $0.02: Don't build a portfolio site because you think you need one, build one if it serves a purpose for you. i.e. learning a new skill, organizing your work, or just having fun. I think the results are much more interesting that way. (Also, don't be afraid to iterate. I think this is the 5th one I've attempted to make)
Nice and clean. I like it. There are so many fancy sites and bootstraps but finally in the end, if you have coded it and it can last next 10 years without a major change to the site design and you can focus on adding content to the site. That's a win.
That's what I was going to suggest. If you're a non-coder who needs a portfolio site, you already have a body of work ready to show. Put that up on a Squarespace site with a nice template instead of wasting time going through HTML/CSS video courses to create one from scratch.
If you're genuinely interested in building from the ground up, definitely go ahead. But if that's not really your goal, you will almost certainly be disappointed with your first site. HTML/CSS courses don't cover design (typography, element spacing, color palettes), so you'll look at your site, you'll know it's ugly but you won't know why. And you won't want to put it online, thereby wasting even more time.
Don't do that. Let your work speak for you, and don't feel embarrassed about using a template. Your audience cares about the quality of your content only, they will be completely oblivious to what is happening behind the scenes.
> As a non-coder it feels like the learning curve for building a website portfolio is super high - even though I am told by coders that it is not.
It is not high if you don't try to reinvent the wheel. Fortunately, you can build upon generous people's work.
Using frameworks is fine unless you end up using things you don't need.
There is still a learning curve, of course, because you need to learn where to look for answers. But building a portfolio site is indeed not that complicated.
Non-coder here, I started with WordPress, spent a lot of time learning how to code my own theme. Then I ditched it, learned the basics about how Git works, set up a static site using Jekyll, styled it with Tachyons. Then I added a gallery functionality and a few custom tweaks, just looking things up as I went. My site is now way simpler to maintain and faster. What took hours to look up and fix now seems easy.
Putting your portfolio site together yourself is time well spent.
Perhaps just start. Not on coding, but on content. Coding facilitates, but a lot of people have already spent a lot of time coding things already. My own 'portfolio' is a wiki, looks neither pretty nor ugly, at least to me, with a heck of a lot of text, about things that interest me. Wiki because of a realisation that chronological order didn't seem to make sense to a body of work that can be added to constantly.
He has helped countless people by giving great advice. I'd really suggest reading his "You Can Probably Stand To Charge More" posts. This should be essential reading for any contractors. This personally helped me double my income.
I had missed this gem of a post.
"Put in $1 then to get the ball rolling, and we’ll circle back to this later.” - How could I have not said something simple like this in my previous negotiations :) Baller of a post.
And yeah I finally decided to inject some character into my personal website and spent a couple of days wrangling with css and made this --- http://linkdot.link . Not much content really though and it is mostly probability puzzles that I solve every now and then.
Hey, just went on your site with firefox and the content was outside the screen. After digging into it a bit I found that you use "transform: scale(1.3)" on the body. It seems like firefox is positioning the element with its original dimensions and then scales the element. "transform-origin: 0 0" fixed it for me.
> Which makes me think, where do we draw the line in terms of web page size?
We look at the business case. TVS' website would be a disaster if it was targeted at the general public, with millions of hits each day. But it's not. His work on Spotify however does have to be optimized for that audience.
His personal site however can be whatever. It's showcased on industry sites like awwwards.com and the like, and those sites are all form, no function. In this environment, Pretty = useful, because it makes his work more noticeable, which is good for getting consulting work.
Do a quick search here on Designer News: https://www.designernews.co/ (it’s like HN but more design focused). They have hundreds of posts of amazing portfolios and personal sites. You’ll get a ton of inspiration there.
Following @jefflombardjr example, I would like to share an example of my personal website: https://lukaszkups.net .
Why do I like it? Because I've literally built it by myself from scratch - starting on design (all the graphics, even the map in experience tab) to the static site generation tool that I use to manage content (will release it soon as my first truly open source project).
Like the multicolored texts in the homepage. Good Colors choice. I like bright Colors but if you are going to be seeing it a lot better to go with Colors that doesn't spoil the eyes and page designs get darker over time.
This portfolio showcase page doesn't contain software project blog posts per se but has a lot of solid designer portfolio examples that might be interesting to check out: https://www.semplice.com/showcase
I tried to get all the important details on a single page and isolate the tech jargon to appeal to non-technical clients. I personally found and had non-technical friends agree with me that a lot of developer portfolios focused too much on the tech (e.g. "I'm a Node developer who loves React!") or go into too much detail about project specifics so I tried to avoid that.
What makes my site interesting is that.. I work in web dev and graphics, so I got to have some fun combining the two for my portfolio. I'd love to see more programmers taking advantage of web technologies to make their portfolios more visually interesting, and playful.
As much as Flash caused headaches and was a thorn in the side of the open web, there sure were a lot more interesting portfolio sites in the Flash days than there are now.
I built my personal website using Google Docs. https://navchatterji.com/. This was a fun weekend experiment where the aim was to build a quick, usable website (in this case a blog) and host it without having to type in a single line of HTML/CSS or terminal command. The instructions on how I made it is near the bottom.