<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Thinking of WordPress as a CMS</title>
  <link rel="alternate" href="http://www.webjunction.org/c/message_boards/find_thread?p_l_id=4977828&amp;threadId=54531501" />
  <subtitle>Thinking of WordPress as a CMS</subtitle>
  <entry>
    <title>Thinking of WordPress as a CMS</title>
    <link rel="alternate" href="http://www.webjunction.org/c/message_boards/find_message?p_l_id=4977828&amp;messageId=54531500" />
    <author>
      <name>George Plumley</name>
    </author>
    <updated>2009-04-10T15:56:31Z</updated>
    <published>2009-04-10T15:56:31Z</published>
    <summary type="html">For anyone thinking about WordPress to run their website &amp;#040;not just a blog&amp;#041;, here&amp;#039;s something that might help.  Blogs are nothing more than very simple content management systems and blog posts are nothing more than chunks of content.  &lt;br /&gt;&lt;br /&gt;By some very simple manipulations of a WordPress theme &amp;#040;you never touch the actual core of WordPress&amp;#041; you can use those blog posts in all sorts of ways.  For example, a blog post could be a book listing and by manipulating your theme templates and style sheets, those book listings can look completely different than a blog post used as an FAQ entry.&lt;br /&gt;&lt;br /&gt;When you start to think of WordPress that way, it&amp;#039;s not a question of whether it can do the job, but what jobs do you want it to do.</summary>
    <dc:creator>George Plumley</dc:creator>
    <dc:date>2009-04-10T15:56:31Z</dc:date>
  </entry>
</feed>

