<?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>Rob@Rojotek &#187; Content Management</title>
	<atom:link href="http://www.rojotek.com/blog/blog/content-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rojotek.com/blog</link>
	<description>Software Development in Brisbane</description>
	<lastBuildDate>Wed, 25 Jan 2012 10:34:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Drupal First Impressions</title>
		<link>http://www.rojotek.com/blog/2008/01/01/drupal-first-impressions/</link>
		<comments>http://www.rojotek.com/blog/2008/01/01/drupal-first-impressions/#comments</comments>
		<pubDate>Tue, 01 Jan 2008 22:49:04 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[Content Management]]></category>
		<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://www.rojotek.com/blog/2008/01/01/drupal-first-impressions/</guid>
		<description><![CDATA[As I recently posted, I’ve been using wordpress everywhere currently. It is simple and easy to use. I am, however, always prepared to learn new things, and use the appropriate tools for a job. So, after hearing drupal come up as an open source CMS at the CMPros summit in Boston, I figured that I’d [...]]]></description>
			<content:encoded><![CDATA[<p>
       As I recently posted, I’ve been using <a href="http://www.rojotek.com/blog/2007/11/26/wordpress-everywhere/">wordpress everywhere</a> currently. It is simple and easy to use. I am, however, always prepared to learn new things, and use the appropriate tools for a job. So, after hearing drupal come up as an open source <span class="caps">CMS</span> at the <a href="http://www.cmpros.org/">CMPros</a> summit in Boston, I figured that I’d try it out.
    </p>
<p>
       The basic install process was pretty straight forward. Download and untar the install available from <a href="http://drupal.org">drupal.org</a>. I created the user for the database on my mysql instance, and followed the simple install guide to get it up and running, which finished with me having created an admin account and logging in as admin.
    </p>
<p>
       After completing the basic install, it was relatively easy to go and create content. The front page includes a create content link available, making it easy to create <strong>stories</strong> and static <strong>pages</strong>. I could go in and do this quickly, and get some nice rapid gratification by creating content. Unfortunately the urls were kinda ugly and drupalish. I wasn’t happy, figured that someone had to have come up with a way to do nice urls. I started with a quick look at the admins screen, and almost ran away after seeing the huge number of options.
    </p>
<p>
       <a title="Drupal Admin Screens" href="http://www.rojotek.com/blog/wp-content/uploads/2008/01/drupal_admin.png"><img src="http://www.rojotek.com/blog/wp-content/uploads/2008/01/drupal_admin.thumbnail.png" alt="Drupal Admin Screens" /></a>
    </p>
<p>
       Google came to the rescue, and I downloaded the <a href="http://drupal.org/project/pathauto">pathauto</a> tool, and started reading documentation. Getting the friendly urls definately isn’t as easy as in wordpress. I had to go in and edit the .htaccess and set the path option:</p>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><table cellspacing="0" cellpadding="0"><tbody><tr><td style="padding:5px;text-align:center;color:#888888;background-color:#EEEEEE;border-right: 1px solid #9F9F9F;font: normal 12px/1.4em Monaco, Lucida Console, monospace;"><div>1<br /></div></td><td><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">&amp;#160;RewriteBase /~rob/drupal-5.3</div></td></tr></tbody></table></div>
</p>
<p>
       Installing a module is pretty straight forward, and simply consists of copying it into the modules directory. It is then enabled through the gui, using: Administer&#62;Modules. When I did this for pathauto I noticed dependancies on the path, and token modules, which needed to be resolved before pathauto could be run.
    </p>
<p>
       As token wasn’t installed by default I had to pause my installation of pathauto. So I was left with exploring path, and the rest of drupal. Path actually works ok. It makes it easy to specify friendly urls for your pages and stories, via a simple text field.
    </p>
<p>
       Pathauto works pretty well to. After getting it installed (just unpackaging the tars for pathauto and node into the modules directory) I was easily able to update the configuration to ensure friednly paths are created. Functionally this ends up making the urls work as well as wordpress. The admin interface also provides heaps of additional options (which I didn’t really need).
    </p>
<p>
       I’ve started putting together a proof-of-concept module for <a href="http://www.ephox.com/products/editlive">EditLive!</a> as well. After some input from the legendary support engineer (<a href="http://slackcoders.com/suneth/">Suneth</a>), we got this working.
    </p>
<p>
       Overall drupal seems to be much more powerful that wordpress. Like wordpress has a rich module system, allowing people to customise and enrich their installation. It is a good enough system, and while I don’t plan on replacing my wordpress installations with it, I can see that it may be useful for bigger sites.
    </p>
]]></content:encoded>
			<wfw:commentRss>http://www.rojotek.com/blog/2008/01/01/drupal-first-impressions/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

