<?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: Site Studio Tips, Tricks and Hacks</title>
	<atom:link href="http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/</link>
	<description></description>
	<lastBuildDate>Tue, 12 Oct 2010 09:45:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Troy</title>
		<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/#comment-592</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Wed, 21 May 2008 00:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://ContentOnContentManagement.com/2007/12/05/site-studio-tips-tricks-and-hacks/#comment-592</guid>
		<description>Hey, just found your blog. I find your 1st two tips very interesting, as I started doing both of these to some degree in the last few months.
The logical naming of nodes is something we have always done. I disagree with Mikeyc, finding unique names is easy with a standard. No two nodes are identical anyway.
The &#039;frag as a file store&#039; is something we have started doing here recently, and DAMN is it handy. Previously we had site wide images, CSS and JS checked in as content. This made editing them a nightmare! Checking out, editing, checking in, review changes, repeat.
A contractor set up the JSP -&gt; eclipse link for me a while back, I will have to check that out again sometime.</description>
		<content:encoded><![CDATA[<p>Hey, just found your blog. I find your 1st two tips very interesting, as I started doing both of these to some degree in the last few months.<br />
The logical naming of nodes is something we have always done. I disagree with Mikeyc, finding unique names is easy with a standard. No two nodes are identical anyway.<br />
The &#8216;frag as a file store&#8217; is something we have started doing here recently, and DAMN is it handy. Previously we had site wide images, CSS and JS checked in as content. This made editing them a nightmare! Checking out, editing, checking in, review changes, repeat.<br />
A contractor set up the JSP -&gt; eclipse link for me a while back, I will have to check that out again sometime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre</title>
		<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/#comment-383</link>
		<dc:creator>Pierre</dc:creator>
		<pubDate>Fri, 14 Mar 2008 16:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://ContentOnContentManagement.com/2007/12/05/site-studio-tips-tricks-and-hacks/#comment-383</guid>
		<description>I David, i&#039;m new in UCM and i really appreciate your comments. It Help me out a lot. thanks</description>
		<content:encoded><![CDATA[<p>I David, i&#8217;m new in UCM and i really appreciate your comments. It Help me out a lot. thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/#comment-362</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 13 Mar 2008 05:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://ContentOnContentManagement.com/2007/12/05/site-studio-tips-tricks-and-hacks/#comment-362</guid>
		<description>I just surfed in and found your site, I really enjoyed the visit and hope to come back soon. nice Site!</description>
		<content:encoded><![CDATA[<p>I just surfed in and found your site, I really enjoyed the visit and hope to come back soon. nice Site!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/#comment-42</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Thu, 20 Dec 2007 15:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://ContentOnContentManagement.com/2007/12/05/site-studio-tips-tricks-and-hacks/#comment-42</guid>
		<description>Another good tip I like is to really make use of Custom Section Properties.  This can help you reuse layouts/fragments when you may otherwise need a new one.  Things like queries can be defined in the section properties so that the same layout can have different dynamic list results.

It&#039;s also handy for defining meta tags that may be applicable per section of the site.

There&#039;s also a way to define site-wide properties using it.  See doc 445449.1 on metalink.oracle.com for a how to.</description>
		<content:encoded><![CDATA[<p>Another good tip I like is to really make use of Custom Section Properties.  This can help you reuse layouts/fragments when you may otherwise need a new one.  Things like queries can be defined in the section properties so that the same layout can have different dynamic list results.</p>
<p>It&#8217;s also handy for defining meta tags that may be applicable per section of the site.</p>
<p>There&#8217;s also a way to define site-wide properties using it.  See doc 445449.1 on metalink.oracle.com for a how to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Roe</title>
		<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/#comment-20</link>
		<dc:creator>David Roe</dc:creator>
		<pubDate>Wed, 12 Dec 2007 00:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://ContentOnContentManagement.com/2007/12/05/site-studio-tips-tricks-and-hacks/#comment-20</guid>
		<description>Hi Mike,

Thanks very much for your comment, as you can see the site doesn&#039;t get much feedback so I&#039;m pretty excited when anyone responds.

To your comment though, I think that&#039;s an excellent point in relation to dozens of sub-admins.  I can see how could quickly become a bear to manage.

Still I think for the majority of sites having logically named IDs can help a great deal when it comes to debugging issues and development.</description>
		<content:encoded><![CDATA[<p>Hi Mike,</p>
<p>Thanks very much for your comment, as you can see the site doesn&#8217;t get much feedback so I&#8217;m pretty excited when anyone responds.</p>
<p>To your comment though, I think that&#8217;s an excellent point in relation to dozens of sub-admins.  I can see how could quickly become a bear to manage.</p>
<p>Still I think for the majority of sites having logically named IDs can help a great deal when it comes to debugging issues and development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mikeyc</title>
		<link>http://contentoncontentmanagement.com/2007/12/site-studio-tips-tricks-and-hacks/#comment-18</link>
		<dc:creator>mikeyc</dc:creator>
		<pubDate>Tue, 11 Dec 2007 07:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://ContentOnContentManagement.com/2007/12/05/site-studio-tips-tricks-and-hacks/#comment-18</guid>
		<description>I really disagree about naming your nodes. My site has dozens of subadmins with access to nodes. They can&#039;t even assign proper URL directory names! Once an ID is used, it cannot be reused... and everyone wants to use &quot;about&quot;. Stick to auto-generated nodeIDs and just chuck in some code to identify the label whenever required.</description>
		<content:encoded><![CDATA[<p>I really disagree about naming your nodes. My site has dozens of subadmins with access to nodes. They can&#8217;t even assign proper URL directory names! Once an ID is used, it cannot be reused&#8230; and everyone wants to use &#8220;about&#8221;. Stick to auto-generated nodeIDs and just chuck in some code to identify the label whenever required.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

