advanced search

XHTML 1.1 web standard template

Published in: HTML 

This is a generic template for an XHMTL 1.1 doc that I start with at the beginning of every project.

Then i setup the directories to match. I use @import for CSS, then a seperate CSS file for screen-specific, and then one for print.
I have the basic DIV structure setup, too.

Hope it helps!


Plain TextExpand 
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
  3. 		 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
  4. <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
  5. 	<head>
  6. 		<meta http-equiv="content-type" content="text/html; charset=utf-8" />
  7. 		<title>title goes here</title>
  8. 		<base href="base url goes here" />
  9. 		<meta name="Author" content="#" />
  10. 		<meta name="Robots" content="#" />
  11. 		<meta name="Generator" content="#" />
  12. 		<meta name="Keywords" content="#" />
  13. 		<meta http-equiv="Expires" content="#" />
  14. 		<meta name="Description" content="#" />
  15. 		<meta name="Copyright" content="#" />
  16. 		<meta http-equiv="Cache-Control" content="#" />
  17.     <link rel="Shortcut Icon" href="/favicon.ico" type="image/x-icon" />
  18.     <link href="/script/javascript.js" type="text/javascript"  />
  19. 		<style type="text/css" xml:space="preserve">
  20. 		/*<![CDATA[*/
  21. 		      @import url(/css/style.css) all;
  22. 		/*]]>*/
  23. 		</style>
  24. 		<link rel="stylesheet" href="/css/screen.css" type="text/css" media="screen" />
  25. 	  <link rel="stylesheet" href="/css/print.css" type="text/css" media="print" />
  26. 	</head>
  27. 	<body>
  28. 		<div id="container">
  29.  
  30. 			<div id="header">
  31. 				<h1>Title of page goes here</h1>
  32. 				<h2>Subtitle of page goes here</h2>
  33. 				<h3>Skip to content</h3>
  34. 			</div><!-- end header div -->
  35.  
  36. 			<div id="nav">
  37. 				<ul>
  38. 					<li><a href="#">Link #1</a></li>
  39. 					<li><a href="#">Link #2</a></li>
  40. 					<li><a href="#">Link #3</a></li>
  41. 				</ul>
  42. 				<ul id="breadcrumbs">
  43. 					<li><a href="#">Home</a></li>
  44. 					<li><a href="#">sub directory</a></li>
  45. 					<li><a href="#">current page</a></li>
  46. 				</ul>
  47. 			</div><!-- end nav div -->
  48.  
  49. 			<div id="main">
  50. 				<h3>Title of article goes here?</h3>
  51. 				<p>Begin article here</p>
  52.  
  53. 				<ul id="sidebar">
  54. 					<li><a href="#">Sidebar Link #1</a></li>
  55. 					<li><a href="#">Sidebar Link #2</a></li>
  56. 					<li><a href="#">Sidebar Link #3</a></li>
  57. 				</ul>
  58. 			</div><!-- end main div -->
  59.  
  60. 			<div id="footer">
  61. 				<p>©2XXX company name here. Creative Commons link/ your own link</p>
  62. 			</div><!-- end footer div -->
  63.  
  64. 		</div><!-- end container div -->
  65.  
  66. 	</body>
  67. </html>

Report this snippet 

Comments

RSS Icon Subscribe to comments
Posted By: dwight_stegall on February 13, 2008

don't put this above it

<?xml version="1.0" encoding="utf-8"?>

Posted By: dwight_stegall on February 13, 2008

you should test your code before posting it.

putting this

above the the doctype moves the doctype down one line and throws internet explorer into the quirks mode. if you are going to operate in the quirks mode why bother to use a doctype in the first place?

Posted By: ethan on January 29, 2008

Nice enough idea in principle... the only caveat I would raise is the use of the XHTML 1.1 variant. This DOCTYPE is intended as the foundation upon which to build compound document formats (XHTML + MathML + SVG + etc).

You should really be using XHTML 1.0 Strict.

Given proper conformance to the XHMTL standard and modular inclusion of the DOCTYPE across a site then upgrading to XHTML 1.1 ought to be simple.

Hope that helps

Posted By: bhertz on November 19, 2007

There are issues with this template that users should know about. Using the xml prolog (

Posted By: bhertz on November 19, 2007

There are issues with this template that users should know about. Using the xml prolog (

Posted By: Mikael on September 26, 2007

Looks like the copyright symbol doesn't read correctly in W3C's validator. Otherwise it was completely valid for me!

Posted By: nano on November 7, 2006

Mmmk, for some reason the code isn't showing, so let's try without tags:

Current: link href="/script/javascript.css" Suggested: link href="/script/javascript.js"

Posted By: nano on November 7, 2006

I think there's a typo at line 18: Wouldn't be better something like:

I mean just to be consistent with extension naming conventions. Anyway it's a great template, thanks for sharing!

You need to login to post a comment.