<?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"
	>

<channel>
	<title>&#124; The Magnum Group &#124; Web Design Content &#124; &#187; Web Site Reviews</title>
	<atom:link href="http://web-design.themagnumgroup.net/content/category/web-site-reviews/feed" rel="self" type="application/rss+xml" />
	<link>http://web-design.themagnumgroup.net/content</link>
	<description>Articles on Web Design</description>
	<pubDate>Wed, 04 Jul 2007 12:15:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<language>en</language>
			<item>
		<title>XHTML and CSS from Photoshop</title>
		<link>http://web-design.themagnumgroup.net/content/xhtml-and-css-from-photoshop-2.htm</link>
		<comments>http://web-design.themagnumgroup.net/content/xhtml-and-css-from-photoshop-2.htm#comments</comments>
		<pubDate>Mon, 19 Feb 2007 12:47:00 +0000</pubDate>
		<dc:creator>Lucky Balaraman</dc:creator>
		
		<category><![CDATA[Web Site Reviews]]></category>

		<guid isPermaLink="false">http://web-design.themagnumgroup.net/content/xhtml-and-css-from-photoshop-2.htm</guid>
		<description><![CDATA[By R Kamalathasan
Edited by Lucky Balaraman
You have a magic lamp in your hands, you rub it, and a genie emanates from the spout.
You to the Genie: I&#8217;m an experienced Photoshop user&#8230; my wish is that I should be able to program a web page in XHTML and CSS without being adept in these languages and [...]]]></description>
			<content:encoded><![CDATA[<p><small>By <b>R Kamalathasan</b><br />
Edited by Lucky Balaraman</small></p>
<p><b><img style="margin: 0pt 10px 0px 0px; float: left;" alt="Photoshop to XHTML and CSS" title="SiteGrinder converts PSD files to XHTML and CSS" src="http://web-design.themagnumgroup.net/content/wp-content/uploads/2007/02/photoshop-to-xhtml.gif" /><i>You have a magic lamp in your hands, </i></b><i>you rub it, and a genie emanates from the spout.</i></p>
<p><b>You to the Genie</b>: I&#8217;m an experienced Photoshop user&#8230; my wish is that I should be able to program a web page in XHTML and CSS without being adept in these languages and without outsourcing the task. Can you deliver, Genie?<b><br />
</b>
<p class="western" style="margin-bottom: 0in;"><b>Genie to You</b>: Your wish is granted, oh Mighty User!</p>
<p class="western" style="margin-bottom: 0in;" align="center">***
</p>
<p class="western" style="margin-bottom: 0in;"><b>What the Genie was talking about is</b> <a href="http://www.medialab.com/sitegrinder/"><b>SiteGrinder</b></a>,&nbsp; a plugin for Photoshop that creates valid XHTML code and CSS code from a web page you design in Photoshop. Here&#8217;s an overview of the program:
</p>
<p class="western" style="margin-bottom: 0in;"><b>Firstly, using Photoshop alone</b> to create a web page will be as tedious as walking 200 kilometers without food, water or shoes. It involves slicing the image, exporting it to HTML and creating the other pages using an alternate web authoring program.
</p>
<p class="western" style="margin-bottom: 0in;"><b>Added to that,</b> if you need to change the design of the page later, it will be as tedious as catching a fish, throwing it back into the water and trying to catch it again. You would also need expertise in HTML and CSS to work with the fish. But what if you donâ€™t know HTML or CSS?? Are you doomed to a fishless existence?</p>
<p class="western" style="margin-bottom: 0in;"><b>Absolutely not! </b>With SiteGrinder, you donâ€™t need to be a PhD in HTML and CSS, you donâ€™t have to slice your images up and you donâ€™t need to create code for rollovers or popups. You merely have to perform a few simple steps in Photoshop to make your page SiteGrinder-ready.
</p>
<p class="western" style="margin-bottom: 0in;">
<p class="western" style="margin-bottom: 0in;"><b>To prepare a Photoshop web page for SiteGrinder,</b> all you have to do is assign an independent layer to each element in the document. You should append a suffix (a &#8220;hint&#8221;) preceded by a hyphen to the layer name to describe the nature of the element to SiteGrinder.
</p>
<p class="western" style="margin-bottom: 0in;"><b>For example,</b> if a text layer in Photoshop contains the text &#8220;About Us&#8221;, and the name of the layer is â€˜About Us - button&#8217;, SiteGrinder will understand that the text â€˜About Usâ€™ is a button link and convert it to XHTML accordingly.</p>
<p><b>In this way,</b> you can create all the pages of your web site in Photoshop, and transform them into an integrated XHTML and CSS web site with a single click. Is that a miracle or what?</p>
<p><b>SiteGrinder comes with abundant help files</b> including detailed video tutorials. Everything is explained, especially the 35 hints (which comprise a feature unique to SiteGrinder and not commonly known).</p>
<p class="western" style="margin-bottom: 0in;"><b>CONCLUSION:</b></p>
<p class="western" style="margin-bottom: 0in;"><b>I have exercised the basic commands of SiteGrinder </b>(hence my terming of this article an &#8220;overview&#8221;) and have not found any drawbacks so far. I am convinced beyond a doubt that this tool will definitely save a web developer an incredible amount of time.</p>
<p class="western" style="margin-bottom: 0in;"><b>Itâ€™s certainly worth giving SiteGrinder a try </b>&#8212; explore the capabilities yourself: in all probability you&#8217;ll be delighted!</p>
<p class="western" style="margin-bottom: 0in;"><b>You can download a trial version</b> from their site <a href="http://www.medialab.com/sitegrinder/"><b>here</b></a>. (not an affiliate link).</p>
<p class="western" style="margin-bottom: 0in;"><b>You can download a trial version of Photoshop</b> <b><a href="http://www.adobe.com/products/photoshop/">here</a></b> (not an affiliate link).</p>
<p class="western" style="margin-bottom: 0in;"><b>Good luck with SiteGrinder</b>, and come back with comments on your experience!
</p>
<p>Technorati Tags: <a class="performancingtags" href="http://technorati.com/tag/photoshop" rel="tag">photoshop</a>, <a class="performancingtags" href="http://technorati.com/tag/css" rel="tag">css</a>, <a class="performancingtags" href="http://technorati.com/tag/xhtml" rel="tag">xhtml</a>, <a class="performancingtags" href="http://technorati.com/tag/web+design" rel="tag">web+design</a></p>
]]></content:encoded>
			<wfw:commentRss>http://web-design.themagnumgroup.net/content/xhtml-and-css-from-photoshop-2.htm/feed</wfw:commentRss>
		</item>
		<item>
		<title>Web Site Reviews: Gmail Home Page</title>
		<link>http://web-design.themagnumgroup.net/content/web-site-reviews-gmail-home-page.htm</link>
		<comments>http://web-design.themagnumgroup.net/content/web-site-reviews-gmail-home-page.htm#comments</comments>
		<pubDate>Wed, 27 Dec 2006 14:16:41 +0000</pubDate>
		<dc:creator>Lucky Balaraman</dc:creator>
		
		<category><![CDATA[CSS]]></category>

		<category><![CDATA[SEO]]></category>

		<category><![CDATA[Usability]]></category>

		<category><![CDATA[Web Site Reviews]]></category>

		<guid isPermaLink="false">http://web-design.themagnumgroup.net/content/web-site-reviews-gmail-home-page.htm</guid>
		<description><![CDATA[Everybody knows and most of us love Gmail and are intimately familiar with its index page, shown at left.
Many of the web designers amongst us would also love to know what the HTML code under the page is like, so we have stripped it naked, looked at it and had some private thoughts about itâ€¦ [...]]]></description>
			<content:encoded><![CDATA[<p><img style="margin: 0px 20px 20px 10px; float: left; width: 300px; height: 204px;" alt="Thumbnail of Gmail Splash Page" title="Thumbnail of Gmail Splash Page" src="http://web-design.themagnumgroup.net/content/images/gmail-page-image.gif" />Everybody knows and most of us love Gmail and are intimately familiar with its index page, shown at left.</p>
<p>Many of the web designers amongst us would also love to know what the HTML code under the page is like, so we have stripped it naked, looked at it and had some private thoughts about itâ€¦ we share them with you below.</p>
<p>It is our hope that you will spend a moment or two to express any significant thoughts you have on the article with a comment. Where beneficial to visitors, we will respond to comments.</p>
<p>Before we get down and dirty, we must tell you that we have <a title="Analysis of Google Groups page" href="http://themagnumgroup.net/Blog/42.htm">analyzed the Google Groups page earlier in our parent site</a>, so we already have a fledgling idea about Googleâ€™s page code appearance. With that background, our tour of the <a title="Gmail splash page source code" href="http://web-design.themagnumgroup.net/content/wp-content/uploads/2006/12/welcome-to-gmail.txt">source code of Gmailâ€™s index page</a> now begins.</p>
<p>We start off with the styles. In contrast to the Google Groupsâ€™ style sheet, the main Gmail style sheet is well organized with no clumsy patches of commented-out code. It is embedded instead of external, which is alright considering the fact that the rest of the web site is in JavaScript. It does not contain styles for any of the HTML tags, and lists only class styles with their properties.These styles do not appear to be in any particular order.</p>
<p><span class="highlight"><b>Comment:</b> It would be preferable for the styles to be in order of appearance or alphabetical order.</span></p>
<p>The page uses a simple table-based design and the code is neatly formatted. At one point where a table is closed and another opened, it is pleasant to see a comment explaining why this was done (the reason pertained to a peculiarity of Internet Explorer).</p>
<p>But alas, there is a bit of clumsy CSS in the middle of the HTML code. We note with suspicion two style sheets placed in the section with nothing in between.</p>
<p><span class="highlight"><b>Comment:</b> Placing a style sheet in the body section is not customary and perhaps even weird. That said, there is no reason to have the two contiguous style sheets. All this has the smell of patchwork repair.</span></p>
<p>We are surprised that Google, with its mountain of cash and army of programmers, has not taken the trouble to make its behind-the-scenes workings neat. This is not the case with other large Internet companies like Yahoo, whose code is better by a degree of magnitude. (Check back after a few days for our analysis of a certain Yahoo page.)</p>
<h3><strong> Surprise Bonus: An Analysis of the Displayed Page</strong></h3>
<h4>The Layout:</h4>
<p>The displayed page is very good from the usability angle.</p>
<p>It is not â€˜busyâ€™, meaning that there is no clutter and no multitude of links to confuse and consternate the visitor (for instance, there are only six links above the fold).</p>
<p>There is an invitation to try the Gmail mobile phone interface: it contains a list of benefits and a call to action, which is good, except that the order of these two features is flawed.</p>
<p><span class="highlight"><b>Comment:</b> We think the benefits should have come before the call to action and not after!</span></p>
<p>The page has been optimized for 1024 pixels width, which conforms to the latest design recommendations.</p>
<h4>The Pageâ€™s SEO:</h4>
<p>The page has a humongous 26,500 backlinks (according to Yahoo Site Explorer), many from government sites like the New York Public Library and authority sites like Wikipedia.com.</p>
<p>There are links to a Privacy page and a â€˜Terms of Useâ€™ page.</p>
<p>The page contains many excellent secondary keywords such as â€˜accountâ€™, â€˜attachmentâ€™,â€™ pdfâ€™, â€˜photosâ€™, â€˜megabytesâ€™ and â€™storageâ€™.</p>
<p><span class="highlight"><b>Comment:</b> For the above reasons, the page is nicely SEOed.</span></p>
<p>This concludes our analysis of the www.gmail.com page. It is important that you you add your opinions on this analysis through our comment form; we look forward to receiving and responding to them.</p>
]]></content:encoded>
			<wfw:commentRss>http://web-design.themagnumgroup.net/content/web-site-reviews-gmail-home-page.htm/feed</wfw:commentRss>
		</item>
	</channel>
</rss>
