<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Handcoded</title>
	
	<link>http://handcoded.ca</link>
	<description />
	<lastBuildDate>Thu, 07 Mar 2013 19:22:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/Handcoded" /><feedburner:info uri="handcoded" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Remove paragraph tags from images in WordPress</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/QIm2US5fEpk/</link>
		<comments>http://handcoded.ca/remove-paragraph-tags-from-images-in-wordpress/#comments</comments>
		<pubDate>Thu, 07 Mar 2013 19:20:14 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=2477</guid>
		<description><![CDATA[By default, WordPress wraps images in &#8216;p&#8217; tags. That is annoying. Here&#8217;s a nifty trick via jamesc on Stackoverflow for removing it. [crayon-519a863c0f500/] Save that to your wp-content/plugins folder and activate it via the dashboard.]]></description>
				<content:encoded><![CDATA[<p>By default, WordPress wraps images in &#8216;p&#8217; tags. That is annoying. Here&#8217;s a nifty trick via <a href="http://wordpress.stackexchange.com/users/2890/jamesc">jamesc</a> on <a title="Stop WordPress Wrapping Images In A “P” Tag" href="http://wordpress.stackexchange.com/questions/7090/stop-wordpress-wrapping-images-in-a-p-tag">Stackoverflow</a> for removing it.</p><pre class="crayon-plain-tag">&lt;?php
/*
Plugin Name: Image P tag remover
Description: Plugin to remove p tags from around images in content outputting, after WP autop filter has added them. (oh the irony)
Version: 1.0
Author: Fublo Ltd
Author URI: http://fublo.net/
*/

function filter_ptags_on_images($content)
{
    // do a regular expression replace...
    // find all p tags that have just
    // &lt;p&gt;maybe some white space&lt;img all stuff up to /&gt; then maybe whitespace &lt;/p&gt;
    // replace it with just the image tag...
    return preg_replace('/&lt;p&gt;\s*(&lt;a .*&gt;)?\s*(&lt;img .* \/&gt;)\s*(&lt;\/a&gt;)?\s*&lt;\/p&gt;/iU', '\1\2\3', $content);
}

// we want it to be run after the autop stuff... 10 is default.
add_filter('the_content', 'filter_ptags_on_images');</pre><p>Save that to your wp-content/plugins folder and activate it via the dashboard.</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/QIm2US5fEpk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/remove-paragraph-tags-from-images-in-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/remove-paragraph-tags-from-images-in-wordpress/</feedburner:origLink></item>
		<item>
		<title>Think about your privacy on social networking sites</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/DZMOpw1YgbQ/</link>
		<comments>http://handcoded.ca/social-networking-privacy/#comments</comments>
		<pubDate>Tue, 26 Jun 2012 20:50:46 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Social Networking]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=2434</guid>
		<description><![CDATA[A new website highlights the privacy risks inherent in social networking sites by aggregating actual user updates.]]></description>
				<content:encoded><![CDATA[<p>Social networking gives us a wide reach to broadcast information about ourselves and what we&#8217;re doing. But it&#8217;s easy to forget just who may be able to access what we&#8217;re posting, and how that may reflect on us as individuals. As Facebook&#8217;s recent <a rel="external" href="https://www.facebook.com/about/timeline">Timeline</a> update demonstrates, what we post to our social networks creates a long historic trail of data about our digital selves.</p>
<p>A story <a rel="external" href="http://thenextweb.com/shareables/2012/06/26/this-site-knows-exactly-what-youre-doing-thanks-to-public-facebook-and-foursquare-data/">posted this morning on <em>The Next Web</em></a> reported on a website that highlights just how little thinking goes into so much of what gets posted on social networks. The website, called &#8220;<a rel="external" href="http://www.weknowwhatyouredoing.com/">We Know What You&#8217;re Doing</a>&#8220;, aggregates publicly available data from Facebook and Foursquare to call out what can only be viewed as stupid behaviour. </p>
<p>The main page of the site shows a list of status updates from Facebook, divided into four categories: <strong>Who wants to get fired?</strong>, <strong>Who&#8217;s hungover?</strong>, <strong>Who&#8217;s taking drugs</strong>, and <strong>Who&#8217;s got a new phone number?</strong>. Using Facebook&#8217;s Graph API the site is able to pull in actual status updates for each category, complete with a profile photo, first name, and last initial for each user. (I&#8217;ve blacked out the names on the screenshot below, but they can be seen in full view on the site).</p>
<p><img src="http://handcoded.ca/wp-content/uploads/2012/06/wkwyd-screenshot.jpg" alt="&quot;We Know What You&#039;re Doing&quot; screenshot" title="&quot;We Know What You&#039;re Doing&quot; screenshot" class="aligncenter size-full wp-image-2435" /></p>
<p>In another section the site posts <a rel="external" href="http://www.weknowwhatyouredoing.com/locations/">actual Foursquare checkins</a> at users&#8217; homes, complete with a photograph of the house or apartment building from Google Streetview. And another section called &#8220;<a rel="external" href="http://www.weknowwhatyouredoing.com/myfriends/">Facebook friend checkins</a>&#8221; presumably does the same thing as the Foursquare section, but I was unable to access it without granting access to my own Facebook account (which I&#8217;m not prepared to do).</p>
<p>At the top of the page, the site proclaims in large type: &#8220;We know what you&#8217;re doing&hellip;&#8221;. Then at the bottom of the page it says: &#8220;&hellip;and we think you should stop.&#8221;</p>
<p>The creator of the site calls it an &#8220;experiment&#8221;, stating &#8220;This website is intended to demonstrate the privacy risks that social networking has&#8221;.</p>
<p>Indeed.</p>
<p>There are two main takeaways from this experiment:</p>
<p><strong>1) Use privacy controls</strong></p>
<p>You see those &#8220;Privacy Settings&#8221; on your account? Use them. In Facebook you can even create custom settings within your network, so that different &#8220;friends&#8221; within your network have different levels of access to what you post. And you can even do it on a post-by-post basis. (I don&#8217;t use Foursquare so I&#8217;m not sure what privacy options are available there, but if you use Foursquare, look into it.</p>
<p><img src="http://handcoded.ca/wp-content/uploads/2012/06/FBPrivacy.jpg" alt="" title="FBPrivacy" width="222" height="164" class="aligncenter size-full wp-image-2436" /></p>
<p><strong>2) Think before you post</strong></p>
<p>Even if you&#8217;ve adjusted your privacy settings, take a second to think about who might see your post, and how it might reflect on your reputation. I&#8217;m not saying you should censor yourself or pretend to be someone you&#8217;re not &#8211; I&#8217;m sure I&#8217;ve posted things before that have raised a few eyebrows. Just be prepared to explain your judgment if you have to, and to deal with any consequences.</p>
<p>As a general rule: don&#8217;t use social media to badmouth your boss, your company, your clients, or for that matter your friends or family members. Save those conversations for the pub or the dinner table (or better yet have a civil, face to face conversation with those concerned).</p>
<p>In short, use common sense.</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/DZMOpw1YgbQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/social-networking-privacy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/social-networking-privacy/</feedburner:origLink></item>
		<item>
		<title>Display http in Firefox</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/98LgSUMgTsE/</link>
		<comments>http://handcoded.ca/display-http-in-firefox/#comments</comments>
		<pubDate>Fri, 04 May 2012 21:23:55 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Browsers]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=2359</guid>
		<description><![CDATA[By default the <code>http://</code> protocol is not shown in the Firefox address bar, which is annoying and can lead to coding errors if you copy and paste a lot of urls into your HTML projects. Here's a quick fix to get it to display, and avoid future headaches.]]></description>
				<content:encoded><![CDATA[<p>Starting with Firefox version 7, <a href="http://en.wikipedia.org/wiki/Firefox#Version_7">the <code>http://</code> protocol indicator no longer appears in the url</a> by default. This means when you copy and paste the url from the address bar you get, for example, <code>www.domain.com</code> instead of the full <code>http://www.domain.com</code>.<br />
<img class="aligncenter size-full wp-image-2360" title="Firefox - no http protocol" src="http://handcoded.ca/wp-content/uploads/2012/05/nohttp-firefox.png" alt="Firefox - no http protocol" width="286" height="63" /><br />
For average users this is no big deal. But if you copy and paste urls into HTML code a lot, like I do, you need to manually enter <code>http://</code> each time. It&#8217;s tedious and annoying, and if you&#8217;re copying and pasting dozens or even hundreds of urls for a project it&#8217;s easy to miss a few. Then the links don&#8217;t work. And that&#8217;s even more annoying.</p>
<p>Fortunately there&#8217;s a fix for this – which is probably old news by now to some readers, since Firefox 7 was released in September 2011. But it&#8217;s still an issue today in version 12. It also bit me sort of hard yesterday when I left the <code>http://</code> out of a couple of links in an HTML email newsletter that was sent out to over 1,000 subscribers*.</p>
<p>So here&#8217;s how to display <code>http://</code> in Firefox:</p>
<p>Type <code>about:config</code> into the address bar.<br />
<img class="aligncenter size-full wp-image-2361" title="Firefox about:config" src="http://handcoded.ca/wp-content/uploads/2012/05/aboutconfig-firefox.png" alt="Firefox about:config" width="288" height="36" /><br />
Filter for <code>browser.urlbar.trimURLs</code>,<br />
<img class="aligncenter size-full wp-image-2362" title="Firefox browser.urlbar.trimURLs" src="http://handcoded.ca/wp-content/uploads/2012/05/browserurlbartrimURLs-firefox.png" alt="Firefox filter: browser.urlbar.trimURLs" width="720" height="82" /><br />
then double-click it, so it&#8217;s value turns to &#8220;false&#8221;.<br />
<img class="aligncenter size-full wp-image-2363" title="Firefox browser.urlbar.trimURLs - false" src="http://handcoded.ca/wp-content/uploads/2012/05/browserurlbartrimURLsfalse-firefox.png" alt="Firefox browser.urlbar.trimURLs - false" width="720" height="65" /><br />
And that takes care of that. Now the <code>http://</code> appears in the address bar, and will be included when you copy and paste the url.<br />
<img class="aligncenter size-full wp-image-2364" title="Firefox http displayed" src="http://handcoded.ca/wp-content/uploads/2012/05/yeshttp-firefox.png" alt="Firefox http displayed" width="293" height="62" /><br />
<small>* <strong>Regarding the email:</strong> I tested it using Outlook 2010, which apparently does not require <code>http://</code> in the code to recognize urls. So the links appeared to work just fine for me. But the editor of the newsletter uses Outlook 2003, which does require <code>http://</code>. So he noticed the error, but not before the email was sent. Gah!</p>
<p>(Email standards&hellip; C&#8217;mon! I&#8217;m sure I&#8217;ll have more to say on that subject in future posts&hellip;).</small></p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/98LgSUMgTsE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/display-http-in-firefox/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/display-http-in-firefox/</feedburner:origLink></item>
		<item>
		<title>Open links in a new window with jQuery</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/2UF7AzJsW6k/</link>
		<comments>http://handcoded.ca/open-links-in-a-new-window-with-jquery/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 20:17:19 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=2240</guid>
		<description><![CDATA[Using <code>target="_blank"</code> to open new windows in XHTML will generate a validation error. This snippet uses jQuery instead to open the links in a new window, and ensures that your code still validates.]]></description>
				<content:encoded><![CDATA[<p>It is possible to open links in a new window by adding <code>target="_blank"</code> to the anchor tag in HTML, but if your page uses the XHTML doctype it will generate a validation error. The following snippet uses JavaScript instead to open the link in a new window, and keeps your XHTML valid.</p>
<p>Make sure you have jQuery loaded, then include this in your JavaScript file:</p>
<p></p><pre class="crayon-plain-tag">$('a[rel="external"]')
    .click( function() {
    window.open( $(this).attr('href') );
    return false;
  });</pre><p></p>
<p>Now you just need to add <code>rel="external"</code> to any anchor tags that you want to open in a new window (e.g. <code>&lt;a href=&quot;somedomain.com&quot; rel=&quot;external&quot;&gt;some link text&lt;/a&gt;</code>).</p>
<p><em>(<strong>Update:</strong> Apparently <a rel="external" href="http://stackoverflow.com/questions/4198788/is-it-alright-use-to-target-blank-in-html5">using <code>target="_blank"</code> is valid in HTML5</a>. But this JavaScript method will still work too).</em></p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/2UF7AzJsW6k" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/open-links-in-a-new-window-with-jquery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/open-links-in-a-new-window-with-jquery/</feedburner:origLink></item>
		<item>
		<title>Custom WordPress widget PHP code snippet</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/EvPyVX8EQSo/</link>
		<comments>http://handcoded.ca/custom-wordpress-widget-php-code-snippet/#comments</comments>
		<pubDate>Wed, 25 Apr 2012 19:25:50 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=2236</guid>
		<description><![CDATA[Add this to your functions.php file: [crayon-519a863c14ab4/] Then add this the theme file(s) where you want the Widget to appear: [crayon-519a863c14afa/] Now when you go the Widget manager in your WordPress Admin you can add some widgets.]]></description>
				<content:encoded><![CDATA[<p>Add this to your <code>functions.php</code> file:</p><pre class="crayon-plain-tag">// Register widgets
if (function_exists('register_sidebar')) {
   register_sidebar(array(
        'name' =&gt; __('Widget Name'), // Change this to your own name
        'id'   =&gt; 'widget-id', // Change this to your own id
        'description'   =&gt; __( 'This is a custom widget.' ), // Change this to your own description
        'before_widget' =&gt; '&lt;div id="%1$s" class="%2$s"&gt;',
        'after_widget'  =&gt; '&lt;/div&gt;',
        'before_title'  =&gt; '&lt;h3&gt;',
        'after_title'   =&gt; '&lt;/h3&gt;'
     ));
}</pre><p>Then add this the theme file(s) where you want the Widget to appear:</p><pre class="crayon-plain-tag">&lt;?php   /* Widgetized area. */
if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('Widget Name') ) : ?&gt; // Match 'Widget Name' with the name of the registered Widget you are using.
         // Some text to display when no widgets have been added.
         &lt;h3&gt;Widget Area!&lt;/h3&gt;
         &lt;p&gt;This is a Widgetized section.&lt;/p&gt;
         &lt;p&gt;If you can see this you need to go to &lt;strong&gt;Appearance &gt; Widgets&lt;/strong&gt; in your WordPress admin and add some widgets.&lt;/p&gt;
&lt;?php endif; ?&gt;</pre><p></p>
<p>Now when you go the Widget manager in your WordPress Admin you can add some widgets.</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/EvPyVX8EQSo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/custom-wordpress-widget-php-code-snippet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/custom-wordpress-widget-php-code-snippet/</feedburner:origLink></item>
		<item>
		<title>Track PDF downloads with Google Analytics</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/5EdGYexErGc/</link>
		<comments>http://handcoded.ca/track-pdf-downloads-with-google-analytics/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 20:31:50 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Code Snippets]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=2232</guid>
		<description><![CDATA[Use this code to track PDF downloads (or other non-HTML files) with Google Analytics. Be sure to change myfile to your actual filename, both in the url and the tracking code. [crayon-519a863c153a3/] Now when the visitor clicks the link to download the file, Google Analytics will record it as a pageview. By prefixing each file [...]]]></description>
				<content:encoded><![CDATA[<p>Use this code to track PDF downloads (or other non-HTML files) with Google Analytics. Be sure to change <code>myfile</code> to your actual filename, both in the url and the tracking code.</p>
<p></p><pre class="crayon-plain-tag">&lt;a href="http://www.mydomain.com/myfile.pdf" onClick="javascript: _gaq.push(['_trackPageview', '/downloads/myfile']);"&gt;</pre><p></p>
<p>Now when the visitor clicks the link to download the file, Google Analytics will record it as a pageview. By prefixing each file name with <code>/downloads/</code>, you can then easily identify and filter these pageviews in your Google Analytics reports.</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/5EdGYexErGc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/track-pdf-downloads-with-google-analytics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/track-pdf-downloads-with-google-analytics/</feedburner:origLink></item>
		<item>
		<title>Want good SEO? Be trustworthy, genuine &amp; relevant</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/mWhb3d-Pstk/</link>
		<comments>http://handcoded.ca/want-good-seo-be-trustworthy-genuine-relevant/#comments</comments>
		<pubDate>Fri, 23 Sep 2011 20:11:35 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://robgolbeck.com/?p=1537</guid>
		<description><![CDATA[Developer Matt Gemmell, writing on ethically questionable Search Engine Optimisation tactics:  &#34;(T)he rules of SEO aren’t magic or arbitrary. They’re based on the goals of a search engine, which is to find relevant results. Relevance implies genuineness, and genuineness implies trust &#8230; &#34;]]></description>
				<content:encoded><![CDATA[<p>Developer <a href="http://mattgemmell.com/">Matt Gemmell</a>, writing on <a href="http://mattgemmell.com/2011/09/20/seo-for-non-dicks/">ethically questionable Search Engine Optimisation tactics</a>:</p>
<blockquote><p>
 <em>(T)he rules of SEO aren’t magic or arbitrary. They’re based on the goals of a search engine, which is to</em> find relevant results<em>. Relevance implies</em> genuineness<em>, and genuineness implies</em> trust<em>. So, shockingly, you should try to make your site’s content </em>trustworthy, genuine and relevant<em>. All of the rules have come about due to their utility in detecting those three positive metrics. <a href="http://mattgemmell.com/2011/09/20/seo-for-non-dicks/">Good SEO is a by-product of not being a dick on the internet</a>.</em>
</p></blockquote>
<p>Well said.</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/mWhb3d-Pstk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/want-good-seo-be-trustworthy-genuine-relevant/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/want-good-seo-be-trustworthy-genuine-relevant/</feedburner:origLink></item>
		<item>
		<title>The benefits of WordPress for Your Website or Blog</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/qzENivU5rx8/</link>
		<comments>http://handcoded.ca/benefits-of-wordpress-for-your-website-or-blog/#comments</comments>
		<pubDate>Thu, 14 Apr 2011 18:52:58 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=1278</guid>
		<description><![CDATA[WordPress is the software I recommend and use for all the websites I build for my freelance clients. I&#8217;ve used other open-source platforms like Drupal and Joomla!, and while I have nothing against them or the sites and developers that prefer them, I believe WordPress is the best open-source content management option for small businesses, [...]]]></description>
				<content:encoded><![CDATA[<p>WordPress is the software I recommend and use for all the websites I build for my freelance clients. I&#8217;ve used other open-source platforms like <a href="http://drupal.org/">Drupal</a> and <a href="http://www.joomla.org/">Joomla!</a>, and while I have nothing against them or the sites and developers that prefer them, I believe WordPress is the best open-source content management option for small businesses, organizations and individuals. In this post I explain why.</p>
<p>First I should clarify that I&#8217;m talking about the self-hosted version of WordPress, which is the open-source software package that users download from WordPress<em>.org</em> and host on their own server. There&#8217;s another version at WordPress<em>.com</em>, which is a commercial blogging service hosted by <a href="http://automattic.com/">Automattic</a>. Both run the same software, but apart from that they&#8217;re quite different. (There&#8217;s a comparison of the two versions at <a href="http://en.support.wordpress.com/com-vs-org/">http://en.support.wordpress.com/com-vs-org/</a>, if you want to know more.)</p>
<p>Here are what I find the major benefits of WordPress to be, and why I think you should consider using it for your website or blog:</p>
<h4>It&#8217;s free</h4>
<p>WordPress costs nothing more than the time it takes to download the software from WordPress.org and install it on your server. In return you&#8217;ll get a powerful, highly functional content management system for your website or blog.</p>
<h4>It&#8217;s easy to set up and manage</h4>
<p>Once you&#8217;ve downloaded the software, you can have a functioning website <a href="http://codex.wordpress.org/Installing_WordPress#Famous_5-Minute_Install">in a matter of minutes</a>, and the WYSIWYG editor makes it easy to publish your content without touching a single line of code.</p>
<h4>It&#8217;s extensible</h4>
<p>WordPress is essentially a framework that is meant to be built upon and improved. There is a huge collection of WordPress themes and plugins available for customizing the design and functionality of your site with the click of a button (literally). If you want to change the &#8216;skin&#8217;, or design of your site, simply activate a new theme from the Appearance menu in the dashboard. And if you need to add some extra features like photo galleries, integration with your Twitter feed or Facebook page, or give your site enhanced security, there are plugins that will do that for you.</p>
<h4>It can be a website, a blog, or both</h4>
<p>WordPress began as a popular blogging platform, but has grown into a powerful content management system capable of managing entire websites, too. Removing the blog from the homepage, or taking it off your website entirely, is simply a matter of choosing the appropriate setting from the dashboard.</p>
<h4>It&#8217;s search engine friendly</h4>
<p>WordPress is built with clean, semantic code that makes it easy for search engines to index your content. It also comes with built in tools such as custom &#8220;permalinks&#8221; that let you highlight relevant keywords and phrases in your urls, which search engines like too. And many premium themes come with options to add custom page titles and meta descriptions to your posts and pages &ndash; both important elements for search engine optimization. And if your theme doesn&#8217;t come with these options already, there are several good SEO plugins available that will add this functionality.</p>
<h4>It&#8217;s well supported</h4>
<p>WordPress is open-source software, backed by a massive community of passionate designers, developers and general enthusiasts from around the world who are working to make sure the software only improves with each new release. WordPress is also very <a href="http://codex.wordpress.org/">well documented</a>, and the <a href="http://wordpress.org/support/">support forums</a> are an invaluable resource for finding solutions to problems, as well as getting (and giving) tips and tricks.</p>
<p>What do you think? Agree? Disagree? Got anything to add? Let me know in the comments!</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/qzENivU5rx8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/benefits-of-wordpress-for-your-website-or-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://handcoded.ca/benefits-of-wordpress-for-your-website-or-blog/</feedburner:origLink></item>
		<item>
		<title>A simple way to choose a colour scheme</title>
		<link>http://feedproxy.google.com/~r/Handcoded/~3/tXc2422qYhU/</link>
		<comments>http://handcoded.ca/a-simple-way-to-choose-a-colour-scheme/#comments</comments>
		<pubDate>Fri, 16 Jul 2010 20:38:20 +0000</pubDate>
		<dc:creator>Rob Golbeck</dc:creator>
				<category><![CDATA[Colour]]></category>

		<guid isPermaLink="false">http://handcoded.ca/?p=823</guid>
		<description><![CDATA[If you&#8217;re colour challenged like me, choosing the colours to use in a web project can be tricky. Here&#8217;s a simple method that might help. To do this, you&#8217;ll need Photoshop and a picture, preferably one that is significant to your project (like a banner). If you&#8217;re project doesn&#8217;t use any pictures, find one with [...]]]></description>
				<content:encoded><![CDATA[<p>If you&#8217;re colour challenged like me, choosing the colours to use in a web project can be tricky. Here&#8217;s a simple method that might help.</p>
<p>To do this, you&#8217;ll need Photoshop and a picture, preferably one that is significant to your project (like a banner). If you&#8217;re project doesn&#8217;t use any pictures, find one with a few general colours that you think could work.</p>
<p>Open your picture in Photoshop. For this demonstration I&#8217;m using the banner from <a href="http://robgolbeck.com">my personal site</a>. I&#8217;m planning to revise that site soon anyhow, so this might give me a head start.</p>
<div align="center">
<img src="http://handcoded.ca/i/open-photo.jpg" alt="" />
</div>
<p>Select <strong>Filter &gt; Pixelate &gt; Mosaic</strong> from the main menu.</p>
<div align="center">
<img src="http://handcoded.ca/i/pixelate-mosaic.jpg" alt="" />
</div>
<p>Change the cell size to increase the pixels of each colour square. The larger the pixels, the fewer colours you&#8217;ll get. Play around with it until you get a range you like. Keep in mind what each colour will be used for (backgrounds, headings, link states, etc.). This will help you decide how many colours you need in the palette.</p>
<div align="center">
<img src="http://handcoded.ca/i/mosaic-cell-size.jpg" alt="" />
</div>
<p>Click OK, and presto! You have a colour scheme.</p>
<div align="center">
<img src="http://handcoded.ca/i/palette.jpg" alt="" />
</div>
<p>Now all you need to do is use the eyedropper tool to get the hex codes for each colour.</p>
<p>Schweet.</p>
<img src="http://feeds.feedburner.com/~r/Handcoded/~4/tXc2422qYhU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://handcoded.ca/a-simple-way-to-choose-a-colour-scheme/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://handcoded.ca/a-simple-way-to-choose-a-colour-scheme/</feedburner:origLink></item>
	</channel>
</rss>
