<?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>CSSAddict &#187; open source</title>
	<atom:link href="http://www.cssaddict.com/tag/open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cssaddict.com</link>
	<description>Web Design Concepts</description>
	<lastBuildDate>Mon, 19 Dec 2011 20:57:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Web Standards &amp; Open Source</title>
		<link>http://www.cssaddict.com/blog/web-standards-open-source/</link>
		<comments>http://www.cssaddict.com/blog/web-standards-open-source/#comments</comments>
		<pubDate>Tue, 18 Dec 2007 14:53:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://www.cssaddict.com/blog/web-standards-open-source/</guid>
		<description><![CDATA[It seems that more and more open source projects are taking interest in Web Standards and clean validated code. Very few CMS projects out there are 100% XHTML and CSS valid, therefore the need to come up with quality code has been emerging even more. We are talking about future compatibility and accessibility, something that [...]]]></description>
			<content:encoded><![CDATA[<p>It seems that more and more open source projects are taking interest in Web Standards and clean validated code. Very few CMS projects out there are 100% XHTML and CSS valid, therefore the need to come up with quality code has been emerging even more. We are talking about future compatibility and accessibility, something that is of everyone’s best interest. One of the main problems regarding these projects is laying on the output of editors.</p>
<p><span id="more-22"></span></p>
<p>If we are to develop a website for a client that needs to update a website on his own, an editor that outputs valid XHTML code is a must. Such editors are certainly not for free. One of the best I’ve come across is <a onclick="javascript:urchinTracker ('/outbound/www.xstandard.com');" href="http://www.xstandard.com/">xstandard</a> that recently has developed a free light version for commercial use. Mind you, I haven’t seen it integrated in any open source project just yet.<br />
Open source is a big hit on ecommerce projects, too. There are a few noteworthy effords on this, such as the so-talked-about <a onclick="javascript:urchinTracker ('/outbound/www.freecsscart.com');" href="http://www.freecsscart.com/index.php/feature-list/">freecsscart</a>, that, unfortunately, is still under development and no-one really knows if they’ll ever release it. A similar idea comes from <a onclick="javascript:urchinTracker ('/outbound/www.tradingeye.com');" href="http://www.tradingeye.com/">tradingeye</a>, although is not free, something that is totally understandable, as valid code in such projects is definitely not an easy task.</p>
<p>People that contribute on open source projects, cannot afford to invest much time on it as noone is really paying them to do it. It seems that we get what we paid for and that’s only fair.</p>
<p>UPDATE: Movable Type&#8217;s publishing platform in now an Open Source project and is available for <a title="MovableType Open Source" href="http://www.movabletype.org/">download.</a> This is definitely something worth looking at, since Movable Type has been a paid project for quite a while.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cssaddict.com/blog/web-standards-open-source/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

