<?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>Oracle of ONE1 &#187; structure</title>
	<atom:link href="http://dvector.com/oracle/tag/structure/feed/" rel="self" type="application/rss+xml" />
	<link>http://dvector.com/oracle</link>
	<description>Obscure words of unity</description>
	<lastBuildDate>Wed, 31 Aug 2011 21:25:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Posts not Pages</title>
		<link>http://dvector.com/oracle/2008/07/16/posts-not-pages/</link>
		<comments>http://dvector.com/oracle/2008/07/16/posts-not-pages/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 20:00:01 +0000</pubDate>
		<dc:creator>one1</dc:creator>
				<category><![CDATA[dvector]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[dvector support]]></category>
		<category><![CDATA[structure]]></category>

		<guid isPermaLink="false">http://dvector.com/oracle/?p=54</guid>
		<description><![CDATA[I have noticed that many novice WordPress users try to build their site using Pages. This fights the WordPress system. These users are not using WordPress as a blogging platform but as an entry-level Content Management System. Now I know we use words such as &#8216;view a web page&#8217; but page here has a different [...]]]></description>
			<content:encoded><![CDATA[<p>I have noticed that many novice WordPress users try to build their site using Pages. This <a title="Don't Fight the System" href="http://dvector.com/oracle/2008/02/28/dont-fight-the-system/">fights the WordPress system</a>. These users are not using WordPress as a blogging platform but as an entry-level Content Management System. Now I know we use words such as &#8216;view a web page&#8217; but page here has a different meaning.</p>
<p>One thing I push, is that 99% of the site&#8217;s content should be in posts. Write content to posts. They are much more flexible and easier for a developer to work with.</p>
<p>Pages have their place on a site but are limited to non-hierarchical, never-changing, organizational metadata (information about data). So what goes on a page? About, contact, history, jurisdiction, terms of use, privacy statements, and a sitemap. All the boring stuff.</p>
<p>Posts, on the other hand, can belong to multiple categories and have unlimited tags. Categories and tags automatically create the navigational structure of the site. The power of going with the flow is that most of the structure is done for you instead of needing to be created by you.</p>
]]></content:encoded>
			<wfw:commentRss>http://dvector.com/oracle/2008/07/16/posts-not-pages/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Fight the System</title>
		<link>http://dvector.com/oracle/2008/02/28/dont-fight-the-system/</link>
		<comments>http://dvector.com/oracle/2008/02/28/dont-fight-the-system/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 22:13:22 +0000</pubDate>
		<dc:creator>oracle</dc:creator>
				<category><![CDATA[dvector]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[dvector support]]></category>
		<category><![CDATA[structure]]></category>

		<guid isPermaLink="false">http://dvector.com/oracle/2008/02/28/dont-fight-the-system/</guid>
		<description><![CDATA[This article introduces experienced and novice web designers to WordPress. WordPress has its own way of structuring data and it is much easier to adjust yourself to the natural structure of WordPress than it is to twist WordPress to your way of thinking. Adjusting yourself will make WordPress a surprisingly effective and efficient means of [...]]]></description>
			<content:encoded><![CDATA[<p>This article introduces experienced and novice web designers to WordPress. WordPress has its own way of structuring data and it is much easier to adjust yourself to the natural structure of WordPress than it is to twist WordPress to your way of thinking. Adjusting yourself will make WordPress a surprisingly effective and efficient means of fulfilling your needs.</p>
<p>WordPress has extensive documentation that covers all aspects of creating, populating, and maintaining your blog or website. <a href="http://codex.wordpress.org" title="WordPress Documentation">Please do view that documentation</a> as it is always the most complete and current.</p>
<p>Don&#8217;t start your design with presentation, start with the structure and come back to the presentation later. First, make certain that everything you wish to do can be done by WordPress. WordPress is an advanced blogging system but it is not a Content Management System. A CMS offers far more flexibility to build the structure but it pays with added complexity.<br />
<span id="more-15"></span></p>
<h3>Structure</h3>
<p>Posts are the basic building block of a WordPress site. A post is the individual article or story that an author creates, saves, and then publishes to the site.  Posts may belong to many categories and may be given many tags.</p>
<p>By default, posts are organized by date posted. They are usually displayed in date order with the most recent posts displaying first. Archives are listings of the posts filtered by date (monthly or yearly archive). The front page of a blog may feature a calendar of dates linked to daily archives. Archives can also be based on categories featuring all the articles related to a specific category.</p>
<h3>Categories and Tags</h3>
<p>Categories and tags provide additional means to view, and importantly, navigate your posts. Categories provide the hierarchical structure and means of viewing and navigating posts. The category structure of your site should be a thoughtful and considered part of your design</p>
<p>Tags provide a longitudinal method of relating and navigating posts. Tag creation and usage is much more ad hoc and creative. Sometimes tags relate to a few key words in a post or to some of the post&#8217;s central ideas. Tags are very good at pulling seemingly unrelated information together.</p>
<p>Regardless of how you use them, please do use both categories and tags for every post you create.</p>
<h3>Pages</h3>
<p>Pages are another content type available in WordPress. They differ from posts in that they are neither categorized or tagged. Generally, use a page for static content such as:</p>
<ul>
<li>About us</li>
<li>Contact us</li>
<li>Office locations</li>
</ul>
<p>Pages should be used with restraint.</p>
<h3>Presentation</h3>
<p>Once you have familiarized yourself with the way WordPress prefers to structure information by creating posts, pages, categories, and tags; then you may begin to change the presentation of the site. Presentation here refers to the look and feel of the site as well as the types of naviagation that are available.</p>
<p>Up until now, you should have been sticking with the default installed theme. This theme is an excellent starting point for you to create your own uniquely branded site. It shows the basics of WordPress structure and covers all of the presentation points. There are many freely distributed themes available for WordPress. Try some of these on by visiting <a href="http://themes.wordpress.net/" title="Theme Viewer">Theme Viewer</a>.</p>
<h3>Consolidation</h3>
<p>Now you are ready to  consolidate the framework of WordPress with your ideas on presentation. Sit down and think about it a little then start putting pencil to paper. The basics of this is well covered in <a href="http://codex.wordpress.org/First_Steps_With_WordPress#Planning_Session" title="Planning">this document</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://dvector.com/oracle/2008/02/28/dont-fight-the-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

