<?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>Blog Yellek &#187; principles</title>
	<atom:link href="http://yellek.org/blog/tag/principles/feed/" rel="self" type="application/rss+xml" />
	<link>http://yellek.org/blog</link>
	<description>Thoughts of a Technologist in South Australia</description>
	<lastBuildDate>Thu, 27 Oct 2011 07:43:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Website Technical Design Principles</title>
		<link>http://yellek.org/blog/2010/02/22/website-technical-design-principles/</link>
		<comments>http://yellek.org/blog/2010/02/22/website-technical-design-principles/#comments</comments>
		<pubDate>Sun, 21 Feb 2010 22:21:34 +0000</pubDate>
		<dc:creator>yellek</dc:creator>
				<category><![CDATA[tech]]></category>
		<category><![CDATA[principles]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://yellek.org/blog/?p=397</guid>
		<description><![CDATA[I&#8217;ve recently become involved in assiting an organisation to add a little bit of technical rigour to their brief for the redesign of their website. As a part of this I&#8217;m developing some technical principles to guide the technical requirements. I&#8217;ve listed the principles below: The website shall be developed in such a way as [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve recently become involved in assiting an organisation to add a little bit of technical rigour to their brief for the redesign of their website. As a part of this I&#8217;m developing some technical principles to guide the technical requirements. I&#8217;ve listed the principles below: </p>
<ol>
<li>The website shall be developed in such a way as to allow maintenance by persons other than the successful bidder.</li>
<li>The design of the website shall allow future enhancements to take into account changing requirements, technology and standards without requiring a rewrite.</li>
<li>The website shall allow the content to be edited and maintained by the client without the need to engage external parties to do so.</li>
<li>The website shall be accessible to the widest possible audience and shall not prevent access by people with disabilities or access by persons using commonly used technology.</li>
<li>The website shall be designed in such a way as to promote favorable ranking in common search engines.</li>
<li>The website shall be designed to prevent modification of its contents by unauthorised users.</li>
</ol>
<p>I think these form a pretty good basis for good technical website design.</p>
]]></content:encoded>
			<wfw:commentRss>http://yellek.org/blog/2010/02/22/website-technical-design-principles/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

