<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Kommentare zu: 10 RedDot CMS elements - RedDot development and element name conventions</title>
	<link>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/</link>
	<description>The RedDot CMS and TYPO3 Blog for developers, authors and RedDot CMS clients</description>
	<pubDate>Sat, 04 Feb 2012 22:58:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>Von: Alex Dean</title>
		<link>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-222</link>
		<author>Alex Dean</author>
		<pubDate>Sun, 18 May 2008 02:37:04 +0000</pubDate>
		<guid>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-222</guid>
					<description>Good point. One more I would like to add. all programmers (except for the ancient cobol or fortran boys and girls maybe) already know this. use sensible names. You should be able to identify your element instantly and know exactly what it is used for.
dont go and call the elements std_item1, std_item2, std_item3 but rather, std_TopParagraph, std_Author, std_disclaimer.
More importantly, name your containers in a manner that people know what is hiding beneath them.</description>
		<content:encoded><![CDATA[<p>Good point. One more I would like to add. all programmers (except for the ancient cobol or fortran boys and girls maybe) already know this. use sensible names. You should be able to identify your element instantly and know exactly what it is used for.<br />
dont go and call the elements std_item1, std_item2, std_item3 but rather, std_TopParagraph, std_Author, std_disclaimer.<br />
More importantly, name your containers in a manner that people know what is hiding beneath them.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Von: Alex Dean</title>
		<link>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-223</link>
		<author>Alex Dean</author>
		<pubDate>Sun, 18 May 2008 02:49:43 +0000</pubDate>
		<guid>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-223</guid>
					<description>Oh, and one more thing. On a similar note

When designing your container structure in Reddot keep in mind that you will be changing your mind on how things work later. Maybe not a year later, maybe not two but at some point in time the customer is going to turn around and ask you for X or Y. Simple example. Customer asks you for the request, that only in a particular language version a totally different site tracking code shall appear. The easiest way to do this is to create a new template and plonk a page of that template into a container at the bottom of the page only for that one particular language version.
OUCH. Now you have to update all 2600 pages in the project manually with this new container content or write a script that will do it for you.

Much easier:
When you design your site, include a container at the bottom which holds a page which holds a container. pull this page automatically throughout your site by predefining it on the masterpage template. Every time a new page is created, the content is automatically refrenced. Now all you have to do is add your special little page to the container in the container once and it will automatically appear everywhere where else.</description>
		<content:encoded><![CDATA[<p>Oh, and one more thing. On a similar note</p>
<p>When designing your container structure in Reddot keep in mind that you will be changing your mind on how things work later. Maybe not a year later, maybe not two but at some point in time the customer is going to turn around and ask you for X or Y. Simple example. Customer asks you for the request, that only in a particular language version a totally different site tracking code shall appear. The easiest way to do this is to create a new template and plonk a page of that template into a container at the bottom of the page only for that one particular language version.<br />
OUCH. Now you have to update all 2600 pages in the project manually with this new container content or write a script that will do it for you.</p>
<p>Much easier:<br />
When you design your site, include a container at the bottom which holds a page which holds a container. pull this page automatically throughout your site by predefining it on the masterpage template. Every time a new page is created, the content is automatically refrenced. Now all you have to do is add your special little page to the container in the container once and it will automatically appear everywhere where else.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Von: Glenn Haworth</title>
		<link>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-3279</link>
		<author>Glenn Haworth</author>
		<pubDate>Fri, 20 Feb 2009 15:32:16 +0000</pubDate>
		<guid>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-3279</guid>
					<description>Not using Reddot, lol...</description>
		<content:encoded><![CDATA[<p>Not using Reddot, lol&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>Von: Ingo Hillebrand</title>
		<link>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-5480</link>
		<author>Ingo Hillebrand</author>
		<pubDate>Wed, 05 Aug 2009 08:14:47 +0000</pubDate>
		<guid>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-5480</guid>
					<description>Thanks a lot for this list - a few days ago i searched the web for a common identifier for a "standard text element" in reddot projects.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for this list - a few days ago i searched the web for a common identifier for a &#8220;standard text element&#8221; in reddot projects.</p>
]]></content:encoded>
				</item>
	<item>
		<title>Von: Markus Giesen</title>
		<link>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-5482</link>
		<author>Markus Giesen</author>
		<pubDate>Wed, 05 Aug 2009 14:22:17 +0000</pubDate>
		<guid>http://blog.markusgiesen.de/2008/04/26/reddot-cms-development-and-element-name-conventions/#comment-5482</guid>
					<description>You're welcome! :)
Hoffe du bist wieder auf den Beinen?!</description>
		<content:encoded><![CDATA[<p>You&#8217;re welcome! <img src='http://blog.markusgiesen.de/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Hoffe du bist wieder auf den Beinen?!</p>
]]></content:encoded>
				</item>
</channel>
</rss>

