<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pro Web Marketing &#187; Web Standards</title>
	<atom:link href="http://www.prowebmarketing.com/blog/category/web-standards/feed" rel="self" type="application/rss+xml" />
	<link>http://www.prowebmarketing.com/blog</link>
	<description>Web Development &#38; SEO Experts</description>
	<lastBuildDate>Tue, 10 Jan 2012 15:39:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Web Fonts: Revisiting an old problem</title>
		<link>http://www.prowebmarketing.com/blog/web-content/web-fonts-revisiting-an-old-problem</link>
		<comments>http://www.prowebmarketing.com/blog/web-content/web-fonts-revisiting-an-old-problem#comments</comments>
		<pubDate>Mon, 10 May 2010 20:12:28 +0000</pubDate>
		<dc:creator>Pro Web</dc:creator>
				<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Web Content]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Website Tools]]></category>

		<guid isPermaLink="false">http://www.prowebmarketing.com/blog/?p=454</guid>
		<description><![CDATA[In a previous article about fonts and web standards, we discussed the problems designers face with fonts on the web and some various solutions.  Today&#8217;s article brings an update to the field in the form of a few new contenders on the web-font battlefield. Font Squirrel&#8217;s @Font-Face Generator @font-face was CSS&#8217;s original answer to the [...]]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://www.prowebmarketing.com/blog/web-site-tools/using-non-standard-fonts-solutions-and-issues">a previous article about fonts and web standards</a>, we discussed the problems designers face with fonts on the web and some various solutions.  Today&#8217;s article brings an update to the field in the form of a few new contenders on the web-font battlefield.</p>
<p><span id="more-454"></span></p>
<h2><a href="http://www.fontsquirrel.com/fontface/generator" target="_blank">Font Squirrel&#8217;s @Font-Face Generator</a></h2>
<p>@font-face was CSS&#8217;s original answer to the web-font question, but due to poor browser support and confusing implementation methods, it hasn&#8217;t yet taken off.  Font Squirrel&#8217;s generator, on the other hand, combines the @font-face declaration and uses a combination of javascript and CSS hacks to make it work in old, incompatible, and obscure browsers.</p>
<p><a href="http://www.fontsquirrel.com/fontface/generator" target="_blank">http://www.fontsquirrel.com/fontface/generator</a></p>
<h2><a href="http://typekit.com/" target="_blank">Typekit &#8211; A commercial approach</a></h2>
<p>Typekit takes a new approach to web-fonts.  One of the forgotten (yet increasingly important) aspects of the web-font issue is the licensing.  With most solutions, designers use fonts online without thinking about licensing.  Typekit does all of that for you &#8211; at a cost.</p>
<p>Typekit is the first commercial model which hosts web fonts as a service.  Integration into your pages is supposed to be very easy and seamless.</p>
<p><a href="http://typekit.com/" target="_blank">http://typekit.com/</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.prowebmarketing.com%2Fblog%2Fweb-content%2Fweb-fonts-revisiting-an-old-problem&amp;title=Web%20Fonts%3A%20Revisiting%20an%20old%20problem" id="wpa2a_2"><img src="http://www.prowebmarketing.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.prowebmarketing.com/blog/web-content/web-fonts-revisiting-an-old-problem/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Photos for the Web</title>
		<link>http://www.prowebmarketing.com/blog/web-content/photos-for-the-web</link>
		<comments>http://www.prowebmarketing.com/blog/web-content/photos-for-the-web#comments</comments>
		<pubDate>Mon, 26 Apr 2010 19:27:12 +0000</pubDate>
		<dc:creator>Pro Web</dc:creator>
				<category><![CDATA[Photography]]></category>
		<category><![CDATA[Web Content]]></category>
		<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://www.prowebmarketing.com/blog/?p=447</guid>
		<description><![CDATA[At Pro Web, we receive a ton of photos every week &#8211; many of them to be integrated into client websites.  Sometimes we  have to throw out a lot of potentially good photographs because they are not &#8220;fit&#8221; for the website.  What usually causes this is incorrect layout &#8211; an easily avoidable mistake. There are [...]]]></description>
			<content:encoded><![CDATA[<p>At Pro Web, we receive a ton of photos every week &#8211; many of them to be integrated into client websites.  Sometimes we  have to throw out a lot of potentially good photographs because they are not &#8220;fit&#8221; for the website.  What usually causes this is incorrect layout &#8211; an easily avoidable mistake.</p>
<p><strong>There are a few easy steps you can take to make sure your photos are appropriate for the web.<span id="more-447"></span><br />
</strong></p>
<h2>Consider where your photos are going</h2>
<p>Most photos on the web are places in a gallery of some sort.  Galleries, particularly on the web, tend to be in a &#8220;wide&#8221; format.  This means that they are designed to hold &#8220;landscape&#8221; style photographs, rather than tall, &#8220;portrait&#8221; style photos.  By taking your pictures with this in mind, you can improve the look of the gallery by making your images consistent.</p>
<p>If your photos are for a certain area of your website, keep the shape of that area in mind!</p>
<h2>Watch the background!</h2>
<p>When taking photos to display publicly on the internet, be sure to remove all unrelated items or clutter from the background of the shot.  This will not only improve your photo aesthetically, but it will appear more professional and more thought out.</p>
<h2>Do not scale or edit photos beforehand</h2>
<p>Unless you are a professional photographer or have other interests in mind, leave that part to your web company.</p>
<h2>Always turn off time stamps!</h2>
<p>&#8220;Time stamps&#8221; are small text overlays on your photo that display the date and time that the photo was taken.  While these can be useful, they can potentially destroy a photo, as it cannot be removed once the photo has been taken!  Be sure to make sure your camera does not have time-stamping enabled.</p>
<h2>Check out more tips</h2>
<p>We have several more tips on photography that you can use in tandem with the advice in this article.  <a title="Photography Tips" href="http://www.prowebmarketing.com/blog/category/photography">Check out more photography tips  from Pro Web Marketing!</a></p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.prowebmarketing.com%2Fblog%2Fweb-content%2Fphotos-for-the-web&amp;title=Photos%20for%20the%20Web" id="wpa2a_4"><img src="http://www.prowebmarketing.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.prowebmarketing.com/blog/web-content/photos-for-the-web/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CSS and Divs vs Tables</title>
		<link>http://www.prowebmarketing.com/blog/web-standards/css-and-divs-vs-tables</link>
		<comments>http://www.prowebmarketing.com/blog/web-standards/css-and-divs-vs-tables#comments</comments>
		<pubDate>Wed, 18 Nov 2009 04:19:37 +0000</pubDate>
		<dc:creator>brad</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[divs]]></category>
		<category><![CDATA[tables]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.prowebmarketing.com/blog/?p=282</guid>
		<description><![CDATA[When it comes to building sites some people are still using tables to create their layouts.  While these still may work they are outdated and can look unprofessional.  This is where CSS and Divs come in.  Not only are they the new and latest design technique but they also can give your site a superior [...]]]></description>
			<content:encoded><![CDATA[<p>When it comes to building sites some people are still using tables to create their layouts.  While these still may work they are outdated and can look unprofessional.  This is where CSS and Divs come in.  Not only are they the new and latest design technique but they also can give your site a superior look.  Some other benefits to using CSS and Divs include faster load times, cross-browser compatibility, lower hosting costs, less time spent, consistency maintained, easier for SEO, etc.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.prowebmarketing.com%2Fblog%2Fweb-standards%2Fcss-and-divs-vs-tables&amp;title=CSS%20and%20Divs%20vs%20Tables" id="wpa2a_6"><img src="http://www.prowebmarketing.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.prowebmarketing.com/blog/web-standards/css-and-divs-vs-tables/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Top 5 Tips for Readable Code</title>
		<link>http://www.prowebmarketing.com/blog/web-standards/top-5-tips-for-readable-code</link>
		<comments>http://www.prowebmarketing.com/blog/web-standards/top-5-tips-for-readable-code#comments</comments>
		<pubDate>Thu, 08 Oct 2009 21:06:43 +0000</pubDate>
		<dc:creator>Pro Web</dc:creator>
				<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[cascading style sheets]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[html]]></category>
		<category><![CDATA[xhtml]]></category>

		<guid isPermaLink="false">http://prowebmarketing.com/blog/?p=11</guid>
		<description><![CDATA[As an expert in CSS and XHTML, I am sometimes irked by having to work with or modify sites that have been coded in years past by developers other than myself.  More often than not, they do not adhere to the acceptable web standards that make editing others code much easier.  There are a few [...]]]></description>
			<content:encoded><![CDATA[<p>As an expert in CSS and XHTML, I am sometimes irked by having to work with or modify sites that have been coded in years past by developers other than myself.  More often than not, they do not adhere to the acceptable web standards that make editing others code much easier.  There are a few simple things you can do to make your XHTML much more digestible, and even more search engine friendly!<span id="more-11"></span></p>
<h2><strong>5.) Avoid Unnecessary Whitespace</strong></h2>
<p>Your XHTML should not contain any blank lines.  They increase file size, create more junk  for spiders to sift through, and can cause serious headaches for developers.  Avoid spaces at the end of your lines as well.</p>
<h2><strong>4.) Use proper indentation (nesting)</strong></h2>
<p>Using proper nesting can make a huge difference in your code&#8217;s organization, and can even make the coding process easier.</p>
<h2><strong>3.) Comment your code</strong></h2>
<p>Commenting your code might seem unnecessary, as to you, it is most likely self-explanatory.  The aim of code readability, however, is for your code to be easy to navigate for other people.  Be sure to create short comments in your code that indicate function.  You may wish to leave these out in the production version of your code, as they do increase file size.</p>
<h2><strong>2.) Always use proper casing</strong></h2>
<p>In XHTML, all tags should be lowercase.  In CSS, there is no declared casing syntax, but a naming convention should be followed consistently.  I prefer to use camel case.  A class name, for example, might be .sampleClass.</p>
<h2><strong>1.) Separate presentation from content</strong></h2>
<p>Your XHTML documents should be very small!  If you can avoid using an extra tag in your XHTML document, please do.  Use CSS and Javascript to their full potentials, and always use external scripting and styles.  This is extremely important for search engine optimization.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.prowebmarketing.com%2Fblog%2Fweb-standards%2Ftop-5-tips-for-readable-code&amp;title=Top%205%20Tips%20for%20Readable%20Code" id="wpa2a_8"><img src="http://www.prowebmarketing.com/blog/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.prowebmarketing.com/blog/web-standards/top-5-tips-for-readable-code/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

