Use this template to structure your Portfolios.

By the end of this, developers should be able to:

• Have something to show to potential future employers/recruiters/friends
• Work on a portfolio and implement more and more features throughout WDI

It's important that you begin thinking about what you want your online presence to look like. What do you want people to find when they google you? What do you want people's first impression of you to be when they visit the url on your business card?

• As a non-technical HR manager, I want to quickly evaluate whether this candidate has the skills and experience to fill an open position at my company.
• As a mid-level engineer, I want to evaluate a junior developer’s coding skills by reviewing their projects and reading their code.
• As a friend of the person who built this portfolio, I want to understand what they do as a developer and what they have created.

NOTE: There are lots more, but let's start with these!

• About Me: Short blurb explaining who you are, and some background info
• Skills: All the skills you have that may be helpful on the job
• Contact info (email, LinkedIn, GitHub, city)
• Resume view & download
• Showcase your GA projects (more details below)

• Personal hobbies/interests
• Professional Timeline (a visual representation of your work history)
• Additional work samples (visual design, writing samples, a link to your photography blog)
• Social profiles if relevant (Twitter, instagram, if they highlight you professionally, not just what your meals look like)
• Could include phone number and mailing address, but not necessary
• Blog posts (2-4) — Link to a medium account, or these could be built in native to the app if you really want bonus points!

• Include links to live site as well as front-end and back-end repos
• Describe both the functionality of the site as well as what technologies you used to build it.
• Talk about your process for building this app. If you have a blog post that goes into detail for each project, link to that post.
• As you add your GA projects to your portfolio, make sure they are user-friendly to an unacquainted visitor.
• The home page should explain the site’s functionality
• Random users might not want to sign up/sign in. You should either put dummy credentials on the homepage that they can use (and explain that), or make sure they can interact with the site without signing up.
• Clean up the data you’ve entered on the site as you were testing it.

If you’ve got design chops, use them. You have an opportunity to impress a wide audience with both your coding skills and your design abilities with this site. If you are not a strong designer, that’s okay too! Don’t try to be something that you’re not on this site. Keep your design simple, or mock up your site based off of another site you have seen that looks great. Get feedback from colleagues (especially non-developers and non-designers) to make sure it doesn’t look terrible. Keep it neutral and focus on producing good projects.

We highly recommend you use Bootstrap, Materialize, or Foundation to aid with the design of your portfolio. Choose one, and start adding features to your site! This doesn't mean you can't change in the future, but do some research and pick which ever one you like best!

1. Download this template.
2. Unzip and rename the template directory.
3. Empty README.md and fill with your own content.
4. Move into the new project and git init.
5. Create a Github repository as the remote for your portfolio
6. Deploy on GH pages as account User Site

You can only host 1 "User Site" per account/organization on the URL username.github.io so you are using that as your portfolio since it will be the showcase of the rest of the projects on your GH account. Read more about User Sites here

GH allows you to host other web sites as “Project Sites” which can be on the URLs username.github.io/project_names. You will have 4 projects which you will launch as “Project Sites” and you can have an unlimited number of those, we hope you add more than 4 after the program! Read more about Project Sites here

As you may know by now, in WDI we'll use browser-template to create web apps. However, since these portfolios typically won't have the same robust functionality, we've included simple index.html, index.js, and main.css files to get started without the added complexity of a webpack build.

Technical or non-technical? If your question is "Is it helpful to show that I'm also a donut fanatic on my portfolio page?" you should direct that towards Outcomes. If your question is "Is it appropriate to put a photo of me passed out at a bar?" the answer is "No." If your question is "Cannot read property of undefined you probably want to see what is to the left of the . and then open an issue here.

Other WDI Grads's Portfolios:

• https://derekbmcintire.github.io
• http://julianbarthold.com/
• https://andrewinnocent.com/
• https://nd56.github.io/ND-Portfolio/
• http://rhjones.me/
• http://gabescarbrough.com/
• https://nriser.github.io/portfolio/
• https://jbculbertson.github.io/
• https://coreyfedde.github.io/portfolio/
• http://cathyobrien.co

1. All content is licensed under a CC­BY­NC­SA 4.0 license.
2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].