Mar 20

There is no software to convert the design PSD into XHTML/CSS or HTML/CSS ?
I think there’s an option to convert PSD to XHTML/CSS - but even so, you’ll not get what you want and there will be still many changes you’ll need to do. (And even tougher cause you gotta read the xhtml/css from top to toe to know what’s already there and what’s not)

It’s still the best to go for a manual xhtml/css coding service. Just like domain appraisals, manual ones are still the best and should never be comprimise with automated ones.

You can get cheap xhtml/css services but I’m not sure about their quality, if you’re looking for quality work, you can perhaps try me.

I’d have to agree on this. Your best bet is to get a PSD coded by hand. If you have a PSD that needs to be coded, I’m sure there are plenty of people here willing to do this for a reasonable price.

Just wondering, what’s the site you found that can take an uploaded PSD and convert it? Are you sure it’s automatic?

Anything you attempt to use for completely automatic PSD->HTML conversion is going to produce horrible results. This is absolutely something that needs to be done by a professional, unless massively bloated pages that take 15 seconds to load, an unreadable mess of code, and complete non-conformance with web standards is alright with you.

1) Automated tools to do that type of conversion usually result in horribly coded train wrecks of pages that don’t work cross browser for ****. Just like how the WYSIWYG parts of things like “the artist formerly known as frontpage” and that steaming pile of crap known as dreamweaver do more to ruin a website than help it.

2) Starting with a goof assed pretty picture for a site design is putting the cart before the horse that usually results in a total miserable /FAIL/ at web development.

Why do I say this? Because you can’t say in a picture what is a h1, what’s a h2, what’s going to be a paragraph, pictures do not adjust to changes in content and often tie you to designs that cannot grow/shrink as the content is edited, it tempts you into having your heart set on fonts that cannot be used on a website that actually bothers with accessability - It’s a disaster waiting to happen. Whoever the hell started this ‘design in photoshop’ BULLSHIT needs to be taken around back of the woodshed with a 30-06 and put down like old yeller… or at the very least have their head bashed in with a cinderblock.

This is the process I advocate

STEP 1 - START by determining the content that will go on the site, then mark up that content using semantic markup saying what each part of that content IS with ZERO concern for how it is going to look on the final page. This will result in a page that degrades well when CSS and the pretty pictures are unavailable. This also will show you what search engines are likely to see for your page so long as you put NO PRESENTATIONAL ELEMENTS IN YOUR MARKUP AT THIS STAGE.

STEP 2 - THEN bend that markup to your will using CSS to create your layout with some nice backgrounds and colors for people who are still stuck on 33.6 (upstate VT, upstate NH, backwoods ME, Utah, Colorado) or are stuck paying for METERED bandwidth and as such turn images off.

STEP 3 - ONLY at this point should you be going to your paint program to create images to hang on the layout. You may need to add an occasional SPAN sandbag or wrapping DIV as hooks for the images at this point, but those should not effect rendering as it appeared at the other two stages.

Starting out with some goofy art (sexual preference slur) picture is a completely back-assward approach to web development, started by artsy designers who frankly wouldn’t know accessability if it stripped naked, painted itself purple and hopped up on a desk singing “look at what a well formed document I am”

Reputation management

braces london

driving schools in Solihull