<?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>csslearn.com &#187; web page structure</title>
	<atom:link href="http://csslearn.com/tag/web-page-structure/feed" rel="self" type="application/rss+xml" />
	<link>http://csslearn.com</link>
	<description>learn style with style</description>
	<lastBuildDate>Mon, 01 Mar 2010 02:17:37 +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>Basic web page structure and layout</title>
		<link>http://csslearn.com/basic-web-page-structure-and-layout</link>
		<comments>http://csslearn.com/basic-web-page-structure-and-layout#comments</comments>
		<pubDate>Thu, 26 Nov 2009 12:04:01 +0000</pubDate>
		<dc:creator>kunal</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[web page structure]]></category>

		<guid isPermaLink="false">http://csslearn.com/?p=60</guid>
		<description><![CDATA[Once you’ve sorted out the site map, avoid firing up your graphics package. It’s a good idea to sketch out page layout ideas on paper before working on your PC or Mac. Not only is this quicker than using graphics software, but it also allows you to compare many ideas side by side. At this [...]


Related posts:<ol><li><a href='http://csslearn.com/information-architecture-and-site-maps' rel='bookmark' title='Permanent Link: Information architecture and site maps'>Information architecture and site maps</a> <small>Before you begin designing a website, you need to collate...</small></li>
</ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p>Once you’ve sorted out the site map, avoid firing up your graphics package. It’s a good idea to sketch out page layout ideas on paper before working on your PC or Mac. Not only is this quicker than using graphics software, but it also allows you to compare many ideas side by side. At this stage, you shouldn’t be too precious about the design—work quickly<br />
and try to get down as many ideas as possible. From there, you can then refine your ideas, combine the most successful elements of each, and then begin working on the computer.</p>
<p>Although the Web has no hard-and-fast conventions, themes run throughout successful websites, many of which are evident in the following image of a version of my Snub Communications homepage.</p>
<p>A website’s navigation should be immediately accessible—you should never have to scroll to get to it. It’s also a good idea to have a masthead area that displays the organization’s corporate brand (or, if it’s a personal site, whatever logo/identity you wish to be remembered by, even if it’s only a URL). The homepage should include an introduction of some sort that briefly explains what the site is about, and it should have some pull-ins to other areas of the site. These pull-ins could be in the form of news items that link to recent product launches, completed projects, and so on.<br />
Most websites require a method for people to contact the site owner, and at least one clear link to a contact page is essential.</p>
<p>Avoid constantly changing the design throughout the site. In print, this sometimes works well and provides variation within a book or magazine. Online, people expect certain things to be in certain places. Constantly changing the position of your navigation, the links themselves, and even the general design and color scheme often creates the impression of an unprofessional site and makes it harder to use.</p>
<p>Ultimately, however your site ends up, and whatever your design, you need to ensure your creation is as usable as possible. A good checklist—even if the points may seem entirely obvious—is as follows:</p>
<ol>
<li>Is the site easy to navigate?</li>
<li>Is it easy for users to locate content on each page?</li>
<li>Is it easy for users to find what they need on the site?</li>
<li>Are download times kept to a minimum?</li>
<li>Is the site suitable and relevant for its target audience?</li>
<li>Does the site use familiar conventions?</li>
</ol>
<p>If you can answer yes to all these things, then you should be on the right track!</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fcsslearn.com%2Fbasic-web-page-structure-and-layout&amp;linkname=Basic%20web%20page%20structure%20and%20layout"><img src="http://csslearn.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>

<p>Related posts:<ol><li><a href='http://csslearn.com/information-architecture-and-site-maps' rel='bookmark' title='Permanent Link: Information architecture and site maps'>Information architecture and site maps</a> <small>Before you begin designing a website, you need to collate...</small></li>
</ol></p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://csslearn.com/basic-web-page-structure-and-layout/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
