...if you release a web site to the client and you would like the web site to be in your porfolio...But the client messes with the coding of the web site and screws some things up so it's not correct?

My example:
http://triplemoonsdesign.com/SMP/ (what it should look like)
http://smpdevelopment.com/ (what it does look like)

While it's not MAJOR problems with the web site that he fudged up, it's things that I would NEVER do and IMO makes me look like an idiot (it does say Designed & Developed by Triple Moons Design at the bottom).

So, while I realize I can't tell this guy he messed up my work and it needs fixed, do you think that it's a viable option for me to link the site hosted on my own server rather then the actual site in my portfolio? Or would that just look bad?

Why wouldn't you link to the website on your own server? Heck, you can go ahead and create websites that clients have not YET purchased, and still place them on your portfolio. It doesn't have to be a live website, for it to appear on your portfolio, it just has to be created!

A portfolio is used to give future clients a sense of what your work is like. It doesn't matter where it's hosts, as long as it's good.

P.S - Poor guy just added a link . Try telling him to decrease the padding or something.

Originally Posted by andrei155

Poor guy just added a link . Try telling him to decrease the padding or something.

Actually no, he did a bit more then that. You have to compare the two closely. I think I picked it all out so quickly because I programmed the original one.

Sorry, I spent around 4 seconds on each site :P, that's all I noticed. :P.

Anyways, I hope that answered your question.

Stephanie I used to link to the sites in my portfolio because I wanted people to be able to see the code I used in case they were interested. I also wanted them to see how the site functioned I encountered the same problems as you with clients changing things.

Now I just show a thumbnail image with a link to a larger image. Take a screen shot of the site before you hand it over and use that image. You can still provide a link to the actual site too if you want, but you have the image to show what it looked like when you turned it over to the client.

You could also use a series of images if you want to show more than one and you can always host a version of the site on your server.

Originally Posted by TripleMoons

...if you release a web site to the client and you would like the web site to be in your porfolio...But the client messes with the coding of the web site and screws some things up so it's not correct?

My example:
http://triplemoonsdesign.com/SMP/ (what it should look like)
http://smpdevelopment.com/ (what it does look like)

While it's not MAJOR problems with the web site that he fudged up, it's things that I would NEVER do and IMO makes me look like an idiot (it does say Designed & Developed by Triple Moons Design at the bottom).

So, while I realize I can't tell this guy he messed up my work and it needs fixed, do you think that it's a viable option for me to link the site hosted on my own server rather then the actual site in my portfolio? Or would that just look bad?

Either way it looks pretty bare bones... Just take a screen shot of the site and have the image in your portfolio linked to his website.

Originally Posted by vangogh

Stephanie I used to link to the sites in my portfolio because I wanted people to be able to see the code I used in case they were interested. I also wanted them to see how the site functioned I encountered the same problems as you with clients changing things.

Now I just show a thumbnail image with a link to a larger image. Take a screen shot of the site before you hand it over and use that image. You can still provide a link to the actual site too if you want, but you have the image to show what it looked like when you turned it over to the client.

You could also use a series of images if you want to show more than one and you can always host a version of the site on your server.

That's exactly where I'm having the issues. I want them to be able to see the functionality but in the correct way, not what they changed and doesn't look/work proper. I like your thought on a pop up larger image of the web site and then having somewhere they can click to view the functioning site as well...I think I'm just going to host the problem children on my server if they are small enough and just link that. I just wasn't sure if that was a kosher thing to do...

Originally Posted by highanddry

Either way it looks pretty bare bones... Just take a screen shot of the site and have the image in your portfolio linked to his website.

Excuse me? You obviously aren't understanding my question.

I would take a screenshot at the time of delivery, and I wold still keep a copy of the websote, both for my portfolio, as well as incase the client messes up the page, in which case, I can chage him extra.

Originally Posted by rsrikanth05

I would take a screenshot at the time of delivery, and I wold still keep a copy of the websote, both for my portfolio, as well as incase the client messes up the page, in which case, I can chage him extra.

Of course I keep a copy of the web site. Not only in case they trash it and it needs fixed, but because you never know with some of these hosting companies...

Saving the web site isn't what my question was. It was about whether or not it looked ok for me to link to the web sites that are hosted on my own server rather then the live web sites. I am using Vangogh's suggestion.

I suggest you host a copy.
To tell the truth, I see negligible difference in the two.

Originally Posted by rsrikanth05

I suggest you host a copy.
To tell the truth, I see negligible difference in the two.

Again, I am using Vangogh's suggestion.
This is not the only problem child, this is simply a single example.

No need to continue offering "suggestions," I know what I'm doing.

I don't know if it's just me and my preggo hormones, but I'm seeing a LOT of replies recently that just aren't reading the entire thread...

Time to delete a few posts and close the thread since we can't all behave like mature boys and girls.