<?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>Paper to Pixel &#187; design tips</title>
	<atom:link href="http://www.papertopixel.org/category/design-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.papertopixel.org</link>
	<description>web design tips for graphic designers</description>
	<lastBuildDate>Sun, 08 Aug 2010 09:05:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Great Advice on Writing Copy for the Web</title>
		<link>http://www.papertopixel.org/2010/great-advice-on-writing-copy-for-the-web/</link>
		<comments>http://www.papertopixel.org/2010/great-advice-on-writing-copy-for-the-web/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 11:16:50 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[recommendations]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=557</guid>
		<description><![CDATA[Rockable Press, the people behind the sites like Freelance Switch have just published a new and great ebook helping you to write better copy for your sites.
As this is an issue we all constantly battle with, from our clients asking us how to do it to even ourselves trying to come up with the best [...]]]></description>
			<content:encoded><![CDATA[<p>Rockable Press, the people behind the sites like Freelance Switch have just published a new and great ebook helping you to write better copy for your sites.</p>
<p>As this is an issue we all constantly battle with, from our clients asking us how to do it to even ourselves trying to come up with the best copy for our sites I thought I&#8217;d let you know about it.</p>
<p><a href="https://www.e-junkie.com/ecom/gb.php?cl=12635&amp;c=ib&amp;aff=103662" target="ejejcsingle">You can find the ebook and more info about it on Rockable Press website</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2010/great-advice-on-writing-copy-for-the-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ignore site maps, create functionality ones instead</title>
		<link>http://www.papertopixel.org/2010/ignore-site-maps-create-functionality-ones-instead/</link>
		<comments>http://www.papertopixel.org/2010/ignore-site-maps-create-functionality-ones-instead/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 11:55:18 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=554</guid>
		<description><![CDATA[How many CMS sites have you worked on last year?
OK, maybe not many. Maybe you still work in the Jurassic era and do all changes for your clients in the code. The majority of sites these days require some form of a CMS systems though. And that means their owners have full control over their [...]]]></description>
			<content:encoded><![CDATA[<p><strong>How many CMS sites have you worked on last year?</strong></p>
<p><strong>OK, maybe not many. Maybe you still work in the Jurassic era and do all changes for your clients in the code. The majority of sites these days require some form of a CMS systems though. And that means their owners have full control over their content. Also, they now decide what goes where. Very often your expertise in that field is no longer required.</strong></p>
<p>Web design has definitely changed and you can either cop on or extinct. Not a great prospect, eh? Two years ago you could have shown off how great you are by your knowledge of creating the sites structure, today the client knows better. And very often doesn&#8217;t want to listen to you.</p>
<p>Good news! There is something new though they need your help with.</p>
<p><span id="more-554"></span></p>
<p>Functionality. Content management is no longer a problem but how the site works is. And it&#8217;s often your call how that gallery works, how contact form processes the information or how product catalog indexes all items. It&#8217;s also your job now to communicate those ideas to clients in a clear and<br />
understandable way.</p>
<p>Therefore from now on, ignore site maps. They are a massive waste of time. Focus your energy on functionality maps.</p>
<p>Here&#8217;s how to make one.</p>
<p>List all pages with a list of functionality beside each page. If necessary draw a quick step by step sketch of how certain functionality will work. Think of it as a functionality story board.</p>
<p>Help your client understand what you are suggesting to them. And remember, the main rule of functionality is that it has to be easy to operate and easy to understand for the visitor.</p>
<p>Last thing, consult your developer before you pass your functionality map to the client. These days you can develop practically any system with time and cost being the only things that may stand on the way.</p>
<p>And they very often do.</p>
<p><strong>&#8211;&gt; Something extra to think about: &lt;&#8211;</strong></p>
<p>- when was the last time you checked how your desired functionality works? Do you visit scripts producers sites and view demos of their systems? Do you ask your developers for advice on what are the best solutions for what you want to achieve? Or do you just play smart?</p>
<p>- which web development blogs are you subscribed to? Do you follow new technologies and issues with the existing ones?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2010/ignore-site-maps-create-functionality-ones-instead/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Is Selling Websites Really That Easy? &#8211; my new guest post</title>
		<link>http://www.papertopixel.org/2009/is-selling-websites-really-that-easy-my-new-guest-post/</link>
		<comments>http://www.papertopixel.org/2009/is-selling-websites-really-that-easy-my-new-guest-post/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 12:52:26 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=501</guid>
		<description><![CDATA[I just published a new guest post on Graphic Design Blog entitled &#8220;Is Selling Websites Really That Easy?&#8221;.
In it I discuss some things that can help you understand better what you sell.
Link to the post: http://www.graphicdesignblog.co.uk/is-selling-websites-really-that-easy-6-steps-that-can-help-you-understanding-more-what-you-sell/
]]></description>
			<content:encoded><![CDATA[<p>I just published a new guest post on Graphic Design Blog entitled &#8220;Is Selling Websites Really That Easy?&#8221;.</p>
<p>In it I discuss some things that can help you understand better what you sell.</p>
<p>Link to the post: <a href="http://www.graphicdesignblog.co.uk/is-selling-websites-really-that-easy-6-steps-that-can-help-you-understanding-more-what-you-sell/" target="_blank">http://www.graphicdesignblog.co.uk/is-selling-websites-really-that-easy-6-steps-that-can-help-you-understanding-more-what-you-sell/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/is-selling-websites-really-that-easy-my-new-guest-post/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>About the baseline myth and 3+ tutorials on how to use baseline on the web</title>
		<link>http://www.papertopixel.org/2009/the-baseline-myth-and-3-tutorials-on-how-to-use-baseline-on-the-web/</link>
		<comments>http://www.papertopixel.org/2009/the-baseline-myth-and-3-tutorials-on-how-to-use-baseline-on-the-web/#comments</comments>
		<pubDate>Sat, 05 Sep 2009 15:02:08 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=470</guid>
		<description><![CDATA[Designers love baseline. 
I actually found this sentence amongst my notes the other day. It sounded true from the start yet still got me thinking. Yes, designers love baseline. It helps so much, doesn’t it?  It keeps copy organized, especially with multicolumn layouts.

There are probably countless examples of great grids where baseline plays important role [...]]]></description>
			<content:encoded><![CDATA[<p><img style="float: right;" src="http://www.papertopixel.org/blog/wp-content/uploads/2009/09/base1.jpg" alt="base" /><strong>Designers love baseline. </strong><br />
<strong>I actually found this sentence amongst my notes the other day. It sounded true from the start yet still got me thinking. Yes, designers love baseline. It helps so much, doesn’t it?  It keeps copy organized, especially with multicolumn layouts.<br />
</strong><br />
There are probably countless examples of great grids where baseline plays important role and numerous books featuring great examples of them. I bet your library is full of those books.</p>
<p>When it comes to the web the situation is somewhat, well, &#8230; strange.</p>
<p><span id="more-470"></span></p>
<p>You can clearly see the lack of baseline on many websites. And since they are generally multicolumn it is even more noticeable.</p>
<p>I asked few of my graphic designer friends would they use baseline on their web projects and their replies were quite surprising. Most of them didn’t realize that you can use baseline on the web. They thought it was one of those print design features that you can not recreate online.</p>
<p>It sounded as if it a baseline on the web was a myth. But it isn’t. You can easily base your next web project on it.</p>
<p>Have a look at our own site with baseline on.</p>
<p><img src="http://www.papertopixel.org/blog/wp-content/uploads/2009/09/base.jpg" alt="base" /></p>
<p><strong>So, how do you do it?</strong><br />
On a design level, the same way as with print. Set your baseline and base your design on it.</p>
<p><strong>When it comes to coding there are few techniques that can help you with setting your type to baseline. I compiled 3+ great tutorials on how to do it.</strong></p>
<p>1.<a href="http://dev.opera.com/articles/view/setting-web-type-to-a-baseline-grid/" target="_blank"> Setting Web type to a baseline grid &#8211; Dev.Opera</a></p>
<p>2. <a href="http://www.alistapart.com/articles/settingtypeontheweb" target="_blank">Setting Web type to a baseline grid &#8211; AList Apart</a></p>
<p>3. <a href="http://forabeautifulweb.com/blog/about/improve_your_web_typography_with_baseline_shift/" target="_blank">Improve your web typography with baseline shift &#8211; For a beautiful web</a></p>
<p>3+. <a href="http://baselinecss.com/" target="_blank">Not really a tutorial but a great and helpful tool. A Baseline CSS-framework on which you can base your layouts. It’s well worth trying it out.</a></p>
<p>Do you have any examples of your sites with baseline? Post them up in comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/the-baseline-myth-and-3-tutorials-on-how-to-use-baseline-on-the-web/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Designing for e-commerce #1: what do you need to know to begin</title>
		<link>http://www.papertopixel.org/2009/designing-for-e-commerce-1-what-to-you-need-to-know-to-begin/</link>
		<comments>http://www.papertopixel.org/2009/designing-for-e-commerce-1-what-to-you-need-to-know-to-begin/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 08:27:30 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[e-commerce]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=376</guid>
		<description><![CDATA[I guess we all remember the days when things were simple. You would work only on what you were best at in the design and what would give you the joy of working. And ignore anything else.
Nowadays the situation seems more complicated. The world and a workplace demand more and more and even the design [...]]]></description>
			<content:encoded><![CDATA[<p><strong>I guess we all remember the days when things were simple. You would work only on what you were best at in the design and what would give you the joy of working. And ignore anything else.</strong></p>
<p><strong>Nowadays the situation seems more complicated.</strong> The world and a workplace demand more and more and even the design profession hasn’t escaped that.</p>
<p>I recently met with a good number of my design friends and clients and most of them mentioned a slight discomfort they feel with the more demanding web work they are being asked to quote for. It’s one thing to price a simple website but it’s something completely different to imagine how much work is involved in a bigger web project like e-commerce for example.</p>
<p><span id="more-376"></span></p>
<p>What really struck my friends was the complexity of the work involved. It’s not just a layout and content placed on a page as one of them put it. There are way more things to consider even before you begin.</p>
<p><strong>So in order to make things easier for them and many of you I decided to create a short series of tips for designing for e-commerce.</strong></p>
<p>We start off today with a list of what you need to find out from your client before you even decide on the full scope of work for the project.</p>
<p>When you look closely at most average shops, at first glance they all seem to work the same. There is a product listing, detailed overview of a product and a checkout. And that seems to be it.</p>
<p>Well, in most cases it is. Although in order to know exactly what functionality you need to design for, you need to find out few things from your client:<br />
<strong><br />
1. Why do they want e-commerce site in the first place</strong><br />
As silly as this question sounds it actually makes sense. I guess in order to create a perfect shop for your client you need to know what are their reasons and most importantly their plans for the new shop.<br />
Is it going to be selling few products only or will it grow and expand over time. This will certainly affect your designs so it’s better to know it from the start.</p>
<p><strong>2. Is it going to be e-commerce alone or will other website functionality be required?</strong><br />
By default e-commerce systems apart from their standard functionality allow very limited, if any content management features. Therefore find out whether your client does not require a Content Management System to manage additional pages in the shop.</p>
<p>Your client may also want to run a blog, or set up internet forums to interact with his clients and these obviously increase your scope of work considerably.</p>
<p><strong>3. Try to find out how many products do they expect to be selling</strong></p>
<p>Depending on the answer you will have to design product presentation that can handle whatever number is mentioned and also allow for the shop to grow if needs be.</p>
<p><strong>4. How many categories do they foresee for their products.</strong><br />
A major part of e-commerce interface is categories listing and in order to design it right you need to now roughly how many categories there are going to be. Will there be any subcategories as well? How does your client want to structure their categories listing? You may have a say on that last one but still it is your client who may dictate the shops structure.<br />
<em><br />
A tip, always assume that the number of categories will change and design thier listing to allow for that.</em></p>
<p><strong>5. Does your client plan any user interaction</strong></p>
<ul>
<li> will they require user registration</li>
<li> user reviews</li>
<li> recommended products</li>
<li> product of the day/week/month</li>
</ul>
<p>These obviously have to be included in the design as well and very often interactive elements are the most problematic to design for.</p>
<p><strong>It is easy for things to go wrong when you work with e-commerce project.</strong> Unfortunately one of the characteristics of the medium is that it can grow and in most cases it will. Your design has to reflect that.</p>
<p>When designing for e-commerce, just like with creating layouts for CMS sites you design for change and that can take a considerable amount of your time which you should factor in for.</p>
<p>Nonetheless if you have all the information you need then unless there is a considerable change of plans you shouldn’t have any problems with creating your layouts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/designing-for-e-commerce-1-what-to-you-need-to-know-to-begin/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>7+ things you need to master to call yourself a professional web designer</title>
		<link>http://www.papertopixel.org/2009/7-things-you-need-to-master-to-call-yourself-a-professional-web-designer/</link>
		<comments>http://www.papertopixel.org/2009/7-things-you-need-to-master-to-call-yourself-a-professional-web-designer/#comments</comments>
		<pubDate>Fri, 24 Jul 2009 09:28:47 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[general web design]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=344</guid>
		<description><![CDATA[Have you heard of that brochure by a Dutch studio, The Stone Twins which entire print run was taken to Dutch Army and soldiers fired bullets through each of copies printed? Amazing idea isn’t it?
I love such stories behind print artworks. They are retold, they inspire and very often they live longer than the piece [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Have you heard of that brochure by a Dutch studio, The Stone Twins which entire print run was taken to Dutch Army and soldiers fired bullets through each of copies printed? Amazing idea isn’t it?</strong></p>
<p><strong>I love such stories behind print artworks. They are retold, they inspire and very often they live longer than the piece itself.  And they are fun to listen, at least to designers anyway.</strong></p>
<p>But what do you hear when it comes to the web though? There aren’t many stories about websites. Not as exciting anyway. On one end there’s the technology, the boring bit. On the other, there are numbers, statistics. Metrics that prove whether the layout you designed was successful or not and whether the site brought any more business to your client. Or was it just another website on the net that simply was just there?</p>
<p><strong>And the only stories you commonly hear are those about websites that failed.</strong> Sites that costed huge amounts of money but never really brought any business to their owners.</p>
<p><span id="more-344"></span></p>
<p><strong>I guess as a designer you don’t want any of your websites to appear in one of those stories, right? </strong></p>
<p><strong>The good news is that it’s not difficult to do so.</strong> Just like with print design there is a set of skills and knowledge you need to master and you’re on a straight path to designing beautiful and successful sites. Of course it’s hard work but hey, it’s just like with anything in life, isn’t it?</p>
<p><strong>So cutting to the chase, what knowledge you should master to call yourself a professional web designer? </strong></p>
<p><strong>1. You have to understand how the web works and realize one important thing, users do not visit your sites for their design.</strong> They come there for information and that is the only thing that matters to them. The only people interested solely in your designs are your fellow designers. And you generally do not design for them.</p>
<p><strong>2. Realize that usability, the way you make it easy for your visitor to use the site is the most crucial thing in web design.</strong> In other words, if your users can’t browse through the site easily they won’t stay and won’t come back. Imagine also what sort of image of the company such website gives.</p>
<p><strong>3.  Learn the technology behind the web.</strong> How information is passed between server and a browser.<br />
Just like with print design where you have to learn the basics of print processes, on the web you need to know how the technology running the show works.</p>
<p>In addition you should learn as much as you can, mainly through experience I am afraid, of how various browsers interpret the code and what are their limitations. This comes usually handy when you design a site that uses modern technologies but you still want it to work on older browsers.</p>
<p><strong>4.  Discover how to organize content on the website. </strong>It simply works much differently than with print.<br />
Learn how users read on the web, what helps them to scan your copy and find information most relevant to what they are looking for. Also you should know what makes great copy on the web and how to write a content that focuses on fulfilling your users needs.</p>
<p><strong>5. In addition to that learn how to structure the entire site.</strong> Just so that your user not only will enjoy reading the copy but also will have no problems finding all the information they need. Master how to make the whole experience of moving from one information to the other seamless and enjoyable.<br />
<strong><br />
6.  Understand how the code works.</strong> If you design the site you should have at least a basic understanding of it. That knowledge will show you what you can do and what might cause you problems. But by all means you don’t have to know how to code.</p>
<p><strong>7. It is also good to investigate actual limitations of the design material you can use. </strong>Fonts, colors and images all work differently than with print. Once you know the difference the whole process of design will become much easier for you. Otherwise there may be some not so nice surprises waiting for you at the end of the road.</p>
<p><strong>7+. And most importantly, view and analyze other sites. </strong>Especially those really successful ones. Just like when you were learning your graphic design by viewing works by design masters. But pay more attention to structure, navigation and usability not to design elements on those sites. This is what your visitors will be paying attention on your sites too.</p>
<p>Mastering this knowledge will have another major effect on your web design skills apart from making your sites work for your client. It will also build a great confidence in your skills. And there is nothing worse that be working on a project and feeling that you may not be good enough to actually be doing it.</p>
<p>So, over the next couple of weeks I will be posting here roundups of links to great articles and tutorials on each of the skills mentioned in the article. These should give you a good foundation to start mastering what you need to know to call yourself a professional web designer.</p>
<p>But for now, if you have any interesting stories behind websites please share them with us in comments here.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/7-things-you-need-to-master-to-call-yourself-a-professional-web-designer/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Why you need a call to action on a website and few tips on how to create one</title>
		<link>http://www.papertopixel.org/2009/why-you-need-a-call-to-action-on-a-website-and-few-tips-on-how-to-create-one/</link>
		<comments>http://www.papertopixel.org/2009/why-you-need-a-call-to-action-on-a-website-and-few-tips-on-how-to-create-one/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 21:07:05 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[web usability]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=305</guid>
		<description><![CDATA[Who is in charge of how your visitor completes the objective you set for him on your site? You? Or do you leave that to the visitor himself to figure out?

Let&#8217;s face it, every website owner has an objective they want their visitors to complete. There&#8217;s no mystery there. You for instance may want your [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Who is in charge of how your visitor completes the objective you set for him on your site? You? Or do you leave that to the visitor himself to figure out?<br />
</strong><br />
Let&#8217;s face it, every website owner has an objective they want their visitors to complete. There&#8217;s no mystery there. You for instance may want your visitors to visit your portfolio and then get in touch. Another company may want their visitors to see some testimonials and make appointment. Or make appointment straight away. There could be millions of objectives but the important part is, every website has one. No matter how big or small.</p>
<p><strong>So why not help your visitors and guide them to complete those?</strong><br />
<span id="more-305"></span>You can achieve that and drastically improve the site&#8217;s performance by including a call to action. Thanks to it your visitors will know what is the next step you want them to take. They will not always follow it but at least there will be an option for them to choose.</p>
<p>A lack of it though can create a different situation altogether. You rely on the visitor to choose their next move then. And imagine that you have 20 different options in your navigation, what are the chances that your visitor will go for the one you would like him to?</p>
<p><strong>A call to action is not difficult to implement but here are few things you should think of when working on it:</strong></p>
<p><strong>1. What is your objective for the site? </strong><br />
Without knowing it it&#8217;s almost impossible to create a call to action. What objective do you want your users to complete on the site? Contact you? View your portfolio? Register for a promotion? Try a demo of your system? Try to imagine what would it be, it will form the main part of your call to action.<br />
<strong><br />
2. What are benefits for the visitor to follow your call to action</strong><br />
Before you create your call to action you need to make sure that there are some benefits for the user to follow it. Why would he do so otherwise?</p>
<p>A good idea is to place your call to action beside a list of benefits of using your company. Especially if it asks the visitor to get in touch with you.</p>
<p><strong>3. Construct it offering an alternative solution</strong><br />
Do not push the visitor in one direction only, offer him an alternative route. Instead of saying &#8220;call us now&#8221; make your call to action to state &#8220;call us now or browse through our work&#8221;. This way your visitor should not feel forced to do one thing only, rather offered two paths to choose from.</p>
<p>The main thing here is to mark graphically which path is more important to you.<br />
<a href="http://www.rememberthemilk.com"><img src="http://www.papertopixel.org/blog/wp-content/uploads/2009/07/rtm.jpg" alt="" /></a><br />
<em>Remember The Milk offers an alternative but main option is made prominent.</em></p>
<p><strong>4. Use active urgent language</strong><br />
A call to action should clearly tell users what you want them to do. It should include active words such as:</p>
<ul>
<li>Call</li>
<li>Try</li>
<li>Register</li>
<li>Sign up</li>
<li>Subscribe</li>
</ul>
<p>and so on. The idea is to encourage the user to take the action.</p>
<p>Long sentences might work well too, example:</p>
<p><a href="http://www.overcomefearofpublicspeakinghq.com">Overcome Fear of Public Speaking</a></p>
<p><a href="http://www.campaignmonitor.com"><img src="http://www.papertopixel.org/blog/wp-content/uploads/2009/07/cm.jpg" alt="" /></a></p>
<p><em>Campaign Monitor uses active language for both call to action and it&#8217;s alternative.</em></p>
<p><strong>5. Make it stand out</strong><br />
A call to action simply won&#8217;t work if it won&#8217;t stand out on a page. Make it prominent, make it big (well, not always but in most cases this works best). Use contrast to differentiate it from the rest of page elements. Use white space for the same purpose.</p>
<p><a href="http://www.wufoo.com"><img src="http://www.papertopixel.org/blog/wp-content/uploads/2009/07/wufoo.jpg" alt="wufoo" /></a></p>
<p><em>Wufoo uses strong color contrast to make call to action stand out.</em></p>
<p><strong>6. Do not restrict it to a home page alone</strong><br />
A common belief is that it should reside on home page only but in reality you should have it on every page. The simplest reason for that is that you do not know which page the user has landed on when they entered your site. He may have simply googled a specific term and landed on one of the inner pages of your site.</p>
<p><a href="http://www.basecamphq.com"><img src="http://www.papertopixel.org/blog/wp-content/uploads/2009/07/bc.jpg" alt="basecamp" /></a></p>
<p><em>Basecamp features this call to action at the bottom of every page</em></p>
<p><strong>7. Test, test, test </strong><br />
Last but not least, you should always test your call to action before launching it on your site. Not only test whether all links work but even most importantly test whether it&#8217;s message is clear, it&#8217;s position right and will your potential visitors understand and act on it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/why-you-need-a-call-to-action-on-a-website-and-few-tips-on-how-to-create-one/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>5 tips on how to design for a CMS and stay sane</title>
		<link>http://www.papertopixel.org/2009/5-tips-on-how-to-design-for-a-cms-and-stay-sane/</link>
		<comments>http://www.papertopixel.org/2009/5-tips-on-how-to-design-for-a-cms-and-stay-sane/#comments</comments>
		<pubDate>Tue, 30 Jun 2009 21:27:39 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[web usability]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/2009/5-tips-on-how-to-design-for-a-cms-and-stay-sane/</guid>
		<description><![CDATA[Do you like to be in control of your artwork? Of course you do.
That&#8217;s one of the characteristics of a designer, you are responsible almost with your life for the way projects turn out and you will do anything to make sure it&#8217;s perfect.
But what can you do with websites where you allow your client [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Do you like to be in control of your artwork? Of course you do.<br />
That&#8217;s one of the characteristics of a designer, you are responsible almost with your life for the way projects turn out and you will do anything to make sure it&#8217;s perfect.</strong></p>
<p>But what can you do with websites where you allow your client to manage or modify the content, grow the site and add whatever they please?<br />
<span id="more-275"></span><br />
How can you keep up the highest quality level with those projects? Or maintain a highest level of usability if you do not have much control over the content? The site is still designed by you and so is the basic usability but many content based issues may and most likely will arise.<br />
<strong><br />
The simplest thing is to start designing for a CMS by assuming the following:</strong></p>
<p>1. The content will most likely be different from what you have been told when the project commenced.</p>
<p>2. There will definitely be much more content than even the client anticipates.</p>
<p>3. And once the client realizes that they can do more with the cms they will.</p>
<p><strong>So what can you do to protect yourself from losing your mind?</strong><br />
<strong><br />
1. Allow the website and it&#8217;s content to expand. </strong><br />
Always make provision that there more pages will be added, same with content, images, videos and other site elements. Your navigation should accommodate this. Add dropdown menus or a way to create local navigation for website sections. Assume that there will be more of everything.<br />
Also do not design your pages or their elements that are editable by the cms to have fixed height. Always allow them to expand vertically.</p>
<p><strong>2. Always exaggerate when it comes to the content.</strong><br />
I always assume that there will be 3 times more content that I was told. In other words if a client tells you there will be only 3 paragraphs on a page, design as if there was meant to be 9 of them. And preview your designs this way.<br />
This is important to keep the styling and a branding consistent no matter how much content there is on the site. You should always design for larger content that&#8217;s going to be on the site.</p>
<p><strong>3. Do not give too much stylistic control to your client. </strong><br />
This generally relates to fonts and colors. Most clients want to be able to change them although from my experience the first thing they will do will be to change them to something not matching your style at all.<br />
Try retaining control over fonts, sizes and colors via your CSS stylesheet.</p>
<p><strong>4. Remember that your templates will be reused to create more pages.</strong><br />
Design them in a way that your client will have no difficulty creating additional pages from them. Also, do not create too many templates as it may be confusing for the client which one to choose for the site and ultimately may generate chaos in the sites layout.</p>
<p><strong>5. Try hardcoding certain elements into the site rather than giving your client access to them.</strong><br />
This mainly relates to thank you and error notes on email forms outputted from cms. Very often this is an overlooked element leaving the site without this strong usability tool.</p>
<p>In other words when you design for the cms you design for change and you should always keep that in mind while working on your artwork.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/5-tips-on-how-to-design-for-a-cms-and-stay-sane/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What to check before you launch a website #2: Content Managed sites</title>
		<link>http://www.papertopixel.org/2009/what-to-check-before-you-launch-a-website-2-content-managed-sites/</link>
		<comments>http://www.papertopixel.org/2009/what-to-check-before-you-launch-a-website-2-content-managed-sites/#comments</comments>
		<pubDate>Sun, 10 May 2009 08:01:26 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=268</guid>
		<description><![CDATA[Couple of days ago I wrote about few things to check before the site goes live. The post, as the title suggested was really intended for static sites. This time I&#8217;d like to mention few additional elements you should remember about before you publish a Content Managed site.
Before we do that let&#8217;s see what is [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Couple of days ago I wrote about <a href="http://www.papertopixel.org/2009/what-to-check-before-you-launch-a-website-1-static-sites/">few things to check before the site goes live</a>. The post, as the title suggested was really intended for static sites. This time I&#8217;d like to mention few additional elements you should remember about before you publish a Content Managed site.</strong></p>
<p><strong>Before we do that let&#8217;s see what is a difference between the two types is?</strong><br />
On a basic level, the difference is that with a static site you know what type of content will be published there. When it comes to Content Managed sites the content can be anything that a particular CMS you use can output.</p>
<p>And even if a client agrees to use only the type of content they discussed with you they most likely would not keep the promise. The rule of thumb with CMS systems is that the minute your client realizes they can do more with the System, they will.</p>
<p><span id="more-268"></span><strong>Therefore you should always think ahead and include at least some generic styles for all types of content the client can output on their site.</strong></p>
<p>In most cases that means making sure that you have styles for image gallery, blog etc.</p>
<p>Although there are certain elements wildly forgotten when it comes to CMS sites. Most of those items are ones that you can often output through rich text editor online and this is in fact the area your clients will be using the most.</p>
<p><strong>So in your text content make sure you have styles for:</strong></p>
<ol>
<li>bulleted lists</li>
<li>ordered lists</li>
<li>images in post</li>
<li> block-quote</li>
<li>all 6 headings</li>
<li>links in paragraph</li>
<li>definition list</li>
<li>forms</li>
<li>tables</li>
</ol>
<p><strong>Also, most systems these days allow to place youtube (or any other service) video within the content so make sure that you have at least margins separating the player from other text set up.</strong> In most cases the way the player look can be controlled on the site you are embedding it from but the position of it is your task.</p>
<p>You could of course go further than default styles and create various sets for different containers your client can put the content into. In most cases though having a one default style will suffice. This of course depends also largely on design.</p>
<p><strong>Last but not least, a 404 page. </strong>For Content Managed sites is crucial to have one. Most CMS system work in a way that changing a page name changes it&#8217;s URL as well. If the page has already been picked up by Google, after the name change the link will lead to nowhere. A 404 page will ensure your visitor that the site is still there and direct him how to at least get to a home page.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/what-to-check-before-you-launch-a-website-2-content-managed-sites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>7 really basic accessibility tips to remember</title>
		<link>http://www.papertopixel.org/2009/7-really-basic-accessibility-tips-to-remember/</link>
		<comments>http://www.papertopixel.org/2009/7-really-basic-accessibility-tips-to-remember/#comments</comments>
		<pubDate>Mon, 04 May 2009 07:34:12 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=255</guid>
		<description><![CDATA[Do you sometimes wonder who is using your site? Who is your average user, how does he interact with your site, how does he react on graphics and design solutions you used?

Probably yes, we like to do that, it is part of the design process to know how our site will be used
But do you [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Do you sometimes wonder who is using your site? Who is your average user, how does he interact with your site, how does he react on graphics and design solutions you used?<br />
</strong><br />
Probably yes, we like to do that, it is part of the design process to know how our site will be used</p>
<p>But do you sometimes wonder how a person with disabilities will use your site? Will a color blind person be able to still distill information from it? Will he finds a hyperlink somewhere in the text?</p>
<p><span id="more-255"></span>When developing a site we all sometimes overlook some basic methods that we can use to make our site more accessible for everyone. I am ashamed to admit that it happens to me to.</p>
<p>So for you and me I compiled a list of few really basic things to remember and check for to make sure your site is accessible on a basic level at least.</p>
<p><strong>1. Make sure your site works with all css switched off</strong><br />
Your visitors with cognitive disabilities may disable complex layouts to get a more linear presentation, users with color deficiencies or low vision may override your site colors or font sizes. So always make sure that all information on your site’s pages display well without any css styling.</p>
<p><strong>2. Construct your links to have a meaning</strong>, avoid &#8220;click here&#8221;, include a description of where the visitor will be taken if he clicks on a hyperlink i.e. &#8220;read more about our product&#8221;</p>
<p><strong>3. Separate your links</strong><br />
Don&#8217;t use only one white space between consecutive links, screen readers may interpret two or more non-separated links as one</p>
<p><strong>4. Provide text equivalent for non-text data.</strong><br />
Simply, include ALT tag to describe the image, use LONGDESC for longer descriptions. Also, you can simply describe non-text content in your sites copy.</p>
<p><strong>5. Try not using images for links.</strong><br />
Screen readers will not interpret them as a link. If you have to do so though, use ALT attribute to allow screen readers use it as a link.</p>
<p><strong>6. Design color elements in a way that they can be viewed and understand without color as well. </strong>Otherwise color blind visitors may have difficulties to see them.</p>
<p><strong>7. Make sure that your site works with JavaScript switched off. </strong>This is especially important if you use some fancy script for navigation. Make sure that your content can be accessed when the script is turned off as well.</p>
<p><strong>And last but not least, always validate your site to look for potential errors.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/7-really-basic-accessibility-tips-to-remember/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
