<?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>Sean Jones</title>
	<atom:link href="http://www.cssmonkey.co.uk/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.cssmonkey.co.uk/blog</link>
	<description>Front-end Web Developer</description>
	<lastBuildDate>Sun, 22 Jan 2012 14:51:50 +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>Faster sites with head.js</title>
		<link>http://www.cssmonkey.co.uk/blog/?p=17</link>
		<comments>http://www.cssmonkey.co.uk/blog/?p=17#comments</comments>
		<pubDate>Sat, 07 Jan 2012 13:23:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://www.cssmonkey.co.uk/blog/?p=17</guid>
		<description><![CDATA[WTF is head js? headjs is a small script which can help speed up your site and comes bundled with a number of other very useful features. WTF do you mean? Headjs allows your javascript files to be loaded like images &#8211; completely separate from the page rendering process. Normally JavaScript is placed within the HEAD [...]]]></description>
			<content:encoded><![CDATA[<h2>WTF is head js?</h2>
<p><a title="link opens in a new window" href="http://headjs.com" target="_blank">headjs</a> is a small script which can help speed up your site and comes bundled with a number of other very useful features.</p>
<h2>WTF do you mean?</h2>
<p>Headjs allows your javascript files to be loaded like images &#8211; completely separate from the page rendering process. Normally JavaScript is placed within the HEAD tag of a page (ideally, below CSS and metadata) which means your JavaScript files will load before the page rendering process, this in turn adds time for your page to display. The most simply fix for this is to move any JavaScript calls to the bottom of the page directly before the closing tag of the BODY. In addition to this, by adding Headjs you can also take advantage of some of it&#8217;s handy features.</p>
<h3>CSS Modenizer</h3>
<p>Headjs adds checks for browser support for various CSS properties and adds CSS classes to the HTML root so you can provide CSS styling appropriate to the capabilities of the browser. e.g.<br />
target CSS for browsers without box-shadow support:</p>
<pre>
.no-boxshadow .box {
   border: 2px solid #ddd;
}</pre>
<h3>HTML5 Enabler</h3>
<p>Headjs provides cross browser support for html5 tags &#8211; &lt;header/&gt;,&lt;article /&gt;,&lt;footer /&gt; etc.</p>
<h3>Browser Detector</h3>
<p>Headjs detects which browser is being used and applies a CSS class to the root element of the page. e.g &#8211; .lt-ie9 stands for less than IE9. It&#8217;s recommend to use feature detection instead of targeting specific browsers.</p>
<h3>And lots of other features</h3>
<p>Headjs also has a api and comes with lots of other features on top of the points mentioned above. Visit <a title="link opens in a new window" href="http://headjs.com" target="_blank">headjs</a> for more info. Finally, it&#8217;s worth keeping in mind this is a JavaScript dependent solution and you should make sure your site functionality isn&#8217;t reliant on this script.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cssmonkey.co.uk/blog/?feed=rss2&#038;p=17</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Responsive designs tools</title>
		<link>http://www.cssmonkey.co.uk/blog/?p=34</link>
		<comments>http://www.cssmonkey.co.uk/blog/?p=34#comments</comments>
		<pubDate>Sun, 20 Nov 2011 13:16:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Responsive design]]></category>
		<category><![CDATA[development]]></category>

		<guid isPermaLink="false">http://www.cssmonkey.co.uk/blog/?p=34</guid>
		<description><![CDATA[Responsive design is all the rage in web development at the moment. It basically entails making a website which is optimised to work on any web device &#8211; tablet, smartphone, desktop etc. Styling and layout are adjusted depending on the device size ensuring the best possible user experience across a range of platforms. Here&#8217;s a [...]]]></description>
			<content:encoded><![CDATA[<p>Responsive design is all the rage in web development at the moment. It basically entails making a website which is optimised to work on any web device &#8211; tablet, smartphone, desktop etc. Styling and layout are adjusted depending on the device size ensuring the best possible user experience across a range of platforms.</p>
<p>Here&#8217;s a quick rundown of a few of the tools I&#8217;ve found useful while building responsive websites&#8230;</p>
<h2>Responsive design tools</h2>
<h3><a title="link opens in a new window" href="http://protofluid.com/" target="_blank">Protofluid</a></h3>
<p>Protofluid is a tool designed for rapid prototyping responsive design. This desktop based app, provides an environment to test your site on a variety of device sizes and orientations. Device sizes available include Phones; BlackBerry Torch, Google Nexus One, iPhone, Motorola Droid, Tablets; BlackBerry Playbook, iPad, Samsung Galaxy Tab, Dell Streak. The only thing that lets this app down though is that you cannot scroll down the page you are testing.</p>
<h3><a title="link opens in a new window" href="http://resizemybrowser.com/" target="_blank">Resize My Browser</a></h3>
<p>Resize My Browser provides a quick and easy way to display content a different window sizes. It comes with a range of pre set sizes and you can also add your own custom sizes. Many browser add-ons such as firefox&#8217;s developer toolbar also provide this functionality.</p>
<h3><a title="link opens in a new window" href="http://www.electricplum.com/dlsim.html" target="_blank">Electric Plum iOS Web Browser Simulator</a></h3>
<p>This is a iPad and iPhone browser emulator for windows. A great time saver for testing your web apps. Features include JavaScript error detection, ability to save out screenshots and a full screen mode &#8211; handy for client presentations.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cssmonkey.co.uk/blog/?feed=rss2&#038;p=34</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Shazia Saleem&#8217;s new fashion site is launched</title>
		<link>http://www.cssmonkey.co.uk/blog/?p=20</link>
		<comments>http://www.cssmonkey.co.uk/blog/?p=20#comments</comments>
		<pubDate>Sun, 20 Nov 2011 12:38:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Latest work]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[Shopify]]></category>

		<guid isPermaLink="false">http://www.cssmonkey.co.uk/blog/?p=20</guid>
		<description><![CDATA[Shazia Saleem London is a high-end fashion label specialising in luxurious hand woven textiles of the finest quality. This site was built using the eCommerce platform Shopify.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.cssmonkey.co.uk/blog/wp-content/uploads/2011/11/shaziaHome.jpg"><img class="alignnone size-full wp-image-22" title="shaziaHome" src="http://www.cssmonkey.co.uk/blog/wp-content/uploads/2011/11/shaziaHome.jpg" alt="shaziasaleem.com - the homepage" width="400" /></a></p>
<p><a title="link opens in a new window" href="http://www.shaziasaleem.com" target="_blank">Shazia Saleem London</a> is a high-end fashion label specialising in luxurious hand woven textiles of the finest quality. This site was built using the eCommerce platform <a title="link opens in a new window" href="http://www.shopify.com/" target="_blank">Shopify</a>.</p>
<p><a href="http://www.cssmonkey.co.uk/blog/wp-content/uploads/2011/11/shaziaCollections.jpg"><img class="alignnone size-full wp-image-21" title="shaziaCollections" src="http://www.cssmonkey.co.uk/blog/wp-content/uploads/2011/11/shaziaCollections.jpg" alt="shaziasaleem.com - the collections page" width="400" /></a><br />
<a href="http://www.cssmonkey.co.uk/blog/wp-content/uploads/2011/11/shaziaProducts.jpg"><img class="alignnone size-full wp-image-23" title="shaziaProducts" src="http://www.cssmonkey.co.uk/blog/wp-content/uploads/2011/11/shaziaProducts.jpg" alt="shaziasaleem.com - the products page" width="400" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cssmonkey.co.uk/blog/?feed=rss2&#038;p=20</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Code standards &amp; best practice: snippet 1</title>
		<link>http://www.cssmonkey.co.uk/blog/?p=7</link>
		<comments>http://www.cssmonkey.co.uk/blog/?p=7#comments</comments>
		<pubDate>Sat, 17 Sep 2011 14:24:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Best practice]]></category>
		<category><![CDATA[coding standards]]></category>
		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://www.cssmonkey.co.uk/cssmonkey.co.uk/blog/?p=7</guid>
		<description><![CDATA[I work for a fairly large Digital Agency which has pretty much doubled in size in the few years I have worked there. As with most digital agencies our deadlines are usually pretty tight and it&#8217;s not unusual for multiple developers to work on a single project. Although working with a large team is great for the banter, it&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>I work for a fairly large Digital Agency which has pretty much doubled in size in the few years I have worked there. As with most digital agencies our deadlines are usually pretty tight and it&#8217;s not unusual for multiple developers to work on a single project. Although working with a large team is great for the banter, it&#8217;s not so good for creating maintainable and stable codebase. Every developer has there own approach/style of coding &#8211; mix this all together and you could potentially end up with a severely bloated codebase which difficult to understand and a absolute nightmare to update.</p>
<p>Over the next series of posts I&#8217;m going to detail some best practice techniques which result in good code consistency and easier to maintain projects.</p>
<h2>Define default Typography styling</h2>
<h3>Headings h1 &#8211; h6</h3>
<p>Define default styling for headings h1 &#8211; h6. The default styling should be defined at the top of the CSS file and modified as necessary for variations in styling i.e Styling specific to a page component.</p>
<p>Headings should always show a hierarchy indicating levels of importance, so your h1 should be in the largest font-size and h6 being the smallest.</p>
<h3>Links and other common content elements</h3>
<p>The same approach mentioned above should also be applied to common content elements such links, paragraphs, numbered lists, unordered list etc. Default styling for each common element should be defined at the top for the CSS file and overridden as necessary.</p>
<p>For links, make sure to define styling for each of the states &#8211; link, visited, hover, active, focus.</p>
<p>The selectors for each state is explained below&#8230;</p>
<ul>
<li>:link &#8211; this state can be used to define styling for when the link is not in use.</li>
<li>:visited &#8211; this state indicates the link has been used before, the link has already been clicked on.</li>
<li>:hover &#8211; this state indicates the link currently has the cursor/pointer hovering over it.</li>
<li>:active &#8211; indicates the link is in the process of being clicked.</li>
<li>:focus &#8211; same idea as :active but is used for when a user has tabbed to the link using the keyboard.</li>
</ul>
<p>When writing CSS, you can also bundle your selectors together by shared styling.</p>
<pre>a:link,a:visited {
color:#ec008c;
}
a:hover,a:active,a:focus {
color:#ff8cd1;
}</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.cssmonkey.co.uk/blog/?feed=rss2&#038;p=7</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

