Then I think you got the point.

The title links to the article... https://hackernoon.com/blockchain-is-like-my-first-time-with-weed-c13c41982578

Good point - fixed!? https://jessekorzan.github.io/expodal/

The worst examples are... my kids!

Another good question.

If it was me, I'd work on a mock-up or a concept sketch and show it to potential clients and friendlies for feedback. Do this a couple times until you feel the feedback is positive enough to move on (looks professional, people trust you have the skills, work examples are clear, and so on).

OR... post works in progress here for other designers to help you nail down a purposeful and stylish site that you're happy with.

Great question.

"Good" design is solving a problem. I'd maybe start with knowing the purpose of your site... Instead of starting with style.

Style is a fine concern to have. Just be cautious... it's hard to know when you're done if your main goal is simply a "stylish site".

If it's strictly a portfolio... don't stress too much. Your personal site shouldn't overshadow your work examples. Your main goal should be that folks see one or two examples of your work that best highlights your skill and abilities.

If it's not a portfolio... maybe it's a concept that showcases what you're most interested in (i.e. interactive video... make an interactive video). It's OK to make something that you enjoy making. A personal site is a good place to explore and go through some trial and error.

Regardless... the best part about a personal site is that it's your site. You can re-do it, mess around with it, change it as you see fit.

Lastly... don't feel constrained to "one" style. Make two sides to your site. One side that simply communicates why you should get hired. The other side... edgy, explorative, etc.

Nice. You said it way better than I did!

Some folks, like myself, have a variable process. Certain projects, maybe I do jump from quick paper sketches to HTML wireframes, other projects require more work; photoshop time for element collages, complex wireframes to spec out requirements, different stages of fidelity for prototypes, user testing, etc.

Paper sketches are often good enough for wireframes, so maybe skip the Omnigraffle. A competitors website can be a fine prototype (using Chrome dev tools, change a logo, change a couple colours and bam! you've got a good reference for early discussions with stakeholders).

Personally, as I got (get) more experience, I am better equipped to gauge when I've defined a problem well enough to start solving it. And what tools/steps I am best with to deliver an appropriate solution. The problem (and constraints) dictates the tools, not the other way around, I guess.

Charles, good question. When you say you are slow, is it you're missing deadlines or you feel you could be more profitable with your time?