<?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: Changing the way we change websites&#8230;</title>
	<atom:link href="http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/feed/" rel="self" type="application/rss+xml" />
	<link>http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/</link>
	<description>bursts of ideas and rants by the alterego</description>
	<lastBuildDate>Tue, 31 Jan 2012 17:40:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Marko Mrdjenovic</title>
		<link>http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/comment-page-1/#comment-82</link>
		<dc:creator>Marko Mrdjenovic</dc:creator>
		<pubDate>Fri, 05 May 2006 16:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/#comment-82</guid>
		<description>That&#039;s what I was saying - sometimes when a used nail is straight it&#039;s cheaper to reuse it. I think another important thing is that a complete redesign is a &#039;huge&#039; project that companies often find hard to back with arguments.

I could make a parallel with cars - you get a new model and in a few years time you get a &#039;cosmetic&#039; change. You might get a few other changes if the car is still selling. Only after it&#039;s life cycle cannot be prolonged anymore the company decides to kill it and launch another one in its place.</description>
		<content:encoded><![CDATA[<p>That&#8217;s what I was saying &#8211; sometimes when a used nail is straight it&#8217;s cheaper to reuse it. I think another important thing is that a complete redesign is a &#8216;huge&#8217; project that companies often find hard to back with arguments.</p>
<p>I could make a parallel with cars &#8211; you get a new model and in a few years time you get a &#8216;cosmetic&#8217; change. You might get a few other changes if the car is still selling. Only after it&#8217;s life cycle cannot be prolonged anymore the company decides to kill it and launch another one in its place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko</title>
		<link>http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/comment-page-1/#comment-81</link>
		<dc:creator>Marko</dc:creator>
		<pubDate>Fri, 05 May 2006 16:07:15 +0000</pubDate>
		<guid isPermaLink="false">http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/#comment-81</guid>
		<description>No, it comes down to cost. Unchanged templates aren&#039;t some holy goal we should aim to achieve. I don&#039;t reuse old nails either.

I think keeping templates might make sense only when doing so is cheaper than not to. Certainly by chosing to keep them we add additional limitation to our designs.

I&#039;d like to believe that with each year there are fewer CMS&#039;s around that would make reusing templates a necessary or even appealing idea.</description>
		<content:encoded><![CDATA[<p>No, it comes down to cost. Unchanged templates aren&#8217;t some holy goal we should aim to achieve. I don&#8217;t reuse old nails either.</p>
<p>I think keeping templates might make sense only when doing so is cheaper than not to. Certainly by chosing to keep them we add additional limitation to our designs.</p>
<p>I&#8217;d like to believe that with each year there are fewer CMS&#8217;s around that would make reusing templates a necessary or even appealing idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko Mrdjenovic</title>
		<link>http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/comment-page-1/#comment-78</link>
		<dc:creator>Marko Mrdjenovic</dc:creator>
		<pubDate>Fri, 05 May 2006 11:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/#comment-78</guid>
		<description>My point is that the technology allows it and more and more companies/people are aware of it which makes it more likely to happen. The thing is that it comes down to the mentality of the caretakers.

When it comes to personal experience my decision is made on the current state of the html code - if it&#039;s clean I just change the styles. It&#039;s way faster. On the backend I strive to make blocks as generic as possible to allow this.</description>
		<content:encoded><![CDATA[<p>My point is that the technology allows it and more and more companies/people are aware of it which makes it more likely to happen. The thing is that it comes down to the mentality of the caretakers.</p>
<p>When it comes to personal experience my decision is made on the current state of the html code &#8211; if it&#8217;s clean I just change the styles. It&#8217;s way faster. On the backend I strive to make blocks as generic as possible to allow this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko</title>
		<link>http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/comment-page-1/#comment-77</link>
		<dc:creator>Marko</dc:creator>
		<pubDate>Fri, 05 May 2006 10:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://friedcellcollective.net/outbreak/2006/05/05/changing-the-way-we-change-websites/#comment-77</guid>
		<description>Yes, but you didn&#039;t change HTML because you simply couldn&#039;t.

You&#039;ll obviously work from existing XHTML templates if your client demands that and I absolutely agree that good templates make such work possible. But that wasn&#039;t my point.

What I wanted to know is if you do it otherwise? Do you look at templates first and try to fit design to it when this isn&#039;t expected of you?

I have a sneaky suspicion that you don&#039;t and that not many people do. And that was my point. There are plenty of reasons to do CSS based designs, but reusing existing templates might not be one of them.

On a big site with a fairly complex CSS it can simply take more time to understand previous design (and that&#039;s work providing little fun) than to whip up your own and I don&#039;t see this changing anytime soon.

Of course, there will always be exceptions.</description>
		<content:encoded><![CDATA[<p>Yes, but you didn&#8217;t change HTML because you simply couldn&#8217;t.</p>
<p>You&#8217;ll obviously work from existing XHTML templates if your client demands that and I absolutely agree that good templates make such work possible. But that wasn&#8217;t my point.</p>
<p>What I wanted to know is if you do it otherwise? Do you look at templates first and try to fit design to it when this isn&#8217;t expected of you?</p>
<p>I have a sneaky suspicion that you don&#8217;t and that not many people do. And that was my point. There are plenty of reasons to do CSS based designs, but reusing existing templates might not be one of them.</p>
<p>On a big site with a fairly complex CSS it can simply take more time to understand previous design (and that&#8217;s work providing little fun) than to whip up your own and I don&#8217;t see this changing anytime soon.</p>
<p>Of course, there will always be exceptions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

