<?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>Blog Tutorials &#187; Design Features</title>
	<atom:link href="http://www.blog-tutorials.com/category/features/design-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blog-tutorials.com</link>
	<description>Helping you create a successful blog!</description>
	<lastBuildDate>Wed, 08 Sep 2010 13:22:13 +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>Is Your Blog W3C Compliant?</title>
		<link>http://www.blog-tutorials.com/design/design-2/is-your-blog-w3c-compliant/</link>
		<comments>http://www.blog-tutorials.com/design/design-2/is-your-blog-w3c-compliant/#comments</comments>
		<pubDate>Tue, 16 Oct 2007 10:11:30 +0000</pubDate>
		<dc:creator>Guru</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Design Features]]></category>

		<guid isPermaLink="false">http://www.blog-tutorials.com/design/design/is-your-blog-w3c-compliant/</guid>
		<description><![CDATA[Last night I checked my personal blog&#8217;s code hoping I can proudly display the W3C Validated Button. Since I use Blogger and do not really do anything to clean up the code (beyond adding Alt-tags to the images I embed) I wasn&#8217;t surprised at all to find that my blog contained lots of errors &#8211; [...]]]></description>
			<content:encoded><![CDATA[<p>Last night I checked my personal blog&#8217;s code hoping I can proudly display the <em>W3C Validated Button</em>. Since I use Blogger and do not really do anything to clean up the code (beyond adding Alt-tags to the images I embed) I wasn&#8217;t surprised at all to find that my blog contained lots of errors &#8211; 851 Errors to be exact. Of course it was still a bit disappointing but as I said, it wasn&#8217;t a big surprise. Since I do not employ any web designer after all and <a href="http://www.blogger.com/">Blogger</a> offers a really easy to use and free service than I can&#8217;t really complain much. However, for the bloggers out there that do employ the services of a web designer it would be a really good idea if you are getting your money&#8217;s worth.</p>
<p>If you find out that the code is not that flawless do not be too harsh on your web designer though. Go ahead and ask why there are errors. If there aren&#8217;t too many most probably the problem lies in your own posts and the &#8220;template&#8221; provided by the designer might even be flawless. However, if there are just too many errors then you can ask the designer to clean up the code, unless you weren&#8217;t able to stipulate in your contract that the code needs to be W3C compliant. In that case, you can chalk it up to experience and either pay an additional fee or choose to stay with the existing design as long as your blog looks decent enough when viewed using browsers other than Internet Explorer.</p>
<p><strong>Useful Stuff:</strong><br />
<a href="http://validator.w3.org/">Validate Your Code Here.</a><br />
Read about <a href="http://www.w3.org/">W3C (World Wide Web Consortium) Here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.blog-tutorials.com/design/design-2/is-your-blog-w3c-compliant/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Alt-Tags: For Spiders and the Visually Impaired</title>
		<link>http://www.blog-tutorials.com/design/images/alt-tags-for-spiders-and-the-visually-impaired/</link>
		<comments>http://www.blog-tutorials.com/design/images/alt-tags-for-spiders-and-the-visually-impaired/#comments</comments>
		<pubDate>Fri, 05 Oct 2007 12:17:25 +0000</pubDate>
		<dc:creator>Guru</dc:creator>
				<category><![CDATA[Design Features]]></category>
		<category><![CDATA[Images]]></category>
		<category><![CDATA[Marketing and Search Optimization]]></category>
		<category><![CDATA[SEO Features]]></category>

		<guid isPermaLink="false">http://www.blog-tutorials.com/design/images/alt-tags-for-spiders-and-the-visually-impaired/</guid>
		<description><![CDATA[Lots of people underestimate the importance of Alt-Tags. Even though SEO experts time and again stress the importance of Alt-Tags many still do not bother with it at all, or if they use it, do not consistently do so. To be honest, I belong to the inconsistent group.
Alt-tags ARE very important. SEO-wise the absence of [...]]]></description>
			<content:encoded><![CDATA[<p>Lots of people underestimate the importance of Alt-Tags. Even though SEO experts time and again stress the importance of Alt-Tags many still do not bother with it at all, or if they use it, do not consistently do so. To be honest, I belong to the inconsistent group.</p>
<p>Alt-tags ARE very important. <strong>SEO-wise the absence of alt-tags will ensure that your images and other embedded media will NOT be indexed by spiders since they will be unable to determine the actual content of each embedded element. </strong></p>
<p>Being a parent of a child with special needs though, I am very sensitive about discrimination towards people with disabilities. To my shame I have have to admit that I have always been focused on the SEO perks of Alt-Tags and neglected to give importance to what it meant for those that are visually impaired until I read about the <a href="http://ap.google.com/article/ALeqM5iT396LrL0Dn_VFtqatKHxASWGBuQD8S1V4R01">class-action suit against Target</a>. To be fair to <a href="http://www.target.com/">Target</a> though <a href="http://www.bizreport.com/2007/10/over_a_third_of_internet_inaccessible_to_blind_users.html">more than a third of websites are inaccessible to blind users</a>. Not that it makes it right but only that I do pity Target in a way since they have to bear the brunt of the negative consequences due to the neglect of webmasters all over the world. If I were them though I would fire my web designers/SEO consultants. They should have followed <a href="http://www.w3.org/TR/WCAG10/">W3C Guidelines</a>!</p>
<blockquote><p><em>&#8220;Provide a text equivalent for every non-text element (e.g., via &#8220;alt&#8221;, &#8220;longdesc&#8221;, or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.&#8221;</em></p></blockquote>
<p>This is a reminder to ALL OF US especially here at Blog-Tutorials. Let&#8217;s make sure our beloved blog is optimized and discriminates against no one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.blog-tutorials.com/design/images/alt-tags-for-spiders-and-the-visually-impaired/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Tweaking your blog&#8217;s HTML? Avoid these horrible tags!</title>
		<link>http://www.blog-tutorials.com/blog-tutorial/tweaking-your-blogs-html-avoid-these-horrible-tags/</link>
		<comments>http://www.blog-tutorials.com/blog-tutorial/tweaking-your-blogs-html-avoid-these-horrible-tags/#comments</comments>
		<pubDate>Mon, 16 Jul 2007 23:34:13 +0000</pubDate>
		<dc:creator>Ia Lucero</dc:creator>
				<category><![CDATA[Blog Tutorial]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Design Features]]></category>
		<category><![CDATA[Opinion]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.blog-tutorials.com/blog-tutorial/tweaking-your-blogs-html-avoid-these-horrible-tags/</guid>
		<description><![CDATA[If you&#8217;ve been blogging for sometime now, you would have tinkered with HTML several times of already. In fact I&#8217;ve shown how you can use several HTML tags to make your posts more readable.
The bad news is, HTML has a dark side: it has tags and attributes that are not very useful or meaningful (i.e., [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve been blogging for sometime now, you would have tinkered with HTML several times of already. In fact I&#8217;ve shown how you can use several HTML tags to <a href="http://www.blog-tutorials.com/blog-tutorial/make-your-blog-posts-readable/">make your posts more readable</a>.</p>
<p>The bad news is, <em>HTML has a dark side</em>: it has tags and attributes that are not very useful or meaningful (i.e., <strong>deprecated</strong>) but can still be used by the ignorant, especially since HTML is very easy to learn. But if it is <em>not learned correctly</em>, your blog might load more slowly or not work at all in other people&#8217;s browsers.</p>
<p><strong>Warning: Do NOT try these at home!</strong></p>
<p><span id="more-323"></span></p>
<h2>Tacky Tags</h2>
<p>Used by people who are trying hard to impress their visitors&#8212;but are clueless about what good web design is all about.</p>
<h3><code>&lt;marquee&gt;</code></h3>
<p>While it can have <a href="http://procurate.com/marquee1.htm">interesting uses</a>, people looking to spice things up should not turn to this tacky replica of a stock ticker. (Horror of horrors, <a href="http://tips-for-new-bloggers.blogspot.com/2007/06/scrolling-text-marquee-html-code.html">this blog is promoting its use</a>!)</p>
<h3><code>&lt;blink&gt;</code></h3>
<p>Again, completely tacky and irritating to look at. If you want to put animations on your website, learn Adobe Flash (or Microsoft Silverlight).</p>
<h2>Cosmetic Tags</h2>
<p>Used by people who don&#8217;t want to style their sites with CSS. These tags may have been irreplaceable a few years ago, but today, there is absolutely no need to use them.</p>
<h3><code>&lt;font&gt;</code></h3>
<p>If you want to change the font style of a paragraph, you can add use the <code>style</code> attribute in the enclosing HTML tag, e.g., <code>&lt;p&gt;</code>:</p>
<p><code>&lt;p style="font-family: Tahoma, Sans-serif; font-size: 18pt;"&gt;Enclosed Text&lt;/p&gt;</code></p>
<p>(But entering rules in a separate stylesheet is the best solution.)</p>
<h3><code>&lt;s&gt;</code> or <code>&lt;strike&gt;</code></h3>
<p>You can indicate deleted text by the more meaningful <code>&lt;del&gt;</code> tag. (Hint: <code>&lt;ins&gt;</code> is the complementary tag used to <em>insert</em> text.)</p>
<h3><code>&lt;center&gt;</code></h3>
<p>If you want to center a paragraph, you can add use the <code>style</code> attribute in the enclosing HTML tag, e.g., <code>&lt;p&gt;</code>:</p>
<p><code>&lt;p style="text-align: center;"&gt;Enclosed Text&lt;/p&gt;</code></p>
<p>(But entering rules in a separate stylesheet is the best solution.)</p>
<h2>The Madness Has Just Begun</h2>
<p>There are <a href="http://www.codehelp.co.uk/html/deprecated.html">many more deprecated HTML tags</a> to mention, but you probably haven&#8217;t encountered them (assuming you&#8217;ve only began to see HTML code lately). The sample code above will not always apply in other situations, but they give you an idea of how to add <em>inline</em> CSS into your HTML. (Recommended reading: <a href="http://w3schools.com/css/default.asp">W3Schools.com CSS page</a>)</p>
<p>While you think taking these extra steps (learning CSS, particularly) to eliminate use of these <em>evil HTML tags</em> is an inconvenience, it&#8217;s a very good investment.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.blog-tutorials.com/blog-tutorial/tweaking-your-blogs-html-avoid-these-horrible-tags/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>A few reminders on third-party Image Hosting</title>
		<link>http://www.blog-tutorials.com/design/images/a-few-reminders-on-third-party-image-hosting/</link>
		<comments>http://www.blog-tutorials.com/design/images/a-few-reminders-on-third-party-image-hosting/#comments</comments>
		<pubDate>Wed, 27 Jun 2007 06:52:43 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Blogging Tools]]></category>
		<category><![CDATA[Design Features]]></category>
		<category><![CDATA[Images]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.blog-tutorials.com/design/images/a-few-reminders-on-third-party-image-hosting/</guid>
		<description><![CDATA[If you have a blog that&#8217;s hosted in Wordpress.com, or Blogspot, or any other free* service, or if you have unlimited resources, that is, truckloads of money to pay for all that uncapped web space, you may be least likely concerned about the gigabytes that images can easily consume from what you have arranged with [...]]]></description>
			<content:encoded><![CDATA[<p>If you have a blog that&#8217;s hosted in Wordpress.com, or Blogspot, or any other free* service, or if you have unlimited resources, that is, truckloads of money to pay for all that uncapped web space, you may be least likely concerned about the gigabytes that images can easily consume from what you have arranged with your webhost of choice. The rest of us common men with an inkling of what saving both gigabytes of allocation and the bandwidth needed to pump out all those images may consider hosting these on a separate service, or outsourcing to a third-party <a href="http://www.webhostingsearch.com/image-hosting.php">image hosting service</a>.</p>
<p>There are all sorts of complications in this, which are more often than not clarified (if not in the most intimidating legalese) in these services&#8217; respective TOS&#8217;s, or Terms of Service. One thing to keep in mind, and something most bloggers may likely be concerned about is what is commonly worded as <em>&#8220;&#8230;perpetual, <strong>non-exclusive</strong>, transferrable, fully-paid, worldwide license to use, copy, publicly perform, publicly display, reformat, translate&#8230;&#8221; </em>**. The &#8220;non-exclusive&#8221; (or its equal) portion pre-empts possible user recoils on the ground that users who avail of these services relinquish ALL rights to material uploaded and thereafter shuttled to the consumers of the image content. Not much to worry about; it&#8217;s a lawyer thing to be six steps ahead and write off 99% of claims to privacy when, say, users suddenly find their beach body picture all over the web on a Flickr advertisement.</p>
<p>Also, keep in mind is how the service you choose to employ the phrase &#8220;legal use&#8221;. Case in point: both ImageShack and Yahoo! Flickr provides hotlinks (direct URLs to the images used in embedding t hem onto web pages where they are served), but their usage clauses are not as parallel. Flickr in each of the uploaded photos&#8217; pages &#8211; where you can choose sizes that range from thumbnail, to small, medium, and full size &#8211; that directly linking to the individual files is a breach of the services&#8217; Terms and Conditions, while ImageShack gets by with a simple reminder that using the thumbnail codes that include the words &#8220;Free image hosting by www.ImageShack.us&#8221; to allow them to show ads keep the basic services free. Multiply, while not exactly an image-only site but has served as one for a lot of bloggers taking advantage of the free* bandwidth, <em>does</em> allow hot-linking, and inserts a watermark with the Multiply logo on a corner of the image.</p>
<p>Remember, a little step you take to conform to the self-imposed rules on a web of free* services goes a long way in avoiding issues that may rise later on when you find yourself right at the center of buzz and traffic, which mostly translates to revenue, considering you&#8217;ve followed the other great tips and tricks from the writers of Blog Tutorials!</p>
<p>* &#8211; <em>free</em> may mean ad-supported<br />
** &#8211; taken from Facebook Terms of Service</p>
]]></content:encoded>
			<wfw:commentRss>http://www.blog-tutorials.com/design/images/a-few-reminders-on-third-party-image-hosting/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Lowdown on the technical aspects of design</title>
		<link>http://www.blog-tutorials.com/tips/the-lowdown-on-design/</link>
		<comments>http://www.blog-tutorials.com/tips/the-lowdown-on-design/#comments</comments>
		<pubDate>Tue, 22 May 2007 05:50:17 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Design Features]]></category>
		<category><![CDATA[Featured Articles]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.blog-tutorials.com/tips/the-lowdown-on-design/</guid>
		<description><![CDATA[Clearly, I&#8217;m asking for trouble here by laying down a list of what is regarded as good design.
Hopefully though, this does not turn out like O&#8217;Reilly&#8217;s Bloggers&#8217; Code of Conduct which he later took back:
Proper use of fonts &#8211; as a general rule, no more than three font families are to be used on a [...]]]></description>
			<content:encoded><![CDATA[<p>Clearly, I&#8217;m asking for trouble here by laying down a list of what is regarded as good design.<br />
Hopefully though, this does not turn out like O&#8217;Reilly&#8217;s Bloggers&#8217; Code of Conduct which he later took back:</p>
<p><em><strong>Proper use of fonts</strong></em> &#8211; as a general rule, no more than three font families are to be used on a single page. Too similar fonts make for a staid feel, while over-using fonts is gaudy. <em>(This one I remember from my elementary Journalism class)</em><br />
<em>Font families</em> &#8211; unlike in print media, the use of serifs <em>(Garamond, Times New Roman, Cambria)</em> and sans-serifs <em>(Arial, Tahoma, Calibri)</em> are reversed: serifs are generally used online for headers and titles, while sans-serifs are used for body text. The general assumption is that serifs when displayed onscreen without sub-pixel font rendering tend to strain the eyes. While OS X and Windows Vista already implement font families optimized for sub-pixel font rendering, this is still a small percentage of your audience.</p>
<p><em><strong>Writing special symbols</strong></em> &#8211; with the proliferation of adaptive WYSIWYG interface, it&#8217;s increasingly more difficult to resist writing in Microsoft Word and pasting everything over to your platform&#8217;s Visual Editor <em>(in my experience, Wordpress and Blogger are notorious for not filtering Microsoft-proprietary extensions to HTML when copy-pasting).</em> As such, the inevitable appearance of symbols such as é and € make the work of future-proofing your code more difficult than it should be.  To get on the good side of font substitution between operating systems and browsers, and future extensions to the current HTML/XHTML standards, consider using entity names versus entity numbers.</p>
<p><em><strong>Use of images</strong></em> &#8211; here&#8217;s where it gets dicey. Unless you&#8217;re running a design site, it is good practice to stick with muted background patterns that tile well &#8211; not wallpaper sized images that only add unnecessary loading times to your page. Then again, I have seen well-optimized images used as watermarks that still manifest good practice. Your gut feel would be your best bet.</p>
<p><em><strong>Formats of choice</strong></em> &#8211; JPEG is still de factor photos and PNG for outlined images. Generally, it is best to leave a file in its original format. You almost never have to perform format conversions as this decreases the fidelity of your images. This is especially true for PNG; unless specialized software is employed, converting a GIF does not give the vector-based advantage of PNG because the latter is dependent on distance between image elements <em>(lines, loops, fills)</em>, unlike GIF.</p>
<p>In the next installment…</p>
<p><em><strong>Color themes </strong></em>-<br />
<em><strong>Adapting to different screen resolutions</strong><strong> </strong></em>-<br />
<em><strong>Cross-browser compatibility</strong></em> -</p>
]]></content:encoded>
			<wfw:commentRss>http://www.blog-tutorials.com/tips/the-lowdown-on-design/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Maximizing Stock Photography</title>
		<link>http://www.blog-tutorials.com/design/images/maximizing-stock-photography/</link>
		<comments>http://www.blog-tutorials.com/design/images/maximizing-stock-photography/#comments</comments>
		<pubDate>Sat, 12 May 2007 15:29:04 +0000</pubDate>
		<dc:creator>Benj Espina</dc:creator>
				<category><![CDATA[Design Features]]></category>
		<category><![CDATA[Images]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.blog-tutorials.com/design/images/maximizing-stock-photography/</guid>
		<description><![CDATA[Stock photography is the general term for photographs that are readily found in repositories whether in the real world or over the internet ... there are literally millions of stock photos in the internet and there are a lot of sites that give them out for free. Those sites who charge for their service often compensate photographers and artists for use of their images.]]></description>
			<content:encoded><![CDATA[<p>Hi everyone, I&#8217;m Benj, one of your new writers for BlogTutorials. Even with the preponderance of technology to allow bloggers to take and modify their own photos, there are still individuals (*clears throat*) who are still  not well-versed in the subtle art of photography. It&#8217;s a good thing that now, people who weren&#8217;t born with a feel for the lens have alternatives as sources of embellishment for their blog posts.<span id="more-242"></span></p>
<p>Stock photography is the general term for photographs that are readily found in repositories whether in the real world or over the internet. Since the photos are already made, creative control is often lost since the modifications that a client can do is limited to his or her image editing skills. Fortunately, there are literally millions of stock photos in the internet and there are a lot of sites that give them out for free. Those sites who charge for their service often compensate photographers and artists for use of their images.</p>
<p>A considerable number of these stock photography sites have one thing in common &#8211; they use hideously large watermarks to label their images. The labels are so huge they obscure the elements of the photograph and worse, they take away a lot of the aesthetic value that the image could bring to your blog post and your site in general.   Almost all of the most relevant search results for &#8217;stock photography&#8217; would feature watermarks so every obsessive-compulsive blogger would be easily turned off from the get-go.</p>
<p>Luckily, there are still stock photography sites that feature images minus the unsightly humongous watermarks. <a href="http://www.everystockphoto.com/" target="_blank">Everystockphoto</a> collates free images from known hosting sites (Flickr, etc.). Each image comes with its own Creative Commons license that lets you know just how much liberty you could take with the image and how you can credit the owner of the image in your post/ site. Details like the original address of the image can also be derived from the particulars provided in the site. To be absolutely sure, you may ask the owner for his or her permission before using the stock image.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.blog-tutorials.com/design/images/maximizing-stock-photography/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
