<?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>Design Simply &#187; Code</title>
	<atom:link href="http://designsimply.com/category/code/feed/" rel="self" type="application/rss+xml" />
	<link>http://designsimply.com</link>
	<description>Simplicity in design, photography &#38; code.</description>
	<lastBuildDate>Mon, 21 Jun 2010 05:12:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>How to Setup Syntax Highlighting in MediaWiki</title>
		<link>http://designsimply.com/2008/06/16/how-to-setup-syntax-highlighting-in-mediawiki/</link>
		<comments>http://designsimply.com/2008/06/16/how-to-setup-syntax-highlighting-in-mediawiki/#comments</comments>
		<pubDate>Mon, 16 Jun 2008 16:41:17 +0000</pubDate>
		<dc:creator>Sheri Bigelow</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[mediawiki]]></category>

		<guid isPermaLink="false">http://designsimply.com/?p=141</guid>
		<description><![CDATA[Steps for setting up GeSHi (Generic Syntax Highlighter) on MediaWiki: Download GeSHi (Generic Syntax Highlighter). Upload geshi.php and the geshi folder to your MediaWiki extensions folder. Create GeSHiHighlight.php using this source code. Copy the following line to your LocalSettings.php file. include("extensions/GeSHiHighlight.php"); Add code to a MediaWiki page using &#60;pre&#62; tags. &#60;php&#62;&#60;?php echo "Hello World!"; ?&#62;&#60;/php&#62; [...]]]></description>
			<content:encoded><![CDATA[<p>Steps for setting up GeSHi (Generic Syntax Highlighter) on MediaWiki:</p>
<ol>
<li><a href="http://sourceforge.net/project/showfiles.php?group_id=114997">Download GeSHi</a> (Generic Syntax Highlighter).</li>
<li>Upload geshi.php and the geshi folder to your MediaWiki extensions folder.</li>
<li>Create GeSHiHighlight.php using <a href="http://embedded.seattle.intel-research.net/wiki/index.php?title=GeSHi#GeshiHighlight.php">this source code</a>.</li>
<li>Copy the following line to your LocalSettings.php file.
<pre>include("extensions/GeSHiHighlight.php");</pre>
</li>
<li>Add code to a MediaWiki page using &lt;pre&gt; tags.
<pre>&lt;php&gt;&lt;?php echo "Hello World!"; ?&gt;&lt;/php&gt;
</pre>
</li>
</ol>
<p>More information about GeSHI can be found at <a href="http://qbnz.com/highlighter/">http://qbnz.com/highlighter/</a>.</p>
<p>Edit: Oops. I had posted the last step with &lt;pre&gt; tags instead of &lt;php&gt;. I&#8217;ve fixed it now. Thanks override!</p>
]]></content:encoded>
			<wfw:commentRss>http://designsimply.com/2008/06/16/how-to-setup-syntax-highlighting-in-mediawiki/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>PHP::Impact Names Most Influential PHP Apps</title>
		<link>http://designsimply.com/2008/06/13/phpimpact-names-most-influential-php-apps/</link>
		<comments>http://designsimply.com/2008/06/13/phpimpact-names-most-influential-php-apps/#comments</comments>
		<pubDate>Sat, 14 Jun 2008 03:13:08 +0000</pubDate>
		<dc:creator>Sheri Bigelow</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[magento]]></category>

		<guid isPermaLink="false">http://designsimply.com/?p=125</guid>
		<description><![CDATA[PHP::Impact recently named sixteen PHP open source applications that have &#8220;changed the world&#8221; including two of my all-time favorite, much loved, and long used web phenomenons, WordPress and Gallery. Ten years running is a long time for the popular, pragmatic, database-wielding phpMyAdmin to have been in high demand—I had no idea phpMyAdmin had been around [...]]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-127 alignright" style="margin-left: 5px; margin-right: 5px;" title="magento_logo" src="http://designsimply.com/wp-content/uploads/2008/06/magento_logo.png" alt="Magento Logo" width="318" height="100" /><a href="http://phpimpact.wordpress.com/">PHP::Impact</a> recently named <a href="http://phpimpact.wordpress.com/2008/05/22/open-source-php-applications-that-changed-the-world/">sixteen PHP open source applications that have &#8220;changed the world&#8221;</a> including two of my all-time favorite, much loved, and long used web phenomenons, <a href="http://wordpress.org/">WordPress</a> and <a href="http://gallery.menalto.com/">Gallery</a>. Ten years running is a long time for the popular, pragmatic, <img class="size-full wp-image-126 alignleft" style="float: left;" title="wordpress_tattoo_logo" src="http://designsimply.com/wp-content/uploads/2008/06/wordpress_tattoo_logo.png" alt="Design by Baxter (endoflevelboss.org)" width="250" height="236" />database-wielding <a href="http://www.phpmyadmin.net/">phpMyAdmin</a> to have been in high demand—I had no idea phpMyAdmin had been around that long. I am also very impressed to see <a href="http://www.magentocommerce.com/">Magento eCommerce</a> on the list since it just <a href="http://www.magentocommerce.com/blog/comments/magento-10/">came out of beta this March</a>. So far, Magento is getting <a href="http://www.magentocommerce.com/blog/category/quotes/">rave reviews</a> and a <a href="http://en.wikipedia.org/wiki/Magento#Criticism">few complaints</a>. It will be interesting to see how these projects continue to evolve and <del>change</del> take over the world.</p>
]]></content:encoded>
			<wfw:commentRss>http://designsimply.com/2008/06/13/phpimpact-names-most-influential-php-apps/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>301 Redirects, Link Structure, XML Sitemaps, &amp; Preferred Domain</title>
		<link>http://designsimply.com/2007/08/24/301-redirects-link-structure-xml-sitemaps-preferred-domain/</link>
		<comments>http://designsimply.com/2007/08/24/301-redirects-link-structure-xml-sitemaps-preferred-domain/#comments</comments>
		<pubDate>Fri, 24 Aug 2007 09:55:33 +0000</pubDate>
		<dc:creator>Sheri Bigelow</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[301 redirects]]></category>

		<guid isPermaLink="false">http://designsimply.com/2007/08/25/set-your-preferred-domain-www-vs-non-www-indexphp-vs/</guid>
		<description><![CDATA[Google representative Matt Cutts advises using 301 redirects to establish a preferred www or non-www domain. URLs such as www.example.com, example.com, www.example.com/index.html, and example.com/home.asp all seem like they point to the same page, but all of them, in fact, could contain unique content. In order to cut down on a search engine cataloging said content [...]]]></description>
			<content:encoded><![CDATA[<p>Google representative Matt Cutts advises using 301 redirects to establish a <a href="http://www.mattcutts.com/blog/seo-advice-url-canonicalization/">preferred www or non-www domain</a>. URLs such as www.example.com, example.com, www.example.com/index.html, and example.com/home.asp all seem like they point to the same page, but all of them, in fact, could contain unique content. In order to cut down on a search engine cataloging said content more than one time, and therefore diluting search engine results pages (SERPs), you can use 301 redirects, a good internal link structure, xml sitemaps, and set your preferred domain in your Google Webmaster Central account.<span id="more-34"></span></p>
<h3>Using 301 Redirects</h3>
<p>A popular variation on the <a href="http://httpd.apache.org/docs/2.2/rewrite/rewrite_guide.html#canonicalhost">Canonical Hostnames Example in Apache&#8217;s URL Rewriting Guide</a> is to add the following to your root .htaccess file:</p>
<p><code>RewriteEngine on<br />
# Redirect index.php to /<br />
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /.*index\.php?\ HTTP/ [NC]<br />
RewriteRule ^(.*)index.php?$ http://www.example.com/$1 [R=301,L]<br />
# Redirect www to non-www (or reverse if you prefer www)<br />
RewriteCond %{HTTP_HOST} ^www.example.com$<br />
RewriteRule ^(.*)$ http://example.com/$1 [R=301,L]<br />
</code></p>
<p>One alternate method to use if you can&#8217;t get access to your .htaccess file is to use a php function like the one below. This would work great for a WordPress blog if you were to install it as the <em>first</em> line in your theme header.php file since it will be called for every page.</p>
<p><code>&lt;?php<br />
if ($_SERVER['HTTP_HOST']=='www.example.com' || $_SERVER['REQUEST_URI']=='/index.php') {<br />
header("HTTP/1.1 301 Moved Permanently");<br />
header('Location: ' . 'http://example.com/');<br />
} ?&gt;</code></p>
<h3>Good Internal Link Structure</h3>
<p>Make sure the links on your own site are consistent. If some of your links point to example.com and some point to www.example.com, there could be potential duplicate content issues. Pick the version you prefer and always use that format for your internal links.</p>
<h3>XML Sitemaps</h3>
<p>The <a href="http://www.sitemaps.org/protocol.php">sitemaps XML format</a> is explained at sitemaps.org. In November 2006, <a href="http://googlewebmastercentral.blogspot.com/2006/11/joint-support-for-sitemap-protocol.html">Google</a>, <a href="http://www.ysearchblog.com/archives/000380.html">Yahoo</a>, and <a href="http://blogs.msdn.com/livesearch/archive/2006/11/15/microsoft-google-yahoo-unite-to-support-sitemaps.aspx">Microsoft</a> announced autodiscovery support for sitemaps via robots.txt. By April 2007, <a href="http://googlewebmastercentral.blogspot.com/2007/04/whats-new-with-sitemapsorg.html">Google</a>, <a href="http://blog.ask.com/2007/04/sitemaps_autodi.html">Ask</a>, <a href="http://www.ysearchblog.com/archives/000437.html">Yahoo</a>, and <a href="http://blogs.msdn.com/livesearch/archive/2007/04/11/discovering-sitemaps.aspx">Microsoft</a> had all confirmed support for XML sitemaps. For autodiscovery, add the following line to your robots.txt file:</p>
<p><code>Sitemap: &lt;sitemap_location&gt;</code></p>
<p>Of course, you should make sure the links used in your XML sitemaps are well-formed and correctly pointing to your preferred domain. Make sure to keep your sitemap file up to date. You can find more information about how the top search engines&#8217; handle sitemaps including how to ping your sitemaps file or submit it manually using <a href="http://www.google.com/webmasters/">Google Webmaster Central</a> and <a href="http://siteexplorer.search.yahoo.com/">Yahoo Search Site Explorer</a>.</p>
<ul>
<li><a href="http://www.google.com/support/webmasters/bin/topic.py?topic=8467">Creating Google Sitemaps Files</a></li>
<li><a href="http://help.yahoo.com/help/us/ysearch/siteexplorer/siteexplorer-45.html">Yahoo Sitemap Support</a></li>
<li><a href="http://search.live.com/docs/siteowner.aspx?t=SEARCH_WEBMASTER_REF_GettingSiteIndexed.htm">Indexing on MSN Search</a></li>
<li><a href="http://about.ask.com/en/docs/about/webmasters.shtml#22">Ask.com Sitemap Suport</a></li>
</ul>
<p>Ping Addresses</p>
<ul>
<li>http://www.google.com/webmasters/tools/ping?sitemap=<br />
http%3A%2F%2Fwww.yoursite.com%2Fsitemap.gz</li>
<li>http://ping.feeds.yahoo.com/rss/ping?u=[THE URL OF YOUR FEED]</li>
<li>http://submissions.ask.com/ping?sitemap=http%3A//www.the URL of your sitemap here.xml</li>
</ul>
<p>Don&#8217;t forget about human readable site maps. Read <a href="http://searchengineland.com/070809-091501.php">Shari Thurow&#8217;s thoughts on the right way to think about site maps</a>.</p>
<h3>Set Your Preferred Domain in Google Webmaster Central</h3>
<p>In addition to adding an XML sitemap, you can set your preferred domain in Google Webmaster Central.</p>
<ul>
<li><a href="http://www.google.com/support/webmasters/bin/answer.py?answer=44232">How to set your preferred domain in Google</a>.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://designsimply.com/2007/08/24/301-redirects-link-structure-xml-sitemaps-preferred-domain/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SEOify Your WordPress with Description &amp; Keyword Meta Tags</title>
		<link>http://designsimply.com/2007/04/11/seoify-your-wordpress-with-description-keyword-meta-tags/</link>
		<comments>http://designsimply.com/2007/04/11/seoify-your-wordpress-with-description-keyword-meta-tags/#comments</comments>
		<pubDate>Thu, 12 Apr 2007 01:57:16 +0000</pubDate>
		<dc:creator>Sheri Bigelow</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[seoify]]></category>

		<guid isPermaLink="false">http://designsimply.com/2007/04/11/wordpress-description-keywords-meta-tags/</guid>
		<description><![CDATA[Ever wonder how to SEOify your WordPress install? Here&#8217;s the code I used in my WordPress theme to use custom fields for description and keywords meta tags. The down side to using this method is that you have to modify it for any new customized meta tags you want to use. I really only wanted [...]]]></description>
			<content:encoded><![CDATA[<p>Ever wonder how to SEOify your WordPress install? Here&#8217;s the code I used in my WordPress theme to use custom fields for description and keywords meta tags. The down side to using this method is that you have to modify it for any new customized meta tags you want to use. I really only wanted to customize the description and keywords meta tags, so this worked out great for me.<span id="more-27"></span></p>
<pre>&lt;?php
if (is_home()) {
   $description = "Default description of this website.";
   $keywords = "default, keyword, list";
} else {
   $description = get_post_meta($post-&gt;ID,'description',TRUE);
   $keywords = get_post_meta($post-&gt;ID,'keywords',TRUE);
}
if ($description) {
   echo "\\t&lt;meta name=\"description\" content=\"$description\" /&gt;\\n";
   }
if ($keywords) {
   echo "\\t&lt;meta name=\"keywords\" content=\"$keywords\" /&gt;\\n";
   }
?&gt;</pre>
<p>Here is another similar method:</p>
<pre>&lt;?php
  $pagetitle = get_post_meta($post-&gt;ID,'pagetitle',TRUE);
  $description = get_post_meta($post-&gt;ID,'description',TRUE);
  $keywords = get_post_meta($post-&gt;ID,'keywords',TRUE);
  if (empty($pagetitle)) {
    echo "&lt;title&gt;";
    wp_title('');
    echo " - ";
  } else {
    echo "&lt;title&gt;";
    if ($pagetitle!='') {echo "$pagetitle - ";}
  }
  bloginfo('name');
  echo "&lt;/title&gt;";
  if (!empty($description)) {
    echo "\\t&lt;meta name=\"description\" content=\"$description\" /&gt;\\n";
  }
  if (!empty($keywords)) {
    echo "\\t&lt;meta name=\"keywords\" content=\"$keywords\" /&gt;\\n";
  }
?&gt;</pre>
<p>Other meta tags, like character set, are hard coded into the main header.php code because they are the same on every page.</p>
<p>You can find more information about <a href="http://codex.wordpress.org/Using_Custom_Fields">Using Custom Fields on wordpress.org</a>. There are several <a href="http://codex.wordpress.org/Plugins/Meta">meta plugins listed on wordpress.org</a>, and a search for <a href="http://www.google.com/search?hl=en&amp;q=custom+fields+plugin+wordpress">custom fields plugins wordpress</a> on Google will return even more options.</p>
]]></content:encoded>
			<wfw:commentRss>http://designsimply.com/2007/04/11/seoify-your-wordpress-with-description-keyword-meta-tags/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
	</channel>
</rss>
