<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Should WordPress Change The Blog Nomenclature Within The Backend?</title>
	<atom:link href="http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend</link>
	<description>Where Every Drink Is On The House</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:56:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brad</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4707</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Mon, 09 Nov 2009 15:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4707</guid>
		<description>I actually asked Matt M in my SitePoint interview if there were any plans/discussions on changing the blog references in the backend of WordPress and he said no</description>
		<content:encoded><![CDATA[<p>I actually asked Matt M in my SitePoint interview if there were any plans/discussions on changing the blog references in the backend of WordPress and he said no</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4663</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 06 Nov 2009 00:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4663</guid>
		<description>Entirely off-topic: Otto&#039;s unfiltered opinions are terrific! Ozh isn&#039;t too shabby on the critique front either. We may not agree with their opinions (particularly Otto&#039;s silly obsession with &lt;strong&gt;never&lt;/strong&gt; modifying HTML no matter how dementedly convoluted and hackish it may make the CSS) but extensive constructive criticism is vital to everyone&#039;s development (unless you are perfect like me of course!).</description>
		<content:encoded><![CDATA[<p>Entirely off-topic: Otto&#8217;s unfiltered opinions are terrific! Ozh isn&#8217;t too shabby on the critique front either. We may not agree with their opinions (particularly Otto&#8217;s silly obsession with <strong>never</strong> modifying HTML no matter how dementedly convoluted and hackish it may make the CSS) but extensive constructive criticism is vital to everyone&#8217;s development (unless you are perfect like me of course!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4660</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Thu, 05 Nov 2009 18:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4660</guid>
		<description>One source of confusion is that there are two different definitions of CMS running around. The first is more literal, where pieces of content are managed as content separated from form or design. In this sense, every WordPress installation, blog or not, is a CMS. Most blogs in general, unless each entry&#039;s design is hand-coded, are instances of a CMS. 

The second definition, which a lot of recent wordcamps have gotten at, is operational. WordPress as a CMS is being taken to mean a larger installation that is not centered around a reverse-chronological blog. This usually involves a greater variety of moving parts: a larger entity or organization than one blogger, more types of pages along a continuum from fixed to dynamic, a theme friendly to menus and maybe more plugins/widgets, and more end users than the web designer. There are already many solutions to changing the admin interfaces for various user roles so that some of them don&#039;t necessarily have to see the word &quot;blog.&quot;

Note that this is much more than &quot;WordPress, Debloggified.&quot; Either a blog or posts reused as &quot;articles&quot; often remain in this second use/definition. 

The phrase &quot;content management system&quot; is a mouthful of awkward, but hard to replace. Sites like cmswire, cmsreport, cmsmyth, cmswatch, and cms critic really do like to talk about WordPress. We should be glad that we&#039;re talking about WordPress and not &quot;WordBlog.&quot;</description>
		<content:encoded><![CDATA[<p>One source of confusion is that there are two different definitions of CMS running around. The first is more literal, where pieces of content are managed as content separated from form or design. In this sense, every WordPress installation, blog or not, is a CMS. Most blogs in general, unless each entry&#8217;s design is hand-coded, are instances of a CMS. </p>
<p>The second definition, which a lot of recent wordcamps have gotten at, is operational. WordPress as a CMS is being taken to mean a larger installation that is not centered around a reverse-chronological blog. This usually involves a greater variety of moving parts: a larger entity or organization than one blogger, more types of pages along a continuum from fixed to dynamic, a theme friendly to menus and maybe more plugins/widgets, and more end users than the web designer. There are already many solutions to changing the admin interfaces for various user roles so that some of them don&#8217;t necessarily have to see the word &#8220;blog.&#8221;</p>
<p>Note that this is much more than &#8220;WordPress, Debloggified.&#8221; Either a blog or posts reused as &#8220;articles&#8221; often remain in this second use/definition. </p>
<p>The phrase &#8220;content management system&#8221; is a mouthful of awkward, but hard to replace. Sites like cmswire, cmsreport, cmsmyth, cmswatch, and cms critic really do like to talk about WordPress. We should be glad that we&#8217;re talking about WordPress and not &#8220;WordBlog.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4659</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4659</guid>
		<description>@&lt;a href=&quot;#comment-4656&quot; rel=&quot;nofollow&quot;&gt;David Coveney&lt;/a&gt; - I think it&#039;s a bit different when it&#039;s in person, because I always give the same kind of unfiltered opinion when asked IRL too, and people don&#039;t tend to get as annoyed as when I do it online.

Maybe it&#039;s because I tend to smile while telling people why they&#039;re wrong (and should be committed into an insane aslyum until such time as they find a cure for idiocy).. Could soften the blow a bit, I suppose. :)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4656" rel="nofollow">David Coveney</a> &#8211; I think it&#8217;s a bit different when it&#8217;s in person, because I always give the same kind of unfiltered opinion when asked IRL too, and people don&#8217;t tend to get as annoyed as when I do it online.</p>
<p>Maybe it&#8217;s because I tend to smile while telling people why they&#8217;re wrong (and should be committed into an insane aslyum until such time as they find a cure for idiocy).. Could soften the blow a bit, I suppose. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4658</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4658</guid>
		<description>@&lt;a href=&quot;#comment-4657&quot; rel=&quot;nofollow&quot;&gt;Jeffro&lt;/a&gt; -Finally something we can all agree on ;-)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4657" rel="nofollow">Jeffro</a> -Finally something we can all agree on ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffro</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4657</link>
		<dc:creator>Jeffro</dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4657</guid>
		<description>@&lt;a href=&quot;#comment-4655&quot; rel=&quot;reply&quot; rel=&quot;nofollow&quot;&gt;Otto&lt;/a&gt; - Are you calling me stupid? Just making sure :)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4655" rel="reply" rel="nofollow">Otto</a> &#8211; Are you calling me stupid? Just making sure :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Coveney</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4656</link>
		<dc:creator>David Coveney</dc:creator>
		<pubDate>Thu, 05 Nov 2009 17:11:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4656</guid>
		<description>What I like about Otto is that he doesn&#039;t care if he annoys you or not - he gives you his straight, unfiltered opinion.

Wish I could be more like that :-)</description>
		<content:encoded><![CDATA[<p>What I like about Otto is that he doesn&#8217;t care if he annoys you or not &#8211; he gives you his straight, unfiltered opinion.</p>
<p>Wish I could be more like that :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4655</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Thu, 05 Nov 2009 16:37:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4655</guid>
		<description>No, absolutely not. This is a worthless bikeshed issue that just causes argument. It won&#039;t have any actual impact in the real world.

If somebody wants to make a translation file with better text, then let them do that first, and we&#039;ll see how much traction it gets among the &quot;it&#039;s a CMS&quot; crowd. My prediction: It won&#039;t get any, because it&#039;s a stupid issue and only stupid people care about it.

Yes, I mean you. :-P</description>
		<content:encoded><![CDATA[<p>No, absolutely not. This is a worthless bikeshed issue that just causes argument. It won&#8217;t have any actual impact in the real world.</p>
<p>If somebody wants to make a translation file with better text, then let them do that first, and we&#8217;ll see how much traction it gets among the &#8220;it&#8217;s a CMS&#8221; crowd. My prediction: It won&#8217;t get any, because it&#8217;s a stupid issue and only stupid people care about it.</p>
<p>Yes, I mean you. :-P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dalton</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4653</link>
		<dc:creator>Dalton</dc:creator>
		<pubDate>Thu, 05 Nov 2009 14:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4653</guid>
		<description>I have building sites with WordPress for several years now (including &lt;a href=&quot;http://wordpress.org/showcase/storycorps/&quot; rel=&quot;nofollow&quot;&gt;one in the showcase&lt;/a&gt; that uses WordPress as a CMS with hundreds of pages of content) and I have to say that I still don&#039;t think that WordPress is ready to be an industrial-strength CMS. To be fair, I also don&#039;t think that&#039;s what the WordPress team is trying to achieve, which is why things settings like &quot;Blog Title&quot; still persist.

WordPress is an amazing blogging platform, and provides some great light-weight CMS capabilities along with the vast array of plugins and functions. But simple CMS functionality like page and file management are still weak and neglected. Some of this functionality is available through plugins, but these can often be out of date or incompatible with other plugins. (Example: WP-Table breaks my cForms).  To top it off, I have to install dozens of plugins for each WordPress install to get some of these features that I consider &quot;basic&quot; CMS functionality. Until these tools become more robust, and part of the WordPress core, WordPress will continue to be blog software that has some great CMS capabilities.</description>
		<content:encoded><![CDATA[<p>I have building sites with WordPress for several years now (including <a href="http://wordpress.org/showcase/storycorps/" rel="nofollow">one in the showcase</a> that uses WordPress as a CMS with hundreds of pages of content) and I have to say that I still don&#8217;t think that WordPress is ready to be an industrial-strength CMS. To be fair, I also don&#8217;t think that&#8217;s what the WordPress team is trying to achieve, which is why things settings like &#8220;Blog Title&#8221; still persist.</p>
<p>WordPress is an amazing blogging platform, and provides some great light-weight CMS capabilities along with the vast array of plugins and functions. But simple CMS functionality like page and file management are still weak and neglected. Some of this functionality is available through plugins, but these can often be out of date or incompatible with other plugins. (Example: WP-Table breaks my cForms).  To top it off, I have to install dozens of plugins for each WordPress install to get some of these features that I consider &#8220;basic&#8221; CMS functionality. Until these tools become more robust, and part of the WordPress core, WordPress will continue to be blog software that has some great CMS capabilities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt mcinvale</title>
		<link>http://www.wptavern.com/should-wordpress-change-the-blog-nomenclature-within-the-backend#comment-4647</link>
		<dc:creator>matt mcinvale</dc:creator>
		<pubDate>Wed, 04 Nov 2009 23:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2784#comment-4647</guid>
		<description>You&#039;re free to change this on your installs with a custom translation. I recently had to change &quot;Posts&quot; to &quot;Bikes&quot; to keep from confusing a client, works quite well.</description>
		<content:encoded><![CDATA[<p>You&#8217;re free to change this on your installs with a custom translation. I recently had to change &#8220;Posts&#8221; to &#8220;Bikes&#8221; to keep from confusing a client, works quite well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

