Portfolio

Introduction

It’s time to build your portfolio! But why? It can be argued that you can get a job without one. And it’s true. Many organisations don’t look at portfolios when hiring. So why bother? Let’s discuss a few reasons.

You want to stand out. It’s a highly competitive world out there. The fight to get through the tech industry job without any experience is tough. So you want to stack the deck in your favour by doing all you can to stand out. Your portfolio will convey an image of you. It will show that you care, that you’re organised, that you have a plan for your learning. It will show your design skills. Either you want it or not, you have a brand, everyone does. And a portfolio will make your brand stronger.

It pushes you. I’d even go as far as saying that you should build a portfolio before building any projects. That’s because it sets your vision. The vision of a full portfolio in a year time prevents you from procrastinating. It makes you get out of bed to code and put in the work. It keeps bugging you in the back of your mind: “My portfolio is empty, I have to keep going”.

It will also prevent you from quitting. No matter how many rejections you get, you know that if you keep building, eventually your portfolio will be so impressive that YOU WILL GET NOTICED. Imagine your prospective employer looking at your portfolio with projects covering dozens of different technologies? “We gotta check her out!”, they’ll think.

It's a project in itself: Building a portfolio is … PART OF YOUR PORTFOLIO! It will be part of your practice as a developer. You’ll have to choose a model, design it, look after the front-end details, put yourself in the viewer’s shoes, think of what to have in it, it’s great practice all-around.

You’ll have to choose which technology to use: WordPress? HTML/CSS? Vanilla JS? A front-end framework? Choosing technologies is part of a developers job. And you get to practice that too. But enough talking about it, let’s do it!

Requirements

  • Your portfolio should be a static website
  • The following sections are required: A top area with a 'banner' or 'hero'; 'About me'; 'My work', 'Contact', Footer
  • You can use any technology you want: WordPress, a front-end framework, bootstrap or just the good old Html/Css/Vanilla Js combo.
  • The 'My Work' area should contain links to your github repositories. If you have full-stack web apps, it should contain links to their webpages.
  • Your portfolio should contain a "Download Resume" button, preferably in the top area.
  • It should be responsive and look good in any screen size.

Tips

  • Keep it simple. The best portfolios are the ones with an impressive amount of quality projects, not fancy, flashy, empty ones. Your goal here is to build your portfolio fast and get back to work.
  • Before publishing your portfolio, make sure it's reviewed by someone in the industry. If you post your work on our Discord community, we'll be happy to help.
  • Simple doesn't mean sloppy. Review it dozens of times so there are no misspellings, typos, broken links, non-matching colours, misaligned sections.

Introduction

It’s time to build your portfolio! But why? It can be argued that you can get a job without one. And it’s true. Many organisations don’t look at portfolios when hiring. So why bother? Let’s discuss a few reasons.

You want to stand out. It’s a highly competitive world out there. The fight to get through the tech industry job without any experience is tough. So you want to stack the deck in your favour by doing all you can to stand out. Your portfolio will convey an image of you. It will show that you care, that you’re organised, that you have a plan for your learning. It will show your design skills. Either you want it or not, you have a brand, everyone does. And a portfolio will make your brand stronger.

It pushes you. I’d even go as far as saying that you should build a portfolio before building any projects. That’s because it sets your vision. The vision of a full portfolio in a year time prevents you from procrastinating. It makes you get out of bed to code and put in the work. It keeps bugging you in the back of your mind: “My portfolio is empty, I have to keep going”.

It will also prevent you from quitting. No matter how many rejections you get, you know that if you keep building, eventually your portfolio will be so impressive that YOU WILL GET NOTICED. Imagine your prospective employer looking at your portfolio with projects covering dozens of different technologies? “We gotta check her out!”, they’ll think.

It's a project in itself: Building a portfolio is … PART OF YOUR PORTFOLIO! It will be part of your practice as a developer. You’ll have to choose a model, design it, look after the front-end details, put yourself in the viewer’s shoes, think of what to have in it, it’s great practice all-around.

You’ll have to choose which technology to use: WordPress? HTML/CSS? Vanilla JS? A front-end framework? Choosing technologies is part of a developers job. And you get to practice that too. But enough talking about it, let’s do it!

Requirements

  • Your portfolio should be a static website
  • The following sections are required: A top area with a 'banner' or 'hero'; 'About me'; 'My work', 'Contact', Footer
  • You can use any technology you want: WordPress, a front-end framework, bootstrap or just the good old Html/Css/Vanilla Js combo.
  • The 'My Work' area should contain links to your github repositories. If you have full-stack web apps, it should contain links to their webpages.
  • Your portfolio should contain a "Download Resume" button, preferably in the top area.
  • It should be responsive and look good in any screen size.

Tips

  • Keep it simple. The best portfolios are the ones with an impressive amount of quality projects, not fancy, flashy, empty ones. Your goal here is to build your portfolio fast and get back to work.
  • Before publishing your portfolio, make sure it's reviewed by someone in the industry. If you post your work on our Discord community, we'll be happy to help.
  • Simple doesn't mean sloppy. Review it dozens of times so there are no misspellings, typos, broken links, non-matching colours, misaligned sections.
An error has occurred. This application may no longer respond until reloaded. Reload 🗙