How exactly do you build a web portfolio?

[rane500]

First I'll introduce myself:

Hi, my name is Matt. I'm currently a junior Java developer with a telecommunications firm, but I'm about to take a generous voluntary severance and reenter the job market. I've decided this time that I want to play to a serious strength that was only really utilized at my current job in a secondary capacity: PHP, MySQL, web UI design, dynamic web content, etc. etc. etc.

My question is this...how exactly does one build a good web portfolio? Obviously I cannot take any *official* work with me from my current position, because it's all for very specific internal sites, tools, and a lot of sensitive data. I do have several sites I've done for friends, organizations I've belonged to, or personal projects...but these range from the quick and dirty to sites containing content I'd just as soon NOT point a potential employer to. :) (Mostly just language, no porn or anything)

So...what would be the best course for me to take? I have several months before the severance actually happens, so I've got plenty of time and am perfectly willing to create some fully-featured and complex "demo" sites, but is that even acceptable? I could also copy the outside sites I've done and change the content to some generic demo-style content, but is that kind of cheesy? (Side note: I retained the rights to reuse all code for things of this nature, so that's not an issue) Is the typical portfolio just a series of links with documentation as to what the destinations are and how they're built, or am I going to be expected to have files on a CD at some point?

Many of the leads I'm examining don't explicitly ask for a portfolio, but I have no doubt in my mind it would help. I can legitimately claim many years of on the job experience with these technologies, so I'm not really worried about my resume contents. I'm just curious as to exactly what constitutes a web portfolio, what's kosher and what I should and should not do.

I've done some research online and did a brute force search for portfolio information on these forums, but in both cases I wasn't getting any hits that really went into what I'm curious about. I finally figured I'd go straight to the source and ask some knowledgable folks who have existing jobs and the portfolios that they use to get said jobs. (/not-so-subtle buttering up)

Thoughts? Thanks in advance.

[Jason Batten]

No one knows? Either everyone is a liar on this forum or you're all cowards? Which is it? Unbelievable, when you want them to show some proof they all run away - typical.

I have no idea. Looking for the same sort of information myself. I suppose it depends on who is going to be reviewing the portfolio.

[dalecosp]

Find some tax-exempt orgs that need a site, do it for free, or dinner, or a mention in their newsletter.

Might work, might not. Most of my income comes from troubleshooting, repair, network installation, not programming.

But, I do it anyway, and charge when I can.

[Jason Batten]

That was slightly helpful, thank you... I'll beat you with the stick later ;)

Anyone who is an experienced freelance programmer here? Surely you have a porfolio gathered of some sort?

[rane500]

The most important question that I hope someone can answer is the demo site one. I have enough time to build several detailed demo sites and I've got dedicated hosting already. I'd even be more than happy to spring for domains to make it that much more detailed. (I would NOT try and pass them off as real sites, however.)

Problem is, is this even worth anything in the professional world? I don't have anyone handy that needs a public project, and even if I did there's no guarantee I'd be able to get specifications, code it, get client approval, and get it deployed properly by the time prospective employers would need to check it out. Art and commercial design professionals have mixed portfolios...there are pieces from prior jobs and contracts, and there are pieces just demonstrating various aspects of their talent.

Why am I uptight about this? Because I'd really, really hate to invest the time and energy into something that ends up being worthless and even potentially damaging if it's some sort of huge faux pas to showcase work that isn't "real." I know that's probably not the case, and I'm looking at plenty of postings that don't mention or want a portfolio anyway...but I know that even in those cases it could potentially give me an enormous advantage if I could say - hey, I have a portfolio, examples of what I do if you'd like to take a look.

[Shrike]

In my experience employers want to see URLs and lots of them. I put about 15 sites that I had worked on at my previous job on my CV, even if I'd just done the tiniest amount of work. If they can click on a URL and visit the site in question, all the better - but really they will just want to ask you about them at interview. Demo sites demonstrate your skills, whch is great, but being able to show commercial websites and applications demonstrates your experience of the industry.

[vaaaska]

Spend your time doing actual work. If you have the extra time to do something to show your talent make sure it's good. As a programmer you should focus on showing those skills as opposed to looking like a web designer.

Prospective employers will always be a mixed bag - you simply can't predict what they will care about. Real life experience is going to trump all.

Being a graphic designer I can say that online portfolios are only worth the people that you show them to - meaning, you still need the real world connection (or some PR type good luck) for them to be signficant. I know alot of young designers who have invested alot of time in them expecting to reap direct benefits from them...but it's pretty unlikely to happen.

Talking to people is always better than hoping they will visit your website.

[Jason Batten]

I'll just cover all areas as best as I can then ask for feedback.

[rane500]

I think I'm going to get permission to snap some screenshots of some of the internal work I've done and polish up several sites done for friends. Both are code heavy and directly related to what I'm trying to get a job doing, so hopefully that will be enough to help me out.