If I use XHTML transitional doctype then will it show (in my portfolio) like I'm not a professional expert?

Question

If I use XHTML transitional doctype then will it show (in my portfolio) like I'm not a professional expert?

It is for one client who is not paying much for work, and he doesn't know about Web Standards. I want to use some deprecated or presentational item to save time so what should I give to him?

• Site with XHTML strict but with some validation errors

or

• Site with XHTML transitional but with W3C validation

What would be good if I add that site in portfolio?

Answer 1

Use whatever you comply with. Using a "strict" doctype will not prove you're a "professional".

Professional developers don't get hung up on the doctype definition you use, unless you have no doctype. What matters is the structure of your portfolio, both visually and in your markup/css/javascript.

Using a "strict" doctype vs. a transitional doctype has nothing to do with how "professional" you are. If you look at StackOverflow, you'll see even they use HTML 4 as their doctype, not even XHTML, and they did that as an intentional design choice, not an afterthought.

Answer 2

There's no point using a strict doctype if you're going to break it. Use transitional.

Answer 3

Standards are just that. Standards, a conventional guide. A "book of best practices". XHTML Transitional is a good score on a portfolio.

Compare this:

Opening a link on a new window, with XHTML Transitional:

<a href="about:blank" target="_blank"></a>

Same task, on Strict, requires a JavaScript approach, i.e.

<a href="about:blank" rel="new_window"></a>
<script type="text/javascript">
var links = document.getElementsByTagName("A");
for (link in links)
{
  if (links[link].rel.toString().indexOf("new_window") > -1)
  {
    links[link].onclick = function(e)
    {
      window.open(this.href, '', '');
    }
  }
}
</script>

Don't complicate yourself. Whatever you use, use it good.

Answer 4

The mark of a professional, IMO, is to understand what your customer would like to accomplish with your work, have the ability to explain to them the values and limitations of various alternatives, and for you to skillfully implement their choices. When you are up for another job and the employer is asking to see a portfolio you can show them the work and explain why certain design decisions were made.

Answer 5

The point is not if it will validate or not .. the points is why would you even consider using a doctype that you do not adhere to ?

Answer 6

"XHTML Transitional" is not a rubbish, it's a standard, like all other standards are. It has its sharp and clear rules and all your web project should run 100% correctly until you keep that standard. (e-e-e... IF the browser fully supports that standard, ha-ha. That question needs googling...)

Using "Strict" is a little bit preferable but don't be ashamed of using "Transitional". But avoid copy-pasting "Strict" code inside "Transitional" project as I did once =)

---

PS: there is one small thing... XHTML 1.1 needs adding [CDATA... inside <script></script> but almost nobody does that (google, yahoo, digg..etc etc) . And their sites keep working. What would you say?. Google on it's start page writes <!doctype> and they are wiser then we are

Answer 7

Why not get rid of the deprecated elements? Seriously, you only need them if you don't use CSS properly, and if you don't, then that's what shows that you're not a 'professional'.

Also, in my opinion XHTML documents should always validate. If you create tag-soup, use HTML.

Answer 8

Though there are some good reasons to use the transitional doctype, whenever I see a new page using it, I automatically question whether the author is using Dreamweaver or similar program to create it, and I always question the author's ability when they use deprecated elements without reason.