<?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>nasarik.com - A Lancashire designer&#039;s journey through life, print and web design &#187; css</title>
	<atom:link href="http://nasarik.com/tag/css/feed/" rel="self" type="application/rss+xml" />
	<link>http://nasarik.com</link>
	<description>I&#039;m just a designer trying to make sense of the web, design and pretty much everything else</description>
	<lastBuildDate>Sun, 22 Jan 2012 21:42:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
  <link>http://nasarik.com</link>
  <url>http://nasarik.com/wp-content/themes/sandbox/images/nasarikfav.jpg</url>
  <title>nasarik.com - A Lancashire designer&#039;s journey through life, print and web design</title>
</image>
		<item>
		<title>Don&#8217;t be afraid of responsive design</title>
		<link>http://nasarik.com/responsive-designs/</link>
		<comments>http://nasarik.com/responsive-designs/#comments</comments>
		<pubDate>Sat, 03 Sep 2011 20:56:19 +0000</pubDate>
		<dc:creator>nasarik</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[bullet]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[dependant]]></category>
		<category><![CDATA[device]]></category>
		<category><![CDATA[dimension]]></category>
		<category><![CDATA[display]]></category>
		<category><![CDATA[experience]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[future]]></category>
		<category><![CDATA[hype]]></category>
		<category><![CDATA[img]]></category>
		<category><![CDATA[impact]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[journey]]></category>
		<category><![CDATA[Magazine]]></category>
		<category><![CDATA[maximum]]></category>
		<category><![CDATA[nasarik]]></category>
		<category><![CDATA[novice]]></category>
		<category><![CDATA[overview]]></category>
		<category><![CDATA[pixel]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[response]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[size]]></category>
		<category><![CDATA[Smashing]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[value]]></category>
		<category><![CDATA[version]]></category>
		<category><![CDATA[width]]></category>
		<category><![CDATA[window]]></category>

		<guid isPermaLink="false">http://nasarik.com/?p=1281</guid>
		<description><![CDATA[If you use Twitter, read Smashing Magazine or any of the other leading design blogs on the web, then no doubt you will be aware of responsive design and the impact that the industry knows it will have on all web developers and designers. If you don&#8217;t, then here is an overview of what it [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://farm7.static.flickr.com/6189/6109968044_50613e24d8.jpg" alt="responsive design" /></p>
<p>If you use Twitter, read Smashing Magazine or any of the other leading design blogs on the web, then no doubt you will be aware of responsive design and the impact that the industry knows it will have on all web developers and designers. If you don&#8217;t, then here is an overview of what it is and why I decided now was the time to get on-board.<span id="more-1281"></span></p>
<h2>So what is response design</h2>
<p>Responsive design is basically adapting a website to appear appropriately dependant on the device being used by the user. This has existed in web design for some time, particularly when a designer has needed to ensure that a site appeared correctly in all web browsers, and more notably IE6. Usual this was achieved by using media queries which detected the browser version and delivered the appropriate style sheet, eliminating the need for crude hacks or work-arounds to create a consistent experience for all.</p>
<p>Today with the introduction of CSS3, we are not simply limited to browser specific queries, we have much more control and can detect a browser screen size and deliver a set of specific styles to that as well. This new ability means that we can choose to build our projects with a set of structured options or alternatively with a fluid response meaning that one site can potentially work comfortably on many devices without a huge amount of work.</p>
<h2>A simple responsive experience, and why?</h2>
<p>With all the hype I simply couldn&#8217;t ignore the seemingly inevitable future for our industry, so I finally bit the bullet and gave it a go. Now, as I have only every really created fixed width designs my first job was to update all my values to percentages so that the design would scale effectively, however, I still wanted to keep a maximum site width, so in addition to the width:100%; value I added the max-width: value as well, specifying my desired pixel dimension (sorry, I know pixel!). So this would give me a desired maximum site look while still giving the overall flexibility of the percentages.</p>
<p>Once the scaling was complete (feel free to test this by resizing the browser window), I then did my research which took me to a great article on <a title="See the article here - Responsive Web Design: What It Is and How To Use It" href="http://coding.smashingmagazine.com/2011/01/12/guidelines-for-responsive-web-design/" target="_blank">Smashing Magazine</a>. Articles like this give invaluable information on all aspects of the responsive design process and I would recommend taking your time to find the most appropriate option before really trying to get to grips with responsive designs. For me however, I explored the <code>'@media </code><code>screen' function</code>, this gave me the control to adapt my design when hitting certain screen dimensions, for example the first thing I tried was to remove content when the screen dimension was that of an iPhone, which looked like this:-</p>
<p>@media screen and (max-width:400px) {<br />
#primary {display:none;}<br />
}</p>
<p>You will see that if you reduce the browser window to below this dimension the sidebar of my site disappears, and the same happens on the iPhone, and that is how the responsive journey of nasarik.com began.</p>
<h2>Stumbling blocks</h2>
<p>I hit a few novice snags along the way which nearly caused me to give up, one of which was the iPhone still scaling my site even though I had included queries. Don&#8217;t panic a simple meta value in your &lt;head&gt; ensures that the iPhone behaves as you would expect and here it is &#8211; &lt;meta name=&#8221;viewport&#8221; content=&#8221;width=device-width; initial-scale=1.0&#8243;&gt;</p>
<p>Finally, testing can be an issue particularly if you don&#8217;t have an iPhone, so try using <a href="http://iphone4simulator.com/" target="_blank">http://iphone4simulator.com/</a> it seems to render perfectly and is free.</p>
<h2>Conclusion</h2>
<p>Responsive design isn&#8217;t to be feared, play with it, try and break your site and see what happens.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://nasarik.com/responsive-designs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Are standard blue hyperlinks conducive in modern web design?</title>
		<link>http://nasarik.com/blue-hyperlinks-necessary/</link>
		<comments>http://nasarik.com/blue-hyperlinks-necessary/#comments</comments>
		<pubDate>Wed, 20 Jul 2011 12:52:16 +0000</pubDate>
		<dc:creator>nasarik</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[activity]]></category>
		<category><![CDATA[animation]]></category>
		<category><![CDATA[Â  Blue]]></category>
		<category><![CDATA[BBC]]></category>
		<category><![CDATA[blue]]></category>
		<category><![CDATA[Cbeebies]]></category>
		<category><![CDATA[Children]]></category>
		<category><![CDATA[colour]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[designer]]></category>
		<category><![CDATA[direction]]></category>
		<category><![CDATA[display]]></category>
		<category><![CDATA[emphasis]]></category>
		<category><![CDATA[expectation]]></category>
		<category><![CDATA[gravitate]]></category>
		<category><![CDATA[hint]]></category>
		<category><![CDATA[History]]></category>
		<category><![CDATA[hover]]></category>
		<category><![CDATA[href]]></category>
		<category><![CDATA[Hyperlinks]]></category>
		<category><![CDATA[interactivity]]></category>
		<category><![CDATA[learning]]></category>
		<category><![CDATA[prioritise]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[purpose]]></category>
		<category><![CDATA[standard]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[width]]></category>

		<guid isPermaLink="false">http://nasarik.com/?p=1039</guid>
		<description><![CDATA[Recently while proofing a design I had created a colleague of mine asked &#8220;Why do we not use blue links?&#8221;, to which my immediate response should have been &#8216;Why should we use blue links!&#8221;. However, to avoid an argument I let him speak about how users were used to the standard blue links shown on [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://farm6.static.flickr.com/5068/5613227656_f9e1b88457.jpg" alt="Blue Hyperlinks, are they really necessary in modern web design?" /></p>
<p>Recently while proofing a design I had created a colleague of mine asked &#8220;Why do we not use blue links?&#8221;, to which my immediate response should have been &#8216;Why should we use blue links!&#8221;. However, to avoid an argument I let him speak about how users were used to the standard blue links shown on web pages and anything else could confuse, but does it and can it?</p>
<p><span id="more-1039"></span>As a designer I try to understand aesthetics and usability in equal measure in an attempt to produce the best user experiences for the websites I create. Blue links as a standard however, leave me in an uncomfortable place; these have been the standard in web design since the beginning, but just because something has always been this way doesn&#8217;t mean it should never change, surely?</p>
<p>In my opinion there are three factors at work here, these are:-</p>
<ul style="margin-bottom: 15px;">
<li>History</li>
<li>Design</li>
<li>Usability</li>
</ul>
<p>So I feel I should touch on each separately&#8230;</p>
<h2>History</h2>
<p><img src="http://farm6.static.flickr.com/5188/5613273624_8e26ed9b48.jpg" alt="The web has moved so far since its inception that it is time to let some things go" width="450" height="320" /></p>
<p>As I mentioned above the blue link has been part of the modern web for as long as I can remember, which has created an expectation in some peoples minds as to how links should be represented online. Having understood this and accepted this concept it still doesn&#8217;t change the fact that blue link was conceved by someone technical, a logical thinker or programmer whose main objective was to keep plain text and active content immediately and visibly separate, in a world were web design hadn&#8217;t been born and where options were limited. Blue is naturally a vivid display colour so choosing this colour to highlight links was an easy choice. Yet things have changed massively since then, visual displays have improved, the addition of images and interactivity altered the web beyond all recognition, so surely we can move on and create new standards?!</p>
<h2>Design</h2>
<p><img src="http://farm6.static.flickr.com/5105/5613273600_839ebb7f43.jpg" alt="Children are not expecting blue links so learn intuitively" width="450" height="320" /></p>
<p>The history segment above can be argued with I&#8217;m sure, but here in design the blue link is the enemy! (Well in my mind it is anyway). Over exaggerated colours, animated gifs and cramped content are now becoming a thing of the past, or more accurately a remnant of the 1990&#8242;s. When the Internet was born it was the playground for technical geeks who communicated and shared, the interface that this occurred within was simply not important. Now however, users are born into the Internet, schools actively encourage very young children to play online and it all seems to come very naturally.</p>
<p>Every step of this modern learning is down to how the pages look and react; would children be as inclined to learn about web pages if they all looked and behaved the same. Is it not also interesting how as design has become part of the modern web the older generation embrassed the internet at a similar rate, and could this mean they are learning in the same way? The aesthetics of objects are tremedously important and dictate how we humans behave towards all sorts of things like magazines, advertising,  foods, books and even other people, but when the web was in its infancy the way the web looked was a relative low priority, with technical leaps being the main focus. Now however, the technology has slowed and people are now able to take a moment to look at the internet in a different way, with that slower pace comes an opportunity to start advancing the web in different other ways than just technical, shoudn&#8217;t now be the time where we can creatively improve the aethetics of the internet while at the same time improving users experiences, in the same way as we have seen with all other products over the years.</p>
<h2>Usability</h2>
<p><img src="http://farm6.static.flickr.com/5026/5612694157_39397d50f6.jpg" alt="The BBC Cbeebies website is a great example of how children can learn to use websites" width="450" height="320" /></p>
<p>With this in mind I looked at the BBC <a href="http://www.bbc.co.uk/cbeebies/" target="_blank">Cbeebies</a> website, here there are no blue links or at least very few. This is where my daughter took her first steps into the web and with no special guidance has been able to navigate this website and many sites since easily and instinctively since she was 2 years old. So how has she grasped this so easily? Well the BBC have used interactivity, anything that can be clicked moves or changes making its purpose really obvious to the user, and not a hint of blue or even plain text to be seen. This method moves away from the trusted blue links convention and assumes that users hover around a page, anything that looks different or interesting automatically makes a user gravitate towards it, once some activity is displayed, you click! &#8211; makes sense really. So if users are able to intuitively learn how a page works quickly and the design actively helps prioritise content either with colour, images, animation or activity then why shouldn&#8217;t it? Young children can grasp this without any direction so why shouldn&#8217;t everyone else, maybe we just need to have a little more faith?</p>
<h2>Conclusion</h2>
<p>Obviously there can be appropriate uses for blue links and I think search engines are a great example of this, I just feel that as long as links are obvious either with using colour or images that add to a design, or activity that emphasis the link we should be able to move forward away from this early method without causing any degradation of user experience.</p>
<p>Let me know what you think&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://nasarik.com/blue-hyperlinks-necessary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Will I bite the HTML and CSS bullet in 2011?</title>
		<link>http://nasarik.com/html-and-css-2011/</link>
		<comments>http://nasarik.com/html-and-css-2011/#comments</comments>
		<pubDate>Fri, 31 Dec 2010 16:14:21 +0000</pubDate>
		<dc:creator>nasarik</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[2010]]></category>
		<category><![CDATA[2011]]></category>
		<category><![CDATA[compatibility]]></category>
		<category><![CDATA[html5]]></category>

		<guid isPermaLink="false">http://nasarik.com/?p=855</guid>
		<description><![CDATA[2010 has been a time when the next stage of web design was born with the introduction to most modern web browsers of HTML5 and CSS3.  I have dabbled and experimented as I expect most other designers have throughout the year, yet compliance always bugs me. The technology I can see on the horizon excites [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://farm6.static.flickr.com/5162/5309406629_2d0f3b1fcc.jpg" alt="Will I bite the HTML and CSS bullet in 2011?" /></p>
<p>2010 has been a time when the next stage of web design was born with the introduction to most modern web browsers of HTML5 and CSS3.  I have dabbled and experimented as I expect most other designers have throughout the year, yet compliance always bugs me.</p>
<p><span id="more-855"></span>The technology I can see on the horizon excites me, CSS3 and HTML5 will help to make web design a far more fluid process, HTML5 will improve structure and CSS3 will reduce the need for as many images within the design, while together these languages will bring a far more interactive web to our browsers without the need for too much additional code.</p>
<p>As always with new technology come new problems, with browser compatibility yet again at the top of the list.  I know that HTML5 can be supported on all browsers with some clever Javascript and CSS3 can simply be left to degrade but is that what I really want to be doing with the sites I create? No, it isn&#8217;t, I want my websites to be identical no matter how the user visits them so complicating the build process with Javascript and another round of HTML hacks doesn&#8217;t fill my heart with joy.</p>
<p>For me, both these technologies are massively important and exciting steps sending the web in the right direction; but that is all they are for me, steps.  Currently my site is based on the HMTL5 ready Starkers theme and I already incorporate some CSS3 values to the sites I build, but I will be waiting to see how quickly the compliance machine moves in 2011 before I commit fully to using them as standard. 2011 is sure to be an interesting and progressive year, I just think 2012 may be the year to get really excited about designing for the web.</p>
<p>Wishing you all a happy and prosperous 2011</p>
]]></content:encoded>
			<wfw:commentRss>http://nasarik.com/html-and-css-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

