<?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>HawkinzWeb Blog &#187; Web Design</title>
	<atom:link href="http://hawkinzwebdesigns.com/blog/category/web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://hawkinzwebdesigns.com/blog</link>
	<description>Making the internet your friend</description>
	<lastBuildDate>Thu, 29 Apr 2010 11:16:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How Accessible is your website?</title>
		<link>http://hawkinzwebdesigns.com/blog/2009/12/how-accessible-is-your-website/</link>
		<comments>http://hawkinzwebdesigns.com/blog/2009/12/how-accessible-is-your-website/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 18:18:00 +0000</pubDate>
		<dc:creator>dehawkinz</dc:creator>
				<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://hawkinzwebdesigns.com/blog/?p=84</guid>
		<description><![CDATA[I recently received a link via Facebook for a site, which failed to open because I was viewing the site via a mobile browser.
When I pointed this out to the site owner, their comment was &#8220;well I don&#8217;t want people on phones on my site&#8221;.  Whilst their response was meant in jest, it did [...]]]></description>
			<content:encoded><![CDATA[<p>I recently received a link via Facebook for a site, which failed to open because I was viewing the site via a mobile browser.</p>
<p>When I pointed this out to the site owner, their comment was &#8220;well I don&#8217;t want people on phones on my site&#8221;.  Whilst their response was meant in jest, it did actually highlight a very important point that many web designers fail to appreciate when designing websites with ever more advanced and complex content structures.  Whilst Browsers are becoming expected to deal with ever more complex scripting and dynamic content structures, the mobile browser is still often unable to process even css let alone javascript, php and flash.</p>
<p>As an example of how not being able to read css can affect a page, see the two following examples:</p>
<p><a href="http://www.hawkinzwebdesigns.com/index2.html" target="_blank">Hawkinzwebdesigns</a> &#8211; this uses css to structure the page layout<br />
<a href="http://www.hawkinzwebdesigns.com/index4.html" target="_blank">Hawkinzwebdesigns</a> &#8211; this has css disabled</p>
<p>And with the ever increasing use of phones, and mobile computing devices to connect with the internet, it is becoming an increasingly important aspect that web designers have to consider.</p>
<p>So what does this mean &#8211; most websites built more than 5 years ago will be largely accessible to mobile browsers, but newer websites will be less likely to be so &#8216;readable&#8217;  There has been a move by some companies to detect mobile browsers and build mobile browser friendly  websites, eg facebooks mobile website is m.facebook.com which reduces the content per page to make them faster loading, and keeps what content is provided to the &#8216;basics&#8217;.</p>
<p>One easy solution for website designers is to include a &#8220;mobile&#8221; link near the top of their home page to link to a more mobile friendly version of the site.  Making a mobile friendly copy does mean more work, as you will find yourself duplicating content often.  But at the heart of mobile content is the idea of presenting information in a more easily manageable way.  As Facebook shows, you <strong>can</strong> still use dynamic content in a mobile page, but you have to re-think how you present the information.</p>
<p>This is the ultimate question a good website designer has to face repeatedly &#8211; &#8220;how am I presenting the information, and is it the most appropriate way for my viewer?&#8221;  NOTE: the best way for your viewer does not always  mean the lowest common denominator, nor does it always mean the most eye-catching way.  Often it is about understanding where your viewer is coming from, and what they are expecting to see.</p>
<img src="http://hawkinzwebdesigns.com/blog/?ak_action=api_record_view&id=84&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://hawkinzwebdesigns.com/blog/2009/12/how-accessible-is-your-website/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Creating a successful Splash Page</title>
		<link>http://hawkinzwebdesigns.com/blog/2009/10/creating-a-successful-splash-page/</link>
		<comments>http://hawkinzwebdesigns.com/blog/2009/10/creating-a-successful-splash-page/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 23:02:00 +0000</pubDate>
		<dc:creator>dehawkinz</dc:creator>
				<category><![CDATA[Splash Pages]]></category>
		<category><![CDATA[Traffic Exchanges]]></category>
		<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://hawkinzwebdesigns.com/blog/?p=65</guid>
		<description><![CDATA[It is a well known fact that on a traffic exchange it is better to use a splash page, preferably a personalised one, rather than an affiliate page, but a question I am often asked is how do I make a splash page?
This post is not going to talk about the design mechanics of building [...]]]></description>
			<content:encoded><![CDATA[<p>It is a well known fact that on a traffic exchange it is better to use a splash page, preferably a personalised one, rather than an affiliate page, but a question I am often asked is how do I make a splash page?</p>
<p>This post is not going to talk about the design mechanics of building a splash page, but rather what you should be putting in, and leaving out, of your splash page.</p>
<p>Firstly you want to ask yourself<br />
&#8220;what is unique or special or different about what I am promoting?&#8221;<br />
ie, why should someone be looking at what you are offering?  Related to this &#8211; if you are promoting an affiliate page &#8211; &#8220;why should they sign up under me rather than someone else?&#8221;</p>
<p>Once you have an idea of what it is that you can focus on, the next question is<br />
&#8220;what is the purpose of my splash page?&#8221;<br />
ie &#8211; Are you trying to make them sign up straight away?  Go and get more information?  Go and visit a different page? Collect their contact details?<br />
This is important because it will affect what and how you present the information you include on the page.</p>
<p>You now should have a good idea of what you want to say, so how are you going to say it?</p>
<p>There has been a trend towards including video on splash pages as there is a school of thought that says videos are more effective than static pages.  Whilst in general terms this may be true, there are a 2 points to bear in mind:</p>
<ol>
<li>There has been an increase in people blocking videos and scripts, which means they may not be seeing your video.</li>
<li>The video needs to be very fast loading, and make its point in the first few seconds.</li>
</ol>
<p>Because of the issue of people blocking videos / scripts, if your splash page is relying on just your video to make its point, then you will be unable to make any impact on the viewer, and so your page is worse than using an affiliate page.<br />
The video needs to make its point fast, because most people will only be viewing your page for just 2 or 3 seconds &#8211; so if you can not grab their attention in that time then you have lost the opportunity.<br />
Therefore you need to consider the video to be at best a supplement to the main message rather than replacing it.</p>
<p>Likewise, if your splash page relies too heavily on scripts &#8211; <strong>especially if you are using a script-driven signup form</strong> &#8211; then you will be excluding some potential respondants.  Scripts generally are not recommended in a splash page as they will slow the loading time as the browser will take the time to load the script, and if the script is positioned before the sales pitch, then the content will load slower and may not even be seen! (remember the page only has a 2 -3 second viewing window for most surfers)</p>
<p>Try to avoid using an all-in-one graphic that contains all your message as:<br />
1. they tend to load slower because the file size is bigger<br />
2. if they graphic fails to load, then all your message is lost.<br />
If possible, try to use a mixture of text and graphics so that your eggs are not all in 1 basket.</p>
<p>There is no &#8216;golden formula&#8217; for making a winning splash page &#8211; despite what some marketers will tell you &#8211; remember you are marketing to people, not robots and individuals will respond differently to the same input.  Some people will respond better to humour, some to facts/statistics, some to emotional factors.  Therefore you need to test and adapt your content to see what works best.  You will probably find that you end up with a variety of pages that are &#8216;targetted&#8217; at different people.</p>
<p>Try and get a punchy, attention grabbing &#8216;headline&#8217; &#8211; something near the top of the page to grab their attention away from whatever else it was they were doing when they saw your page &#8211; it does not have to be text, it could be a graphic.<br />
Next, you want to get your primary message across in 2 or 3 short, concise statements &#8211; remember the idea of a splash page is that it is a quick taster of more, not a full 4 course meal<br />
Finally, the call to action &#8211; this is what you want the viewer to do next eg click a link, enter contact details, etc</p>
<img src="http://hawkinzwebdesigns.com/blog/?ak_action=api_record_view&id=65&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://hawkinzwebdesigns.com/blog/2009/10/creating-a-successful-splash-page/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
