Web development portfolio tips from an interviewer’s perspective

Yaphi Berhanu on August 22, 2017

This article originally appeared on Simple Steps Code. A lot of people have asked me what makes a good web development portfolio. I can't speak... [Read Full]
markdown guide

Could you review this layout idea for my website? s.codepen.io/bigblind/debug/BpdoQL...

The page currently shows a blog, but if I were to make a portfolio section, it'd be a simple grid in the main content section, with images on the left, and descriptions on the right.


Yeah that would be a great layout! (For reference, this url ended up working for me: codepen.io/bigblind/pen/BpdoQL/)

The page view was clearly structured, and it responded well to different widths.

For your mobile menu, since it's fixed, I'd add an overflow: scroll; to it (or however else you want to handle it) in case the bottom of it gets cut off. That's a small thing though.

Nice work, and I hope this has been helpful!


Thank you so much for taking the time to do this. Both the article and your feedback were enormously useful.


Also, I'm sorry, I didn't know debug links could expire. I opened the link in Incognito mode to make sure it worked for other users, but didn't think to look up whether there were other restrictions.

No worries. Link shares can be tricky when urls have unpredictable restrictions like that. Happens to me all the time.


Very excited that you posted this article, I am just beginning to start building things to add to my portfolio/github. It was somewhat mentioned in the project ideas, but when do you think the appropriate time or situation is to begin adding frameworks, libraries, etc., versus sticking with the basic tools (For web, HTML, CSS, plain JS)? Is it just until you believe you have a good grasp of those and have some work to back up the confidence in those skills?


I like the idea of getting comfortable with HTML, CSS, and plain JS first, so I'd agree with your statement about having a good grasp of those along with some projects to back up your skills. It's so much easier to learn a framework when you know those languages.

Once you're comfortable with the fundamentals, the next step is to look at companies you're interested in and see what tech most of them seem to be using. If there's a framework that keeps popping up, experiment with that and build a small project with it. That way you'll have an idea of how to use it, and you have evidence you can point to that you've used it.

If you ever find yourself unsure what to spend time on, you won't go wrong sharpening your HTML, CSS, and JS since these automatically make you better at many frameworks at once.

code of conduct - report abuse