<?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>Kieran Chapman Design &#187; Development</title>
	<atom:link href="http://kieranchapmandesign.com/category/development/feed/" rel="self" type="application/rss+xml" />
	<link>http://kieranchapmandesign.com</link>
	<description>Web and user experience design by Kieran Chapman</description>
	<lastBuildDate>Mon, 12 Mar 2012 00:12:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Most-Used WordPress Plugins</title>
		<link>http://kieranchapmandesign.com/2011/08/most-used-wordpress-plugins/</link>
		<comments>http://kieranchapmandesign.com/2011/08/most-used-wordpress-plugins/#comments</comments>
		<pubDate>Tue, 30 Aug 2011 19:26:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[CMS]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=589</guid>
		<description><![CDATA[These are the plugins I find most useful when developing a WordPress site.]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-591 alignright" title="wp_plugin" src="http://kieranchapmandesign.com/wp/wp-content/uploads/2011/08/wp_plugin.jpg" alt="wp_plugin" width="200" height="200" />There are thousands of <a href="http://wordpress.org/extend/plugins/" target="_blank">WordPress plugins</a> available, but there&#8217;s only a few that I use pretty regularly. Every WordPress developer has his own favorite plugins, and here are the ones I use most:</p>
<p><a href="http://wordpress.org/extend/plugins/advanced-twitter-widget/" target="_blank"><strong>Advanced Twitter Widget</strong></a><br />
Some WordPress themes come with a Twitter widget built in, but if yours doesn&#8217;t then Advanced Twitter Widget is a simple plugin that lets you add your tweets to your site. (And while it&#8217;s true you can use <a href="http://twitter.com/about/resources/widgets" target="_blank">Twitter&#8217;s own widgets</a>, I prefer to style the tweets to better match the site&#8217;s style.)</p>
<p><strong><a href="http://wordpress.org/extend/plugins/contact-form-7/" target="_blank">Contact Form 7</a></strong><br />
Contact Form 7 is a simple but useful contact form. Lets you easily create multiple custom forms and send to various email addresses.</p>
<p><strong><a href="http://wordpress.org/extend/plugins/exclude-pages/" target="_blank">Exclude Pages</a></strong><br />
Exclude Pages lets you create public pages that don&#8217;t appear in the navigation.  This is useful for public pages you&#8217;d like to remain hidden, landing pages you don&#8217;t want to appear in your site&#8217;s navigation, client pages, and for themes that don&#8217;t allow you to use <a href="http://codex.wordpress.org/Appearance_Menus_Screen" target="_blank">custom menus</a>.</p>
<p><strong><a href="http://wordpress.org/extend/plugins/lightbox-2/" target="_blank">Lightbox 2</a></strong><br />
Lightbox 2 automatically makes any linked image display in a lightbox-style popover, rather than just open the image in a browser window.</p>
<p><strong><a href="http://wordpress.org/extend/plugins/widget-logic/" target="_blank">Widget Logic</a></strong><br />
This is one of the most useful WordPress plugins, and it gives you a lot of control over how sidebar widgets appear on your site. While many WordPress themes allow for different sidebar content for various pages, some have a single sidebar for all pages. And even for those themes with multiple sidebars, you might want more control over what widgets appear on specific pages. Widget Logic lets you control exactly what widget appears on what page. That sounds vague, but once you learn how the conditions are written it&#8217;s powerful and easy to have widgets appear exactly where you want them.</p>
<p><strong><a href="http://wordpress.org/extend/plugins/wp-db-backup/" target="_blank">WP-DB-Backup</a></strong><br />
It&#8217;s always a good idea to make backups. WP-DB-Backup makes backups of your MySQL database and saves, emails or downloads it. You can also schedule automated backups to be sent to an email address.</p>
<p><strong><a href="http://wordpress.org/extend/plugins/wp-super-cache/" target="_blank">WP Super Cache</a></strong><br />
<a href="http://daringfireball.net/linked/2008/04/23/atwood-wp" target="_blank"> John Gruber</a> is infamous for trashing WordPress sites he links to: often such sites are overwhelmed with traffic, and WordPress can&#8217;t handle high levels of traffic very well. Enter WP Super Cache: this plugin creates cached versions of your site&#8217;s pages instead of having to hit the database each time a page is accessed. If you expect a lot of site traffic, WP Super Cache is a must-have.</p>
<p><a href="http://wordpress.org/extend/plugins/wordpress-seo/" target="_blank"><strong>WordPress SEO by Yoast</strong></a><br />
Another no-brainer plugin. WordPress SEO gives you control over page titles, descriptions, and keywords on a per-page basis. A nice feature is the &#8220;Google result preview&#8221; that shows how the page would appear in Google based on your current settings. Also, WordPress SEO generates a <a href="http://www.google.com/support/webmasters/bin/answer.py?hl=en&amp;answer=156184&amp;from=40318&amp;rd=1" target="_blank">Google sitemap</a> XML file as well (which eliminated the need for a no-longer-must-have plugin, <a href="http://wordpress.org/extend/plugins/google-sitemap-generator/" target="_blank">Google XML Sitemaps</a>).</p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2011/08/most-used-wordpress-plugins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>View Source on Mobile Safari</title>
		<link>http://kieranchapmandesign.com/2011/01/view-source-on-mobile-safari/</link>
		<comments>http://kieranchapmandesign.com/2011/01/view-source-on-mobile-safari/#comments</comments>
		<pubDate>Tue, 18 Jan 2011 23:53:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=520</guid>
		<description><![CDATA[For web developers building for the iPad]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re a web developer and want to view source on an iPad — for example, to see if iPad-specific code or CSS file is loading correctly — install the View Source on Mobile Safari bookmarklet: <a href="http://banagale.com/view-source-from-safari-on-ipad.htm" target="_blank">View Source from Safari on iPad</a></p>
<p><strong>Update</strong>: Daring Fireball linked to an improved version that&#8217;s a little more legible: <a href="http://www.ravelrumba.com/blog/ipad-view-source-bookmarklet/" target="_blank">iPad View Source Bookmarklet</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2011/01/view-source-on-mobile-safari/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Add Attributes to Links via jQuery</title>
		<link>http://kieranchapmandesign.com/2011/01/add-attributes-to-links-via-jquery/</link>
		<comments>http://kieranchapmandesign.com/2011/01/add-attributes-to-links-via-jquery/#comments</comments>
		<pubDate>Thu, 06 Jan 2011 00:29:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[jQuery]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=512</guid>
		<description><![CDATA[Use jQuery for automatic lightbox-style effect with image links.]]></description>
			<content:encoded><![CDATA[<p>I was working on a recent project that used a lightbox-style jQuery plugin called <a href="http://famspam.com/facebox/">Facebox</a>. This allowed me to put both images and DIVs of content into a lightbox-style popover — simply add <span style="font-family: Consolas, Monaco, 'Courier New', Courier, monospace; line-height: 18px; font-size: 12px; white-space: pre;">rel=“facebox“</span> to an anchor tag and it would activate the popover.</p>
<p>The one thing Facebox didn&#8217;t do &#8220;out of the box&#8221; was automatically make links to images open in the lightbox window. To fix this, I just used a bit of jQuery to add <span style="font-family: Consolas, Monaco, 'Courier New', Courier, monospace; line-height: 18px; font-size: 12px; white-space: pre;">rel=“facebox“</span> to any anchor tag that linked to a JPG or PNG:</p>
<pre>// add rel="facebox" to image links for lightbox effect
$("a[href$=.jpg],a[href$=.jpeg],a[href$=.png]").attr("rel","facebox");</pre>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2011/01/add-attributes-to-links-via-jquery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reduce Your PNGs</title>
		<link>http://kieranchapmandesign.com/2010/05/reduce-your-pngs/</link>
		<comments>http://kieranchapmandesign.com/2010/05/reduce-your-pngs/#comments</comments>
		<pubDate>Fri, 14 May 2010 02:15:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=454</guid>
		<description><![CDATA[Compress Photoshop-generated PNG files]]></description>
			<content:encoded><![CDATA[<p>PNGs are pretty standard images on the web these days, but Photoshop tends to generate unnecessarily large files. And even though most people have high-speed access, any savings in image size is a good thing and will help speed page load times.</p>
<p><a href="http://www.brothersoft.com/pngthing-245069.html"><img class="alignleft size-full wp-image-456" title="PNG Thing" src="http://kieranchapmandesign.com/wp/wp-content/uploads/2010/05/pngthing.jpg" alt="PNG Thing" width="100" height="120" /></a>Enter <a href="http://www.brothersoft.com/pngthing-245069.html" target="_blank">PNG Thing for Mac</a>. Running your Photoshop-generated PNGs through PNG Thing reduces their size: just drag your images onto PNG Thing and strips out unnecessary junk, making your PNGs smaller. (It does a better job on large files and doesn&#8217;t make much of a dent with smaller PNGs.)</p>
<p><a href="http://mezzoblue.com/archives/2010/04/15/smaller_pngs/" target="_blank">Dave Shea</a> says Fireworks does an even better job of reducing PNGs. But if you don&#8217;t have Fireworks handy, PNG Thing is a nice (free) way to go.</p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2010/05/reduce-your-pngs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>yav Form Validation</title>
		<link>http://kieranchapmandesign.com/2010/04/yav-form-validation/</link>
		<comments>http://kieranchapmandesign.com/2010/04/yav-form-validation/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 19:17:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[UI]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=434</guid>
		<description><![CDATA[Make form validation (a little) easier with yav.]]></description>
			<content:encoded><![CDATA[<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">yav Form Validation</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">- Make form validation (a little) easier with yav.</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">Forms are a way for your site&#8217;s users to contact you, place orders, complete a survey — in general, provide you with important information. So, it&#8217;s very important that forms are clear, well-designed, and easy to use.</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">Validating online forms is a pain from a developer&#8217;s point of view, but necessary for a good user experience. If a user does make a mistake completing a form — such as omitting a required field or entering an invalid email address  — you want to let them know right away so they can fix it before submitting the data. And it&#8217;s best to show the error right away without refreshing the page or having to user search for what might be wrong. (A somewhat-old but still-relevant article by UIE is worth a read: &lt;a href=&#8221;http://www.uie.com/articles/form_design_wild/&#8221;&gt;Web Form Design in the Wild, Part II&lt;/a&gt;.)</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">&lt;a href=&#8221;http://yav.sourceforge.net/&gt;yav&lt;/a&gt; is Javascript form validation tool that does a great job handling form validation. It&#8217;s good for both simple validating (such as requiring a field or checking for a valid email address) and more complex rules (if your country = United States then require the State field; if your country = Canada, require province). You can even write custom Javascript functions if you need require even more specific validation rules.</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">yav also gives you options for displaying form errors. You can list the errors in a single section above the form, which works well with shorter forms:</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">IMAGE</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">You can also display error messages inline, which is better for longer forms. You don&#8217;t want users to have to search for their error, so calling out the error next to the field that needs correcting makes it easy to find:</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">IMAGE</div>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;">yav&#8217;s config settings let you change error message text, and you have total control over the look of the errors using CSS. The only downside is that it&#8217;s not terribly well-documented, so if you&#8217;re unfamiliar with Javascript you&#8217;ll probably require some trial &amp; error to get things to work like you want them.</div>
<p>Forms are a way for your site&#8217;s users to contact you, place orders, complete a survey — in general, provide you with important information. So, it&#8217;s very important that forms are clear, well-designed, and easy to use.</p>
<p>Validating online forms is a pain from a developer&#8217;s point of view, but necessary for a good user experience. If a user does make a mistake completing a form — such as omitting a required field or entering an invalid email address  — you want to let them know right away so they can fix it before submitting the data. And it&#8217;s best to show the error right away without refreshing the page or having to user search for what might be wrong. (A somewhat-old but still-relevant article by UIE is worth a read: <a href="http://www.uie.com/articles/form_design_wild" target="_blank">Web Form Design in the Wild, Part II</a>.)</p>
<p><a href="http://yav.sourceforge.net" target="_blank">yav</a> is Javascript form validation tool that does a great job handling form validation. It&#8217;s good for both simple validating (such as requiring a field or checking for a valid email address) and more complex rules (if your country = United States then require the State field; if your country = Canada, require province). You can even write custom Javascript functions if you need even more specific validation rules.</p>
<p>yav also gives you options for displaying form errors. You can list the errors in a single section above the form, which works well with shorter forms:</p>
<p><img class="alignnone size-large wp-image-445" style="border: 1px solid black;" title="yav-2" src="http://kieranchapmandesign.com/wp/wp-content/uploads/2010/04/yav-2-541x550.png" alt="yav-2" width="541" height="550" /></p>
<p>You can also display error messages inline, which is better for longer forms. You don&#8217;t want users to have to search for their error, so calling out the error next to the field that needs correcting makes it easy to find:</p>
<p><img class="alignnone size-large wp-image-444" style="border: 1px solid black;" title="yav-1" src="http://kieranchapmandesign.com/wp/wp-content/uploads/2010/04/yav-1-550x124.png" alt="yav-1" width="550" height="124" /></p>
<p>yav&#8217;s config settings let you change error message text, and you have total control over the look of the errors using CSS. The only downside is that it&#8217;s not terribly well-documented, so if you&#8217;re unfamiliar with Javascript you&#8217;ll probably require some trial &amp; error to get things to work like you want them.</p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2010/04/yav-form-validation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The End of IE6&#8230;Please!</title>
		<link>http://kieranchapmandesign.com/2010/01/the-end-of-ie6-please/</link>
		<comments>http://kieranchapmandesign.com/2010/01/the-end-of-ie6-please/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 11:52:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=409</guid>
		<description><![CDATA[People need to stop using IE6, but developers can't forget about it...yet.]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-411" src="http://kieranchapmandesign.com/wp/wp-content/uploads/2010/01/ie6_end.gif" alt="" width="300" height="129" />Over at ZDnet Ed Bott says <a href="http://blogs.zdnet.com/Bott/?p=1645" target="_blank">it&#8217;s time to stop using Internet Explorer 6</a>. Actually, people should have stopped using IE6 two or three years ago, but there are <em>still</em> people using it today.</p>
<p>Checking my server logs, I see that only 2-3% of people visiting my sites are still using IE6 — small enough that I can probably ignore them — but for some of my clients, that number runs around 5%. For these higher-trafficked sites, I can&#8217;t just ignore these users (as much as I&#8217;d like to). The sites don&#8217;t render perfectly as designed when using IE6, but they <em>do</em> have to work.</p>
<p>So until more of these people upgrade their archaic browser, I as a web developer need to keep testing the sites I build in IE6. But I think 2010 will be the last year I do that.</p>
<p>Are <em>you</em> still using IE6? <a href="http://www.microsoft.com/ie/" target="_blank">Upgrade it now</a> — it&#8217;s free! Or better yet, avoid security issues and download <a href="http://www.getfirefox.com/" target="_blank">Firefox</a> or <a href="http://www.apple.com/safari/" target="_blank">Safari</a> instead.</p>
<p><em>Related:</em> <a href="http://daringfireball.net/linked/2010/01/19/ie-security" target="_blank">France Joins Germany Warning Against Internet Explorer</a></p>
<p><em>Update:</em> Perhaps the end is beginning? <a href="http://arstechnica.com/microsoft/news/2010/02/ie6-users-to-be-evicted-from-gmail-google-calendar.ars" target="_blank">IE6 users to be evicted from Gmail, Google Calendar</a></p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2010/01/the-end-of-ie6-please/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Microsoft Word HTML Mess Cleaner</title>
		<link>http://kieranchapmandesign.com/2009/10/microsoft-html-cleaner/</link>
		<comments>http://kieranchapmandesign.com/2009/10/microsoft-html-cleaner/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 11:54:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=335</guid>
		<description><![CDATA[A tool to clean up Microsoft FrontPage- and IE-generated HTML]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re a web developer who&#8217;s had to deal with HTML code from Internet Explorer, FrontPage or Word then you know what a mess it can be. (And just calling it &#8220;mess&#8221; is being kind&#8230;) Next time you&#8217;ve got the unlucky task of wading through Microsoft-generated HTML, run it through <a href="http://www.algotech.dk/word-html-cleaner-input.htm" target="_blank">Microsoft Word 2000 HTML Mess Cleaner</a> first. It won&#8217;t make the code perfect, but it will clean things up well enough that you can actually find your way through it.</p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2009/10/microsoft-html-cleaner/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SEO: Common Sense for Web Developers</title>
		<link>http://kieranchapmandesign.com/2009/10/seo-common-sense-for-web-developers/</link>
		<comments>http://kieranchapmandesign.com/2009/10/seo-common-sense-for-web-developers/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 00:46:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=333</guid>
		<description><![CDATA[Real search engine optimization is part of good web development]]></description>
			<content:encoded><![CDATA[<p>Recently there was a bit of an uproar in the web developer community because of a blog post by Derek Powazek titled <a href="http://powazek.com/posts/2090" target="_blank">Spammers, Evildoers, and Opportunists</a>. In it he tears apart SEO (Search Engine Optimization) by saying, among other things, &#8220;Search Engine Optimization is not a legitimate form of marketing.&#8221; I mostly agreed with what he wrote, but only because I understood what he <i>meant</i>: good web development <i>includes</i> good SEO practices, plain and simple. A well-developed web site is easily found and read by search engine spiders. Shifty &#8220;SEO&#8221; companies that say they can guarantee top placement in search engines are probably using unethical linking tactics that aren&#8217;t SEO but instead are flat-out spamming &#8212; these are the &#8220;evildoers&#8221; who are ruining the web.</p>
<p>I think part of Derek&#8217;s problem was that he assumed everybody knows good common-sense web development practices. But as Danny Sullivan pointed out in <a href="http://searchengineland.com/an-open-letter-to-derek-powazek-on-the-value-of-seo-27680" target="_blank">An Open Letter To Derek Powazek On The Value Of SEO</a> &#8220;the stuff that you think isn&#8217;t rocket science &#8212; that anyone knows &#8212; is indeed a mystery to others.&#8221; I&#8217;m still surprised when I see sites coded poorly &#8212; bad page titles, using images instead of plain text, misuse of (or not using) header tags &#8212; but it reminds me that what Derek (and I) consider common sense web development just <i>isn&#8217;t</i> to many people. This is where legitimate SEO professionals come in to help clean up a sloppy or unknowing developer&#8217;s work.</p>
<p>Sullivan correctly notes that &#8220;sometimes [people] can&#8217;t find that web developer who also understands SEO issues. In the same way, you sometimes don&#8217;t find web developers who are also designers.&#8221; Sites I build are SEO-friendly without calling it that, simply because it&#8217;s the right way to build websites. Of course, once the site is up it&#8217;s up to you to add the most important part of any site: compelling content that brings people back to your site.</p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2009/10/seo-common-sense-for-web-developers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Display Your Logo with CSS</title>
		<link>http://kieranchapmandesign.com/2009/10/display-your-logo-with-css/</link>
		<comments>http://kieranchapmandesign.com/2009/10/display-your-logo-with-css/#comments</comments>
		<pubDate>Sat, 17 Oct 2009 14:42:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=261</guid>
		<description><![CDATA[A simple CSS tip to display your logo and keep your code clean and SEO-friendly]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a simple tip to use CSS for displaying your website&#8217;s logo (and any image in general). The HTML is about as basic as you can get:</p>
<div class="code">
&lt;h1&gt;&lt;a href=&#8221;/&#8221;&gt;My Great Website&lt;/a&lt;&gt;/h1&gt;
</div>
<p>The CSS to &#8220;hide&#8221; the text and display the logo image instead is pretty simple as well:</p>
<div class="code">
h1 {<br />
	width: 400px;<br />
	height: 100px;<br />
	background: url(/images/logo.gif) top left no-repeat;<br />
}</p>
<p>h1 a {<br />
	text-indent: -300em;<br />
	overflow: hidden;<br />
	float: left;<br />
	width: 400px;<br />
	height: 100px;<br />
}
</p></div>
<p>This styles the text and sets the height and width of the <tt>h1</tt> tag to the size of the logo, and displays the logo as a background image. The <tt>h1&nbsp;a</tt> style hides the text from the user (but not from search engines) by negative indenting the text and basically hiding it off-screen.</p>
<p>The result:</p>
<ul>
<li>very simple HTML code that&#8217;s easily read by search engines (better for SEO)</li>
<li>text that provides a correct representation of the logo (no ALT tag needed)
<li>design elements are kept separate from the code, making future updates easier (the image can be changed simply by modifying the CSS)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2009/10/display-your-logo-with-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Margin Doubling in IE6</title>
		<link>http://kieranchapmandesign.com/2009/09/margin-doubling-in-ie6/</link>
		<comments>http://kieranchapmandesign.com/2009/09/margin-doubling-in-ie6/#comments</comments>
		<pubDate>Tue, 29 Sep 2009 03:39:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://kieranchapmandesign.com/?p=324</guid>
		<description><![CDATA[A workaround for IE6's "mystery of the double-sized margin"...]]></description>
			<content:encoded><![CDATA[<p>This post is more of a note to myself so I don&#8217;t forget it (again) when battling IE 6. If you happen to find it useful, then I feel for you for dealing with that browser&#8230;</p>
<blockquote><p>If you have a floated element such as a div and you place margin-right or margin-left on that element, our most beloved Internet Explorer 6.0 will double that margin value, causing havoc in your html layout. To fix this simply add <code>display:inline;</code> to your floating element.</p></blockquote>
<p>(via <a href="http://www.jaymeblackmon.com/ie6-double-margin-bug-fix" target="_blank">Jayme Blackmon</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://kieranchapmandesign.com/2009/09/margin-doubling-in-ie6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

