<?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>26AM Design Studio (Creative) &#187; Design Thoughts</title>
	<atom:link href="http://www.26am.com/blog/category/design-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.26am.com</link>
	<description>Web Development, Graphic Design Blog</description>
	<lastBuildDate>Fri, 29 Jan 2010 10:11:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What&#8217;s coming up on the 26AM blog?</title>
		<link>http://www.26am.com/blog/2010/01/29/whats-coming-up-on-the-26am-blog/</link>
		<comments>http://www.26am.com/blog/2010/01/29/whats-coming-up-on-the-26am-blog/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 10:07:00 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Design Thoughts]]></category>
		<category><![CDATA[Just for Fun]]></category>
		<category><![CDATA[The Hum of Life]]></category>
		<category><![CDATA[CES]]></category>
		<category><![CDATA[Haiti]]></category>
		<category><![CDATA[Non Profit]]></category>
		<category><![CDATA[Tradeshow]]></category>

		<guid isPermaLink="false">http://www.26am.com/blog/2010/01/29/whats-coming-up-on-the-26am-blog/</guid>
		<description><![CDATA[Josh and I (David) make up the 26AM team. However we are constantly bringing in other friends in the industry to pick up the slack when work is overwhelmingly busy as it is now. Two big things have happened for us recently. The first is we went to CES in Vegas! The second is we&#8217;ve [...]]]></description>
			<content:encoded><![CDATA[<p>Josh and I (David) make up the 26AM team. However we are constantly bringing in other friends in the industry to pick up the slack when work is overwhelmingly busy as it is now. Two big things have happened for us recently. The first is we went to CES in Vegas! The second is we&#8217;ve noticed a sharp increase in our Non-Profit work. This ranges from projects related to Haiti, Christian Organizations, Government Funded Agencies and so on. We are going to begin sharing those experiences and perspectives on it all with you. (Well isn&#8217;t that just dandy?)<span id="more-218"></span></p>
<p>Two weeks ago when I was in Las Vegas attending CES (The Consumer Electronics Show) with a good friend of mine from Evident Productions, we came up with idea for a blog series. So over the next month or two I will be blogging about my experiences at the show from a little point of view than many blogs you may find that have talked about CES. </p>
<p>I will be doing this series as a multi-part series that focuses on design, quality and production side of the entire trade show experience rather than focusing on the products that were presented at the show. </p>
<p>That&#8217;s about it for now! Hope you&#8217;re having a great day where you are!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.26am.com/blog/2010/01/29/whats-coming-up-on-the-26am-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Printer friendly web pages with &#8220;Print.css&#8221;</title>
		<link>http://www.26am.com/blog/2010/01/27/printer-friendly-web-pages-with-print-css/</link>
		<comments>http://www.26am.com/blog/2010/01/27/printer-friendly-web-pages-with-print-css/#comments</comments>
		<pubDate>Wed, 27 Jan 2010 18:01:32 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Design Thoughts]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Fonts]]></category>
		<category><![CDATA[Print]]></category>

		<guid isPermaLink="false">http://www.26am.com/?p=202</guid>
		<description><![CDATA[When most people think web pages they think &#8220;on screen.&#8221; I&#8217;ll admit, I&#8217;m the exact same way. I rarely think of taking a web page off screen and onto paper. On a recent project 26AM completed for a California State Government agency, we learned that portability not only to mobile devices but to paper is [...]]]></description>
			<content:encoded><![CDATA[<p>When most people think web pages they think &#8220;on screen.&#8221; I&#8217;ll admit, I&#8217;m the exact same way. I rarely think of taking a web page off screen and onto paper. On a recent project 26AM completed for a California State Government agency, we learned that portability not only to mobile devices but to paper is an important criteria.<span id="more-202"></span></p>
<p>It&#8217;s been a long time since I printed a web page (partially because I&#8217;m cheap and don&#8217;t like changing ink jet cartridges). However, printing a page doesn&#8217;t have to be a pain if the designer took a little extra time and made a &#8220;print.css&#8221; stylesheet. Print.css when applied correctly can make a web page easy to read and ink efficient.</p>
<p>Let&#8217;s take for instance the 26AM blog which you&#8217;re reading right now. We&#8217;ve created a print.css file that does the following:</p>
<ul>
<li>Changes the background to white</li>
<li>Uses Arial, Helvetica, Sans-Serif fonts</li>
<li>Removes all menus, the search bar, sidebar, header images</li>
<li>Adds print friendly titles and headers</li>
<li>Adds copyright information and the date/time stamp.</li>
</ul>
<p>The first step is instructing the browser to use <a href="http://www.26am.com/wp-content/themes/26AM/print.css">Print.css</a> when a person chooses to print the document. We added the following line to our HEAD tag.</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">&lt;link rel=&quot;stylesheet&quot; href=&quot;http://www.26am.com/wp-content/themes/26AM/print.css&quot; type=&quot;text/css&quot; media=&quot;print&quot; /&gt;</pre></div></div>

<p>Of course for your purposes, you&#8217;ll want to set the HREF to your newly created print.css file. The second step is filling in the <a href="http://www.26am.com/wp-content/themes/26AM/print.css">Print.css</a> file. Ours looks like this:</p>

<div class="wp_syntax"><div class="code"><pre class="css" style="font-family:monospace;"><span style="color: #808080; font-style: italic;">/* 26AM Print Styles */</span>
<span style="color: #a1a100;">@media print {</span>
	body <span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">font-family</span><span style="color: #00AA00;">:</span> arial<span style="color: #00AA00;">;</span>
		<span style="color: #000000; font-weight: bold;">font-size</span><span style="color: #00AA00;">:</span> <span style="color: #933;">11pt</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
	<span style="color: #cc00cc;">#header</span> <span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">display</span><span style="color: #00AA00;">:</span> <span style="color: #993333;">none</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
	a<span style="color: #00AA00;">,</span> a<span style="color: #3333ff;">:visited</span><span style="color: #00AA00;">,</span> a<span style="color: #3333ff;">:active </span><span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">color</span><span style="color: #00AA00;">:</span> <span style="color: #cc00cc;">#09C</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
	<span style="color: #cc00cc;">#printheader</span> <span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">display</span><span style="color: #00AA00;">:</span> <span style="color: #993333;">block</span><span style="color: #00AA00;">;</span>
		<span style="color: #000000; font-weight: bold;">background</span><span style="color: #00AA00;">:</span> <span style="color: #cc00cc;">#29ABE2</span><span style="color: #00AA00;">;</span>
		<span style="color: #000000; font-weight: bold;">padding</span><span style="color: #00AA00;">:</span> <span style="color: #933;">10px</span><span style="color: #00AA00;">;</span>
		<span style="color: #000000; font-weight: bold;">margin</span><span style="color: #00AA00;">:</span> <span style="color: #933;">1em</span> <span style="color: #cc66cc;">0</span> <span style="color: #933;">1em</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
	<span style="color: #cc00cc;">#printfooter</span> <span style="color: #00AA00;">&#123;</span>
	<span style="color: #000000; font-weight: bold;">font-size</span><span style="color: #00AA00;">:</span> <span style="color: #933;">10pt</span><span style="color: #00AA00;">;</span>
	<span style="color: #000000; font-weight: bold;">color</span><span style="color: #00AA00;">:</span> <span style="color: #cc00cc;">#666</span><span style="color: #00AA00;">;</span>
	<span style="color: #000000; font-weight: bold;">border-top</span><span style="color: #00AA00;">:</span> <span style="color: #933;">1px</span> <span style="color: #993333;">solid</span> <span style="color: #993333;">gray</span><span style="color: #00AA00;">;</span>
	<span style="color: #000000; font-weight: bold;">margin</span><span style="color: #00AA00;">:</span> <span style="color: #933;">2em</span> <span style="color: #cc66cc;">0</span> <span style="color: #cc66cc;">0</span><span style="color: #00AA00;">;</span>
	<span style="color: #000000; font-weight: bold;">padding</span><span style="color: #00AA00;">:</span> <span style="color: #933;">1em</span> <span style="color: #cc66cc;">0</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
 	<span style="color: #6666ff;">.breadcrumb</span> <span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">font-size</span><span style="color: #00AA00;">:</span> <span style="color: #933;">9pt</span><span style="color: #00AA00;">;</span>
		<span style="color: #000000; font-weight: bold;">margin</span><span style="color: #00AA00;">:</span> <span style="color: #cc66cc;">0</span> <span style="color: #cc66cc;">0</span> <span style="color: #933;">1em</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
	img<span style="color: #6666ff;">.authoravatar</span> <span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">display</span><span style="color: #00AA00;">:</span> <span style="color: #993333;">none</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
&nbsp;
	a.stbutton<span style="color: #00AA00;">,</span>
	h2.pagetitle<span style="color: #00AA00;">,</span>
	p.postmetadata<span style="color: #00AA00;">,</span>
	.respond<span style="color: #00AA00;">,</span>
	<span style="color: #cc00cc;">#respond</span><span style="color: #00AA00;">,</span>
	<span style="color: #cc00cc;">#sidebar</span><span style="color: #00AA00;">,</span>
	<span style="color: #cc00cc;">#footer</span> <span style="color: #00AA00;">&#123;</span>
		<span style="color: #000000; font-weight: bold;">display</span><span style="color: #00AA00;">:</span> <span style="color: #993333;">none</span><span style="color: #00AA00;">;</span>
	<span style="color: #00AA00;">&#125;</span>
<span style="color: #00AA00;">&#125;</span></pre></div></div>

<p>You&#8217;ll see that the majority of what we&#8217;ve done is hide things. You&#8217;ll also see that we are revealing things as well. We&#8217;ve hidden all the unnecessary information that we mentioned above, but then we revealed the printer friendly formatted information such as date and time stamp. Hope this has helped. If you&#8217;re working on a project for a client or for yourself, having a printer friendly version of the website can really show your attention to detail and care for the end user. Leave us a note and let us know if this has helped you.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.26am.com/blog/2010/01/27/printer-friendly-web-pages-with-print-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>26AM Version 2.0</title>
		<link>http://www.26am.com/blog/2009/10/26/26am-version-2-0/</link>
		<comments>http://www.26am.com/blog/2009/10/26/26am-version-2-0/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 06:54:51 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Company News]]></category>
		<category><![CDATA[Design Thoughts]]></category>
		<category><![CDATA[Just for Fun]]></category>

		<guid isPermaLink="false">http://www.26am.com/blog/?p=80</guid>
		<description><![CDATA[We&#8217;ve been thinking through our 26AM website for some time now. The current iteration of our site was never intended to be permanent. It was merely meant to serve as a place holder. So far, it&#8217;s done its job. However, we have been feeling more and more dissatisfied with the design and functionality. We need [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve been thinking through our 26AM website for some time now. The current iteration of our site was never intended to be permanent. It was merely meant to serve as a place holder. So far, it&#8217;s done its job. However, we have been feeling more and more dissatisfied with the design and functionality. We need something a little more maintainable and content driven. <span id="more-80"></span>So we&#8217;ve tried to hit some key points including:</p>
<ul>
<li>Showcasing our clients and the work we&#8217;ve performed for them</li>
<li>Providing information about our services</li>
<li>A simple quotation form</li>
<li>Updated blog design to display our thoughts and musings</li>
<li>Twitter feed in a more organized fashion</li>
<li>Prettier more functional design.</li>
</ul>
<p>Here&#8217;s what we came up with so far. Look for it soon live on our site!</p>
<p><a href="http://www.26am.com/blog/wp-content/uploads/2009/10/concept_1_a.jpg"><img class="alignnone size-medium wp-image-77" title="concept_1_a" src="http://www.26am.com/blog/wp-content/uploads/2009/10/concept_1_a-300x231.jpg" alt="concept_1_a" width="300" height="231" /></a></p>
<p><a href="http://www.26am.com/blog/wp-content/uploads/2009/10/concept_1_b.jpg"><img class="alignnone size-medium wp-image-78" title="concept_1_b" src="http://www.26am.com/blog/wp-content/uploads/2009/10/concept_1_b-287x300.jpg" alt="concept_1_b" width="287" height="300" /></a></p>
<p><a href="http://www.26am.com/blog/wp-content/uploads/2009/10/concept_1_c.jpg"><img class="alignnone size-medium wp-image-79" title="concept_1_c" src="http://www.26am.com/blog/wp-content/uploads/2009/10/concept_1_c-287x300.jpg" alt="concept_1_c" width="287" height="300" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.26am.com/blog/2009/10/26/26am-version-2-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design Coding Guidelines</title>
		<link>http://www.26am.com/blog/2009/04/05/design-coding-guidelines/</link>
		<comments>http://www.26am.com/blog/2009/04/05/design-coding-guidelines/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 03:46:33 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Design Thoughts]]></category>
		<category><![CDATA[Just for Fun]]></category>

		<guid isPermaLink="false">http://www.26am.com/blog/?p=60</guid>
		<description><![CDATA[It&#8217;s hard not to blog this. YouTube rap video is after the jump.

]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s hard not to blog this. YouTube rap video is after the jump.<span id="more-60"></span></p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/a0qMe7Z3EYg&amp;hl=en&amp;fs=1" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="425" height="344" src="http://www.youtube.com/v/a0qMe7Z3EYg&amp;hl=en&amp;fs=1" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.26am.com/blog/2009/04/05/design-coding-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web 2.0 is old skool</title>
		<link>http://www.26am.com/blog/2009/03/04/web-20-is-old-skool/</link>
		<comments>http://www.26am.com/blog/2009/03/04/web-20-is-old-skool/#comments</comments>
		<pubDate>Wed, 04 Mar 2009 21:26:02 +0000</pubDate>
		<dc:creator>David</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Design Thoughts]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Web 2.0]]></category>

		<guid isPermaLink="false">http://www.26am.com/blog/?p=46</guid>
		<description><![CDATA[Remember when &#8220;Web 2.0&#8243; was as talked about as the weather? Everyone wanted their site to look Web 2.0. There were blog posts galore about companies becoming Web 2.0. When it comes down to it, Web 2.0 is really a couple of things: being social, using ajax, and efficient design. One of the things that [...]]]></description>
			<content:encoded><![CDATA[<p>Remember when &#8220;Web 2.0&#8243; was as talked about as the weather? Everyone wanted their site to look Web 2.0. There were blog posts galore about companies becoming Web 2.0. When it comes down to it, Web 2.0 is really a couple of things: being social, using ajax, and efficient design. One of the things that drove me crazy during all the buzz was that everyone felt the need to make their site Web 2.0. That to me is &#8220;fad mentality.&#8221; It hasn&#8217;t really seemed to serve anyone in the past nor do I think it&#8217;ll serve anyone now. Web 2.0ishness doesn&#8217;t apply to everyone. Having a blog doesn&#8217;t apply to someone looking to put their plumbing business online. That kind of site needs basic Search Engine Optimization and the facts about their services.</p>
<p>So if you&#8217;re thinking about Web 2.0ing (not a real word) your company/site/brand, ask yourself a few questions:</p>
<ul>
<li>Will my company benefit from interacting with customers/members/clients through the web?</li>
<li>Are my clients actually people who use the web to interact? (Most construction companies don&#8217;t use the web to conduct business)</li>
<li>Are there better ways for me to drum up business/awareness for our company?</li>
</ul>
<p>I&#8217;m not against Web 2.0, heck 26AM has jumped on the concept. I am however against trying to make something hip and trendy when it serves no purpose and in fact could potentially hurt a business.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.26am.com/blog/2009/03/04/web-20-is-old-skool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
