<?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>Themble</title>
	<atom:link href="http://themble.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://themble.com</link>
	<description>Sometimes Simple is Better</description>
	<lastBuildDate>Mon, 16 Aug 2010 13:05:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Possibly the Perfectest Reset Stylesheet Evar</title>
		<link>http://themble.com/blog/perfect-reset-stylesheet/</link>
		<comments>http://themble.com/blog/perfect-reset-stylesheet/#comments</comments>
		<pubDate>Sat, 10 Jul 2010 01:55:29 +0000</pubDate>
		<dc:creator>eddiemachado</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Reset Stylesheet]]></category>

		<guid isPermaLink="false">http://themble.com/?p=401</guid>
		<description><![CDATA[In search of the best Reset Stylesheet? Why not take a look at mine? It's pretty friggin' sweet.]]></description>
			<content:encoded><![CDATA[<p></p><p>Yea, &#8220;perfectest&#8221;. It&#8217;s a word.  Anyway, I&#8217;ve been meticulously scouring the web for a perfect reset stylesheet. Something that will make the starting point for each project somewhat uniform. I&#8217;m pretty sure I&#8217;ve come pretty damn close and decided to post my findings here for your benefit. So take some time to check out what&#8217;s inside the file or skip down to the bottom and download it. Enjoy!</p>
<p>Right off the bat, you&#8217;ll notice alot of the common stuff you&#8217;ll find in almost every reset stylesheet:</p>
<pre>
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, font, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td { margin: 0;padding: 0;vertical-align: baseline;border: 0;outline: 0;background: transparent;}

ol, ul {list-style: none;}

blockquote, q {quotes: none;}

:focus {outline: 0;}

table {border-collapse: collapse;border-spacing: 0;}
</pre>
<p>I&#8217;ve also added a little gem (thanks to <a href="http://www.hugsformonsters.com/" title="Hugs for Monsters">@hugsformonsters</a> for the tip) to clean up Safari&#8217;s text rendering:</p>
<pre>
html {-webkit-font-smoothing: antialiased;}
</pre>
<p>As well as something to help clear floats (thanks to <a href="http://www.simplebits.com" title="Simplebits">@simplebits</a>).</p>
<pre>
.clear:after {content: ".";display: block;height: 0;clear: both;visibility: hidden;}
</pre>
<p>Underneath this, you&#8217;ll find a few bonus styles that are commonly used on almost every site. You can change them up to suit your needs, but they are really useful and it&#8217;s a no brainer putting these in your reset stylesheet since you&#8217;ll <strong>always</strong> have a need for them.</p>
<pre>
/* text alignment */
.text-left {text-align: left;}
.text-center {text-align: center;}
.text-right {text-align: right;}

/* text formatting */
.small-caps, abbr {font-variant: small-caps;letter-spacing: 1.7px;}
.uppercase {text-transform: uppercase;letter-spacing: 1px;}
.lowercase {text-transform: lowercase;}
.strike {text-decoration: line-through;}
.underline {text-decoration: underline;}
strong, .strong {font-weight: 700;}
em, .em {font-style: italic;}

/* alignment */
.left {float: left;}
.right {float: right;}

/* images, videos, and more */
img, object, embed {display: block;}

/* code and pre blocks */
code, pre, .code { white-space: pre-wrap;white-space: -moz-pre-wrap;white-space: -pre-wrap;white-space: -o-pre-wrap;word-wrap: break-word; }
</pre>
<p>So by now you should see what i&#8217;m starting to get at. There&#8217;s no need to duplicate these styles now in your main css file. You can just create a pretty nice string just using these default styles.</p>
<p>Underneath these you&#8217;ll find some h1&#8242;s-h5&#8242;s each followed with a class to make styling text alot easier.</p>
<pre>
/******************************************************************
H1, H2, H3, H4, H5 STYLES
******************************************************************/

h1 a, .h1 a, h2 a, .h2 a, h3 a, .h3 a, h4 a, .h4 a, h5 a, .h5 a { text-decoration: none; }

h1, .h1 { font-size: 3.6em; line-height: 1.33em; }

h2, .h2 { font-size: 2.4em; line-height: 1.5em; }

h3, .h3 { font-size: 1.8em; line-height: 1.66em; }

h4, .h4 { font-size: 1.4em; line-height: 1.7em; }

h5, .h5 { font-size: 1.1em; line-height: 2.09em; }
</pre>
<p>Again, you can change these to your liking, but with all these default settings, your page should be off to a great start.</p>
<p>So here&#8217;s the whole thing. Just copy and paste it or you can <a href="http://themble.com/downloads/perfect-reset.css" title="Perfectest Reset Stylesheet">download it here</a>.</p>
<p>If you&#8217;ve got any suggestions as to what else I should put in here or if you see something that I&#8217;m missing, feel free to drop me a line on <a href="http://twitter.com/eddiemachado" title="Eddie Machado Twitter">Twitter</a>. You can follow me <a href="http://twitter.com/eddiemachado" title="Eddie Machado Twitter">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://themble.com/blog/perfect-reset-stylesheet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML5 Video Made Easy</title>
		<link>http://themble.com/blog/html5-video-made-easy/</link>
		<comments>http://themble.com/blog/html5-video-made-easy/#comments</comments>
		<pubDate>Tue, 13 Apr 2010 23:39:46 +0000</pubDate>
		<dc:creator>eddiemachado</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[Video]]></category>

		<guid isPermaLink="false">http://www.themble.com/?p=268</guid>
		<description><![CDATA[The <abbr title="HyperText Markup Language">HTML</abbr><span class="five">5</span> Video Tag is going to make displaying video on your sites <strong>alot</strong> easier.  Once the details are figured out...]]></description>
			<content:encoded><![CDATA[<p></p><p>When the buzz about HTML5 started, the one thing I was most excited about was the video tag. It was going to make video easy to embed in any situation and it was going to have fallbacks just in case a device or browser (ahem IE) didn&#8217;t support it.  Perfect, I thought. Well, fast forward a few months and we&#8217;re still not quite there. Yes, it&#8217;s easy to use and works fairly well, but there&#8217;s one problem: Codecs. There&#8217;s a lack of unity when it comes to codecs so we have to encode our videos in a few formats. Luckily, you really <em>only</em> need to worry about one codec. I&#8217;ll explain why.</p>
<p><video controls width="570px" height="328px" poster="http://themble.com/wp-content/themes/themble/images/html5sample.png"><br />
		<source type="video/mp4" src="http://themble.com/wp-content/themes/themble/videos/sample-vid.mp4"><br />
		<source type='video/ogg; codecs="theora, vorbis"' src="http://themble.com/wp-content/themes/themble/videos/sample-vid.ogg"></p>
<p>		<!-- flash default --></p>
<p></video>	</p>
<h2>Explaining the Code:</h2>
<p>This is the <abbr title="HyperText Markup Language">HTML</abbr>5 Video Tag.  With this code, videos can play in the browser <em>without</em> the need to use Flash.  Since <abbr title="Internet Explorer">IE</abbr> doesn&#8217;t support <abbr title="HyperText Markup Language">HTML</abbr>5 yet, this example has a Flash fallback.  When you load this page in <abbr title="Internet Explorer">IE</abbr>, you&#8217;ll see the Flash player.  <strong>With this video tag, we can now display videos on the iPhone and iPad!</strong></p>
<p>Each browser has it&#8217;s own set of controls so the video <em>will not</em> have the same control panel in every browser.  It&#8217;s ok though, since they will all look pretty similar and will seem familiar to the user.</p>
<pre>
&lt;video width="640px" height="360px" poster="images/thumbs/sample-thumb.png" controls autobuffer&gt;
    &lt;!-- safari / chrome / ie9 --&gt;
    &lt;source type="video/mp4" src="files/sample-vid.mp4"&gt;

    &lt;!-- firefox / opera --&gt;
    &lt;source type="video/ogg" src="files/sample-vid.ogg"&gt;

    &lt;!-- flash default --&gt;

    &lt;!-- image default (if NOTHING is supported) --&gt;
    &lt;img src="images/no-video.gif" alt="Video is not supported" /&gt;
&lt;/video&gt;
	</pre>
<h3>Additional Arguments</h3>
<pre>
&lt;video width="640px" height="360px" controls&gt;
	</pre>
<p>Adding the <span>controls</span> argument adds controls to the video player.  Without this argument, <strong>no controls will show</strong>.  This is probably only useful for <em>autoplay videos</em>.</p>
<pre>
&lt;video width="640px" height="360px" poster="images/thumbs/sample-thumb.png" controls&gt;
	</pre>
<p>Adding the <span>poster=&#8221;&#8230;&#8221;</span> argument adds an image.  It acts differently in every browser and is still experimental.  In Firefox it acts as the <strong>video thumbnail</strong>.  In Safari &amp; Chrome it displays <em>behind</em> the actual video.  Hopefully this gets worked out before the final working version of <abbr title="HyperText Markup Language">HTML</abbr><span class="five">5</span>.</p>
<pre>
&lt;video width="640px" height="360px" poster="images/thumbs/sample-thumb.png" controls autoplay&gt;
	</pre>
<p>Adding the <span>autoplay</span> argument makes the video start playing on page load.</p>
<pre>
&lt;video width="640px" height="360px" poster="images/thumbs/sample-thumb.png" controls autobuffer&gt;
	</pre>
<p>Adding the <span>autobuffer</span> makes the video load as soon as the page loads.  You obviously don&#8217;t want to add this on alot of the videos since it will pull <em>all</em> the videos with this attribute.</p>
<h2>How to Simplify It</h2>
<p>WHen you think about it, you really only need to make sure people can see your videos on iPhones and iPads. Any other decide <em>should</em> allow your flash video player to be viewable. So, with that logic, all you have to do is encode your video using the .mp4 codec, drop it in the video tag, and use the flash fallback for everything else. This negates the step of having to encode it for Firefox. Simple.</p>
]]></content:encoded>
			<wfw:commentRss>http://themble.com/blog/html5-video-made-easy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Site Speed isn&#8217;t a Quick Fix</title>
		<link>http://themble.com/blog/site-speed-isnt-a-quick-fix/</link>
		<comments>http://themble.com/blog/site-speed-isnt-a-quick-fix/#comments</comments>
		<pubDate>Mon, 12 Apr 2010 20:20:37 +0000</pubDate>
		<dc:creator>eddiemachado</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[Loading TIme]]></category>
		<category><![CDATA[Site Speed]]></category>
		<category><![CDATA[YSlow]]></category>

		<guid isPermaLink="false">http://www.themble.com/?p=262</guid>
		<description><![CDATA[Why you should read up on proper syntax and optimizing databases instead of looking for that "quick fix" plugin or tutorial.]]></description>
			<content:encoded><![CDATA[<p></p><p>The recent announcement that Google has added site speed as a ranking factor has people running to find quick-fix solutions.  Most people will drop a plugin or two into their WordPress install or follow a simple tutorial they found doing a quick search for &#8220;improving site speed&#8221; and assume that will get the job done.  Yes, a simple way to increase your site-speed (especially with WordPress) is to use a caching plugin.  What most people don&#8217;t think about is, as time goes on and your content expands and grows, it get&#8217;s harder and harder to maintain that initial speed burst these plugins will give you.</p>
<h3>It&#8217;s not a race, it&#8217;s a marathon.</h3>
<p>So how do you plan for content you haven&#8217;t even thought about yet?  Well, you can&#8217;t.  What you can do is lay a solid foundation so that when you do bring out the new stuff, it won&#8217;t cause a hiccup. It&#8217;s actually alot simpler to do this than people think and it all starts with how your site is coded.</p>
<h3>Valid Code runs faster.  It&#8217;s Science.</h3>
<p>Your web browser is not a human.  It can&#8217;t guess what you meant when you wrote &lt;p.&gt; instead of &lt;p&gt;.  It can sometimes figure things out on it&#8217;s own and display things the right way, but you&#8217;re making it think.  <strong>Web Browsers don&#8217;t like to think, they just want to do.</strong> Everytime a wrong or misplaced piece of code is parsed it takes just a little longer for that page to load. Sloppily written code will slow your site down. One or two incorrect lines may not mean much, In fact I doubt you&#8217;ll even notice it. The real harm comes when you get <em>accustomed</em> to writing messy and invalid code. One or two unclosed &lt;img&gt; tags won&#8217;t do much, but imagine what a couple hundred of them will do. If you learn to do it right from the very start, you won&#8217;t have to ever worry about it again.</p>
<p class="outgoing">Validate your code with <a href="http://validator.w3.org/" title="W3C Markup Validator" rel="nofollow">W3C Markup Validator</a> or <a href="http://validator.nu" title="Validator.nu" rel="nofollow">Validator.nu</a>.</p>
<h3>An Extra Step will do your Images Good.</h3>
<p>I love sites with tons of images.  When done properly, it really makes the whole experience more interactive. When overdone though, it can bring your loading time to painful crawl. So what if you have a really image heavy site?  How do you keep it from doing that unattractive 1980&#8242;s printer-like loading of your large images? Shrink &#8216;em ya dummy!</p>
<p>There are a few tools that make compressing images easier. Yes, they add an extra step to your process, but they can save seconds from your load time.  I&#8217;ve cut as much as 80% of the file size of an image just by compressing it. Best part? You won&#8217;t even be able to tell a degradation in quality. That&#8217;s a win-win if you ask me.</p>
<p class="outgoing">Download and compress your images with <a href="http://imageoptim.pornel.net/" title="ImageOptim" rel="nofollow">ImageOptim (OS X only)</a> or use the <a href="http://wordpress.org/extend/plugins/wp-smushit/" title="Smush It!" rel="nofollow">Smush It Plugin for WordPress</a>.</p>
<h3>Quit putting your database to work!</h3>
<p>Everytime you add a chore to your database&#8217;s list of things to display, it&#8217;s going to take longer for it to get the job done.  Be good to your database and it will be good to you. Any easy way to lighten it&#8217;s workload is to make it stop doing the mundane stuff no one likes doing anyway.</p>
<h3>A happier WordPress Database in 2 simple steps</h3>
<ol>
<li>Open your header file and replace all the &lt;?php bloginfo(&#8216;&#8230;&#8217;); ?&gt; with your site&#8217;s actual information.<br /><em>For example, change &#8220;&lt;?php bloginfo(&#8216;name&#8217;); ?&gt;&#8221; to &#8220;My Site Name&#8221;. Do the same thing in the footer and any other area where the content isn&#8217;t dynamic.</em></li>
<li>Hardcode every link in your navigation (if you can).  Do the same think for your footer links.</li>
</ol>
<p>These may seem like common sense to some people, but alot of people forget that every single one of those &lt;?php bloginfo(&#8216;&#8230;&#8217;); ?&gt; queries is another chore the database has to perform. You&#8217;re probably not going to be using this theme on another site so there&#8217;s really no reason to leave those in. Just ensure, that you&#8217;re directories won&#8217;t change!</p>
<h3>I learned something today&#8230;</h3>
<p>You can see how a few small things can really help clean up your code and make your site smoother.  As time goes on, your files can get cluttered and messy. If you start doing it the right way now, when the content starts rolling in you&#8217;ll be in a much better position. There will be less broken elements, misplaced tags, and your code and database will perform better.</p>
]]></content:encoded>
			<wfw:commentRss>http://themble.com/blog/site-speed-isnt-a-quick-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome to Themble</title>
		<link>http://themble.com/blog/welcome-to-themble/</link>
		<comments>http://themble.com/blog/welcome-to-themble/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 06:44:29 +0000</pubDate>
		<dc:creator>eddiemachado</dc:creator>
				<category><![CDATA[Article]]></category>
		<category><![CDATA[Hello World!]]></category>
		<category><![CDATA[Site News]]></category>
		<category><![CDATA[Updates]]></category>

		<guid isPermaLink="false">http://www.themble.com/?p=60</guid>
		<description><![CDATA[It's my first post. Welcome to the party.]]></description>
			<content:encoded><![CDATA[<p></p><p>In my experience working with WordPress and a few other blogging platforms, I&#8217;ve found it&#8217;s tough to find really easy to use and content friendly themes.  Yea, they may look good with the temporary demo content but it&#8217;s <em>supposed</em> to look that way.  The fact is when you plug-in your own content, it bites.  Some themes just aren&#8217;t flexible and tough to customize.  That&#8217;s where Themble comes in.</p>
<p>Themble is designed to help you make your site <em>yours</em>.  It may sound like a simple idea, but think about it.  When people are looking for an authoritative site, they have to weigh a few factors in their head as to which site they want to believe:</p>
<ul>
<li><strong>Search Engine Ranking</strong><br />
<em>Let&#8217;s face it, these days, people aren&#8217;t looking on Page 2 of their Search Results.  If they can&#8217;t find the information they&#8217;re looking for on the first page, they try their search again.</em></li>
<li><strong>General Site Design</strong><br />
<em>If the content doesn&#8217;t look clean or the page is littered with messy advertising blocks and un-aligned images, most readers discredit it&#8217;s content instantly.  Why would an &#8220;authoritative site&#8221; have a messy and lazily designed website?  It wouldn&#8217;t.</em></li>
<li><strong>Easy to Understand Navigation</strong><br />
<em>When you reach a site for the first time, it&#8217;s rare you land on it&#8217;s home page.  You most likely land on an article with the content you were looking for.  If a reader can&#8217;t even understand where on their site they are, how do you expect them to come back?  If you entered a store and couldn&#8217;t find which isle the item you were looking for was in, would you return to that store?</em></li>
</ul>
<p>Obviously there&#8217;s <strong>much</strong> more to it than those basic items, but it&#8217;s a good start.  On this site, we&#8217;re going to strive to make each site unique in it&#8217;s own right.</p>
<p>This is why choosing the right theme is <strong>crucial</strong> to your site&#8217;s success.  Downloading and using a free theme is perfectly fine, if you want your site to be <em>good enough</em>, but chances are good that there are several sites out there that are going to have that <strong>same exact theme</strong> on their site.  That doesn&#8217;t really make you look like an authoritative source, it just <em>makes you look lazy</em>.</p>
]]></content:encoded>
			<wfw:commentRss>http://themble.com/blog/welcome-to-themble/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
