1.866.PIXELMILL (1.866.749.3564 US/Canada)

Search Support

Search our knowledgebase? Enter keywords or article id:

> go to search support


Support Index


Help and Support


Search

Go back to search results

Enter keyword or id#:




Promotions


Quick Links

Printable Article

What DOCTYPE should I use for my site to validate?

Article ID: KB101750

Question: My template doesn't have a DOCTYPE. What DOCTYPE should I use for my site to validate?

Answer: There is no easy answer to this question, because it really depends on what you've done with your site and how the template was originally designed. You see, assigning a DOCTYPE after creating a web site is working backwards. The idea is that you should start with a DOCTYPE, and then build the site around that standard. Assigning a DOCTYPE does not help your site to validate magically; you can only have a validated site if you first define a DOCTYPE and then build the rest of the page to follow the rules defined by the DOCTYPE.

Some of our templates are not coded to a specific DOCTYPE. If the product details page does not show a specific DOCTYPE compatibility, then the template is not guaranteed to validate to any specific DOCTYPE. The diagram below shows part of the PixelMill product details page for a template that is compatible with the XHTML doctype. If a template does not show anything under "Standards", then it's possible that it won't validate.

Doctype specified in product details

So if your template has not already been designed to validate with a specific DOCTYPE, chances are that you'll find it difficult to get your site to validate. We would encourage that you look at our other templates that have been predesigned to be compliant with a specific DOCTYPE.

Even if you purchase a "compliant" template, keeping the web site compliant is up to you. You should be aware of the limitations of your web editor; for example, FrontPage webbots are notorious for generating code that are not compliant. So if you are using a compliant template but then add lots of FrontPage components, you won't have a compliant site anymore. Newer web editors, such as Dreamweaver 8 and Expression Web, do help you to keep a site compliant by inserting code that follows the DOCTYPE you're using or warning you if there is code that isn't compatible.


Was this helpful?

Please rate this article:

Not helpful Very helpful
1 2 3 4 5 6 7

Email address: (not required)

(Please provide your email address if you would like PixelMill support to follow-up with you about your comment. You're email address is NOT REQUIRED to submit a comment.)

Comments: (How can we improve this article?)


Clicking "Submit" will not clear this page.


link to this page: http://www.pixelmill.com/support/al1092/kb101750.htm
permalink to this article: http://www.pixelmill.com/support/kb101750.htm

Back to top

Items you recently viewed:


pm46519htdl1
$98.00

pm45887dwdl1
$94.00

pm45779fpdwtdl1
$87.00

pm46207fpdwtdl1
$98.00


PixelMill EDU

Introducing...

PixelMill EDUâ„¢ is an innovative and proprietary online training series designed to aid the do-it-yourself Web builder in transitioning to new Web editors, coding standards, and Web technologies.

Webinars and Seminars:

FrontPage to SharePoint Designer Series
This is a 6-Week series designed to give you strong exposure to the new SharePoint Designer web editor and interface, along with examples of working with Windows SharePoint Services and tips for transitioning from FrontPage.
Register Now!

Tables to Tableless CSS Series
This is a 6-Week series designed to help you transition from building Tables-based Web site layouts to working with CSS to edit and build Tableless Web site layouts. For all Web builders using Dreamweaver, Expression Web, or any other web editor.
Register Now!

FrontPage to Expression Web Series
This is a 6-Week series designed to give you strong exposure to the new Expression Web software and interface, along with tips for transitioning from FrontPage.
Register Now!

Learn more and register!

ADVERTISEMENT
adventisement