<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Welcome to the New Quark VS InDesign.com</title>
	<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/</link>
	<description>The Authority for News &#038; Opinion on the War of the Desktop Publishing Giants QuarkXPress and Adobe InDesign</description>
	<pubDate>Tue, 06 Jan 2009 13:40:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: csmef</title>
		<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-26718</link>
		<pubDate>Thu, 21 Jun 2007 11:42:13 +0000</pubDate>
		<guid>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-26718</guid>
					<description>Canton Fair, general information about the China Export Commodites Fair (canton fair). Services includes Canton Fair guide, discount hotel booking, trip advice and interpreter.</description>
		<content:encoded><![CDATA[<p>Canton Fair, general information about the China Export Commodites Fair (canton fair). Services includes Canton Fair guide, discount hotel booking, trip advice and interpreter.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Joe</title>
		<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16814</link>
		<pubDate>Fri, 15 Sep 2006 15:33:20 +0000</pubDate>
		<guid>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16814</guid>
					<description>Hey &lt;strong&gt;Mambo&lt;/strong&gt;, &lt;strong&gt;Mambo&lt;/strong&gt; Itialiano.</description>
		<content:encoded><![CDATA[<p>Hey <strong>Mambo</strong>, <strong>Mambo</strong> Itialiano.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: woz</title>
		<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16809</link>
		<pubDate>Thu, 14 Sep 2006 06:54:16 +0000</pubDate>
		<guid>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16809</guid>
					<description>LOL! Love the new layout. The posting of a reaction is also a lot easier. The new loayout is a bit less "present" on my desktop when I 'take a short break from work ;-)
I read your article about Joomla. My own site is Joomla driven and I totally agree that there's not enough documentation! It's all "in-crowd php programmers" stuff. And right now I'm facing the upgrading of my site for the 3rd!! time in a few months just for security reasons. (Previous versions of Joomla were easily hackable). This last one, .11 required manually tweaking the config.php. Anyone that would simply update via ftp and not do the tweaking bit, would see their site crashing. Even now you had to go looking for clues in the Joomla forum. No documentation... (Thank God for backups!)
My site's not big but it's a DTP focus site that focusses on InDesign / PDF / Certified DTP (in Dutch). I'll have a look at Wordpress. The MacnightOwl.com is also a very happy WordPress user.</description>
		<content:encoded><![CDATA[<p>LOL! Love the new layout. The posting of a reaction is also a lot easier. The new loayout is a bit less &#8220;present&#8221; on my desktop when I &#8216;take a short break from work ;-)<br />
I read your article about Joomla. My own site is Joomla driven and I totally agree that there&#8217;s not enough documentation! It&#8217;s all &#8220;in-crowd php programmers&#8221; stuff. And right now I&#8217;m facing the upgrading of my site for the 3rd!! time in a few months just for security reasons. (Previous versions of Joomla were easily hackable). This last one, .11 required manually tweaking the config.php. Anyone that would simply update via ftp and not do the tweaking bit, would see their site crashing. Even now you had to go looking for clues in the Joomla forum. No documentation&#8230; (Thank God for backups!)<br />
My site&#8217;s not big but it&#8217;s a DTP focus site that focusses on InDesign / PDF / Certified DTP (in Dutch). I&#8217;ll have a look at Wordpress. The MacnightOwl.com is also a very happy WordPress user.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Pariah S. Burke</title>
		<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16793</link>
		<pubDate>Wed, 13 Sep 2006 20:45:57 +0000</pubDate>
		<guid>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16793</guid>
					<description>Just a quick note: Because the new Quark VS InDesign.com launched late on Tuesday, we\'re holding the Tip o\' the Day over through today, Wednesday. A new one will appear on Thursday the 13th.</description>
		<content:encoded><![CDATA[<p>Just a quick note: Because the new Quark VS InDesign.com launched late on Tuesday, we\&#8217;re holding the Tip o\&#8217; the Day over through today, Wednesday. A new one will appear on Thursday the 13th.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Pariah S. Burke</title>
		<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16792</link>
		<pubDate>Wed, 13 Sep 2006 19:39:26 +0000</pubDate>
		<guid>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16792</guid>
					<description>I\'m glad you like the new layout, Woz!

LOL I should have known someone astute would find that! I commented it out because it just didn\'t fit with the tone of the new site announcement.

After I wrote &lt;a href=\"http://designorati.com/web-design/editorial-110/2006/joomla-content-management-system-making-open-source-proprietary/\" rel=\"nofollow\" rel="nofollow"&gt;this article on Joomla&lt;/a&gt;, I spent eight weeks teaching it to myself. Because of the lack of documentation, I had to learn how Joomla worked and how I could use it by reading all the PHP code and figuring what functions were there and what they did. After having the database converted and roughly 80% of the new site built in Joomla through trial and error, I discovered that the self-proclaimed \"world\'s greatest CMS\" had major flaws and missing functions in its core. Worse, even the most experienced third-party add-on makers couldn\'t fill the holes because they would have to rewrite massive sections of Joomla\'s core code in the process.

Once you figure out how to use and customize it, Joomla is a great product for managing small amounts of content in closed arenas like corporate intranets and membership sites. It\'s no where near ready to manage a publicly-accessible, content-driven Website.

Mambo, being the same codebase as Joomla, is the same way. Drupal and other open source CMSes were better documented, but suffered from the same problem: They were developed to manage small sites with minimal reader interaction.

Some of the ASP .Net CMS systems looked quite interesting, but I don\'t want to move to Windows Web servers.

In the end, the personal blog software WordPress was the best choice as a core. It had the fundamentals needed to be a solid CMS, and, more importantly, enabled itself to be extended into one without rewriting massive portions of its core; I could just build &lt;em&gt;on top of&lt;/em&gt; WordPress, which is an important consideration because it means we\'re not stuck rewriting every time a needed WordPress upgrade is released.

&lt;blockquote&gt;Will you also be selling the finished product? ;-) &lt;/blockquote&gt;

I would like to eventually. With the exception of a couple of little elements and functions that I want to touch up, it\'s just about ready for deployment on any site. I\'ve got a name for it: Workflow:WebPublish Content Management System.

Now, whether I will actually get around to packaging it and putting it out there... At the moment, I\'ve just got too many other projects going. Hopefully in the near future I\'ll get Workflow:WebPublish out there for sale.</description>
		<content:encoded><![CDATA[<p>I\&#8217;m glad you like the new layout, Woz!</p>
<p>LOL I should have known someone astute would find that! I commented it out because it just didn\&#8217;t fit with the tone of the new site announcement.</p>
<p>After I wrote <a href=\"http://designorati.com/web-design/editorial-110/2006/joomla-content-management-system-making-open-source-proprietary/\" rel=\"nofollow\" rel="nofollow">this article on Joomla</a>, I spent eight weeks teaching it to myself. Because of the lack of documentation, I had to learn how Joomla worked and how I could use it by reading all the PHP code and figuring what functions were there and what they did. After having the database converted and roughly 80% of the new site built in Joomla through trial and error, I discovered that the self-proclaimed \&#8221;world\&#8217;s greatest CMS\&#8221; had major flaws and missing functions in its core. Worse, even the most experienced third-party add-on makers couldn\&#8217;t fill the holes because they would have to rewrite massive sections of Joomla\&#8217;s core code in the process.</p>
<p>Once you figure out how to use and customize it, Joomla is a great product for managing small amounts of content in closed arenas like corporate intranets and membership sites. It\&#8217;s no where near ready to manage a publicly-accessible, content-driven Website.</p>
<p>Mambo, being the same codebase as Joomla, is the same way. Drupal and other open source CMSes were better documented, but suffered from the same problem: They were developed to manage small sites with minimal reader interaction.</p>
<p>Some of the ASP .Net CMS systems looked quite interesting, but I don\&#8217;t want to move to Windows Web servers.</p>
<p>In the end, the personal blog software WordPress was the best choice as a core. It had the fundamentals needed to be a solid CMS, and, more importantly, enabled itself to be extended into one without rewriting massive portions of its core; I could just build <em>on top of</em> WordPress, which is an important consideration because it means we\&#8217;re not stuck rewriting every time a needed WordPress upgrade is released.</p>
<blockquote><p>Will you also be selling the finished product? ;-) </p></blockquote>
<p>I would like to eventually. With the exception of a couple of little elements and functions that I want to touch up, it\&#8217;s just about ready for deployment on any site. I\&#8217;ve got a name for it: Workflow:WebPublish Content Management System.</p>
<p>Now, whether I will actually get around to packaging it and putting it out there&#8230; At the moment, I\&#8217;ve just got too many other projects going. Hopefully in the near future I\&#8217;ll get Workflow:WebPublish out there for sale.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: woz</title>
		<link>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16791</link>
		<pubDate>Wed, 13 Sep 2006 12:06:28 +0000</pubDate>
		<guid>http://quarkvsindesign.com/announcements/press-releases/2006/letter-from-the-editor-welcome-to-the-new-quark-vs-indesigncom/#comment-16791</guid>
					<description>Well, it works for me! Love the new layout. Who actually won the contest, btw? Your CSM smells like Joomla, but in your code is this: &lt;blockquote&gt; It's ironic really that the product billed as personal blog software turned out to be more adaptable to professional-level online publishing and content management than products designed to be professional content management systems. A couple of months developing our own WordPress tools and front end, and we have a team-ready, robust content management system with more flexibility and ease of use than Joomla and its ilk could aspire to in five years.&lt;/blockquote&gt;

Funny. Will you also be selling the finished product? ;-)</description>
		<content:encoded><![CDATA[<p>Well, it works for me! Love the new layout. Who actually won the contest, btw? Your CSM smells like Joomla, but in your code is this:<br />
<blockquote> It&#8217;s ironic really that the product billed as personal blog software turned out to be more adaptable to professional-level online publishing and content management than products designed to be professional content management systems. A couple of months developing our own WordPress tools and front end, and we have a team-ready, robust content management system with more flexibility and ease of use than Joomla and its ilk could aspire to in five years.</p></blockquote>
<p>Funny. Will you also be selling the finished product? ;-)
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
