<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: A Simple CMS</title>
	<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/</link>
	<description></description>
	<pubDate>Mon, 01 Dec 2008 22:46:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Karl Voss</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-18817</link>
		<dc:creator>Karl Voss</dc:creator>
		<pubDate>Mon, 23 Jun 2008 18:51:13 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-18817</guid>
		<description>Maybe nanoc?

http://nanoc.stoneship.org/help/manual/chapter-1/</description>
		<content:encoded><![CDATA[<p>Maybe nanoc?</p>

<p><a href="http://nanoc.stoneship.org/help/manual/chapter-1/" rel="nofollow">http://nanoc.stoneship.org/help/manual/chapter-1/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bycco</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-18399</link>
		<dc:creator>bycco</dc:creator>
		<pubDate>Sat, 14 Jun 2008 15:54:54 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-18399</guid>
		<description>What about LTSun, snewscms or webyep?</description>
		<content:encoded><![CDATA[<p>What about LTSun, snewscms or webyep?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Ritchie</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15981</link>
		<dc:creator>Daniel Ritchie</dc:creator>
		<pubDate>Sat, 15 Mar 2008 01:00:27 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15981</guid>
		<description>Ian, I thought of you again, when I reached the end of the GoPHP5 projects list, and found [Thacmus](http://sourceforge.net/projects/thacmus/).</description>
		<content:encoded><![CDATA[<p>Ian, I thought of you again, when I reached the end of the GoPHP5 projects list, and found <a href="http://sourceforge.net/projects/thacmus/">Thacmus</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Ritchie</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15768</link>
		<dc:creator>Daniel Ritchie</dc:creator>
		<pubDate>Mon, 03 Mar 2008 12:27:45 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15768</guid>
		<description>I checked out [PureEdit.com](http://www.pureedit.com/) and found that a page on that site, built in PureEdit, is sitting open with world writeable edit feature.  I didn't look for more pages, and the other people who found it before me were nice about it too.  He's lucky.</description>
		<content:encoded><![CDATA[<p>I checked out <a href="http://www.pureedit.com/">PureEdit.com</a> and found that a page on that site, built in PureEdit, is sitting open with world writeable edit feature.  I didn&#8217;t look for more pages, and the other people who found it before me were nice about it too.  He&#8217;s lucky.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15699</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Fri, 29 Feb 2008 17:01:18 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15699</guid>
		<description>The reason Django isn't even close is that I'd like something that *I don't need to help maintain*.  With that in mind, Django is not even close.</description>
		<content:encoded><![CDATA[<p>The reason Django isn&#8217;t even close is that I&#8217;d like something that <em>I don&#8217;t need to help maintain</em>.  With that in mind, Django is not even close.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex V. Koval</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15696</link>
		<dc:creator>Alex V. Koval</dc:creator>
		<pubDate>Fri, 29 Feb 2008 15:32:15 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15696</guid>
		<description>Hello Ian,
despite your comment that Django "Not even remotely close." I tend to disagree. I've worked with Plone, Wiki (ZWiki), PHP, Perl, Wordpress, and a static tools (like Dreamweaver or MS Homesite). While I am software developer, it is interesting to see end-users reaction to things we do, and how easy they accept tools we provide. As far I've seen so far, things like Plone were easy to 'dive in', but difficult to change particular pars - its either works, or not. Wiki is too limited for a typical site like you require (and most users do). PHP is a thing from software development, and end user should have some knowelerge to use it. Also, PHP syntax and error handling are far from excellent. IMO, most acceptable were either Microsoft Front Page, or Django. Please don't be surprised, but the template system and ability to quickly prepare model &#38; represent it in page, with automated /admin/ is the thing users usually satisfied with. A typical "CMS" site have 2 models: ContentBlock (a block of text) and ContentList (a menu). That is more then enough to start, with a good devision on templates. As an example of such site, built in 3 days is here: http://www.urbanalarm.com/. It has been made in a 3 days for one of our customers, and they are happy. Or another 2 hours work is here (Russian): http://www.artmama.com.ua. Also, typical CMS. Allows to edit pictures, static pages, galleries and images. And worth to spend 3 hours of developer time to develop and set it up initially, and end users use it.
Alex</description>
		<content:encoded><![CDATA[<p>Hello Ian,
despite your comment that Django &#8220;Not even remotely close.&#8221; I tend to disagree. I&#8217;ve worked with Plone, Wiki (ZWiki), PHP, Perl, Wordpress, and a static tools (like Dreamweaver or MS Homesite). While I am software developer, it is interesting to see end-users reaction to things we do, and how easy they accept tools we provide. As far I&#8217;ve seen so far, things like Plone were easy to &#8216;dive in&#8217;, but difficult to change particular pars - its either works, or not. Wiki is too limited for a typical site like you require (and most users do). PHP is a thing from software development, and end user should have some knowelerge to use it. Also, PHP syntax and error handling are far from excellent. IMO, most acceptable were either Microsoft Front Page, or Django. Please don&#8217;t be surprised, but the template system and ability to quickly prepare model &amp; represent it in page, with automated /admin/ is the thing users usually satisfied with. A typical &#8220;CMS&#8221; site have 2 models: ContentBlock (a block of text) and ContentList (a menu). That is more then enough to start, with a good devision on templates. As an example of such site, built in 3 days is here: <a href="http://www.urbanalarm.com/." rel="nofollow">http://www.urbanalarm.com/.</a> It has been made in a 3 days for one of our customers, and they are happy. Or another 2 hours work is here (Russian): <a href="http://www.artmama.com.ua." rel="nofollow">http://www.artmama.com.ua.</a> Also, typical CMS. Allows to edit pictures, static pages, galleries and images. And worth to spend 3 hours of developer time to develop and set it up initially, and end users use it.
Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Dick</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15426</link>
		<dc:creator>Michael Dick</dc:creator>
		<pubDate>Mon, 18 Feb 2008 04:36:03 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-15426</guid>
		<description>http://www.pureedit.com -- All you need to do is build your database and PE does the rest, no strings attached. :).</description>
		<content:encoded><![CDATA[<p><a href="http://www.pureedit.com" rel="nofollow">http://www.pureedit.com</a> &#8212; All you need to do is build your database and PE does the rest, no strings attached. :).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Ritchie</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-14967</link>
		<dc:creator>Daniel Ritchie</dc:creator>
		<pubDate>Tue, 12 Feb 2008 16:48:56 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-14967</guid>
		<description>Probably more like [Coranto](http://www.coranto.org/ "LOL NewsPro!") aka (in the past) NewsPro.

But PHP/etc. (Coranto is mostly PERL), and yes, borrowing heavily from the newer concepts/patterns of OOP (Coranto is mostly procedural, but *cough*, it's legacy PERL)

Of course, I found this post a few days ago via the query, "simple php cms", and I'll vomit if I see one more MODULAR AJAX BLOGIKISCAFFOLD... since, as Ian seems to point out here, that road leads us in two directions:

1. You trap yourself and the user in a system of a system.
2. You begin to roll your own code into the system system, and if you or the system system are bad at it, your system system system is kludged.  See direction 1.

SO, as intrepid never-satisfied geeks, nerds, and dorks, we are (this was a random header text on some other page) ten years later still hand coding.

Personally, I'm new to rolling my own, so I'm looking into what PEAR and [CAKE](http://cakephp.org/ "OM NOM NOM") can do to accomplish this.</description>
		<content:encoded><![CDATA[<p>Probably more like <a href="http://www.coranto.org/" title="LOL NewsPro!">Coranto</a> aka (in the past) NewsPro.</p>

<p>But PHP/etc. (Coranto is mostly PERL), and yes, borrowing heavily from the newer concepts/patterns of OOP (Coranto is mostly procedural, but <em>cough</em>, it&#8217;s legacy PERL)</p>

<p>Of course, I found this post a few days ago via the query, &#8220;simple php cms&#8221;, and I&#8217;ll vomit if I see one more MODULAR AJAX BLOGIKISCAFFOLD&#8230; since, as Ian seems to point out here, that road leads us in two directions:</p>

<ol>
<li>You trap yourself and the user in a system of a system.</li>
<li>You begin to roll your own code into the system system, and if you or the system system are bad at it, your system system system is kludged.  See direction 1.</li>
</ol>

<p>SO, as intrepid never-satisfied geeks, nerds, and dorks, we are (this was a random header text on some other page) ten years later still hand coding.</p>

<p>Personally, I&#8217;m new to rolling my own, so I&#8217;m looking into what PEAR and <a href="http://cakephp.org/" title="OM NOM NOM">CAKE</a> can do to accomplish this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricardo Cabral</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-14891</link>
		<dc:creator>Ricardo Cabral</dc:creator>
		<pubDate>Tue, 12 Feb 2008 02:15:27 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-14891</guid>
		<description>Like http://www.pureedit.com/ ?</description>
		<content:encoded><![CDATA[<p>Like <a href="http://www.pureedit.com/" rel="nofollow">http://www.pureedit.com/</a> ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DMX</title>
		<link>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-14648</link>
		<dc:creator>DMX</dc:creator>
		<pubDate>Sun, 10 Feb 2008 16:28:14 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/02/05/a-simple-cms/#comment-14648</guid>
		<description>Check out CMS made simple. http://www.cmsmadesimple.org/

Its perfect for what I do with small clients. Smarty templates + CMS for all look and feel, you drop pages into it, organise them into the menus, and shazam, instant website. Its probably not so good for highly dynamical sites, but for "pamphlet" websites, its great, because its so easy, and because dumb-arse graphic designers can usually be taught smarty pretty well. 

And the fact that its not all portal-boxy or bloggy is a definate bonus.</description>
		<content:encoded><![CDATA[<p>Check out CMS made simple. <a href="http://www.cmsmadesimple.org/" rel="nofollow">http://www.cmsmadesimple.org/</a></p>

<p>Its perfect for what I do with small clients. Smarty templates + CMS for all look and feel, you drop pages into it, organise them into the menus, and shazam, instant website. Its probably not so good for highly dynamical sites, but for &#8220;pamphlet&#8221; websites, its great, because its so easy, and because dumb-arse graphic designers can usually be taught smarty pretty well. </p>

<p>And the fact that its not all portal-boxy or bloggy is a definate bonus.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
