<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0" xml:base="http://douglast.com">
<channel>
 <title>Thoughts on Design</title>
 <link>http://douglast.com</link>
 <description />
 <language>en</language>
<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/douglast/IrOj" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="douglast/iroj" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
 <title>Do You Hear Yourself?</title>
 <link>http://douglast.com/archives/368</link>
 <description>&lt;p&gt;Do you subscribe to your own RSS feeds?  You should. It may sound like a strange form of vanity but it's not. It's a defense mechanism. If you don't subscribe, how do you know what your readers are getting? I subscribe to my personal site and social media feeds, as well as those of sites I work on.  Several times I've caught and fixed problems with feeds before clients or readers have noticed anything.&lt;/p&gt;
&lt;p&gt;This week I caught a problem on my own LinkedIn account. I'm not sure why, but LinkedIn suddenly started aggregating &lt;a href="http://twitter.com/tschet"&gt;my Twitter account.&lt;/a&gt; This is not something that I'm interested in. I caught it after only a few tweets because it showed up in my LinkedIn feed. If I didn't subscribe it could have been months before I noticed.&lt;/p&gt;
&lt;p&gt;What should you subscribe to?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Your company site &lt;/li&gt;
&lt;li&gt;Your blog&lt;/li&gt;
&lt;li&gt;Your social media sites &lt;/li&gt;
&lt;li&gt;Hashtags and news searches for you, your company, or your industry&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Any subscription you'd add?&lt;/p&gt;
&lt;p&gt;I use Google Reader which I sync to several computers and other devices, but there are a number of good feed readers available.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/368#comments</comments>
 <category domain="http://douglast.com/tag/rss">RSS</category>
 <category domain="http://douglast.com/category/blogging">Blogging</category>
 <category domain="http://douglast.com/category/social-media">Social Media</category>
 <pubDate>Sun, 19 Jun 2011 12:43:29 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">368 at http://douglast.com</guid>
</item>
<item>
 <title>iPad Wallpaper Images</title>
 <link>http://douglast.com/archives/367</link>
 <description>&lt;p&gt;I've been spending a lot of time with Photoshop lately, and I'd like to share some of my work with you. Jump over to &lt;a href="http://rivendesign.com/wallpaper"&gt;Riven Design and check out the iPad wallaper images&lt;/a&gt; we've put up. When I have time I'll add some other formats.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/367#comments</comments>
 <category domain="http://douglast.com/category/ipad">iPad</category>
 <category domain="http://douglast.com/category/software/photoshop">Photoshop</category>
 <category domain="http://douglast.com/category/photography">Photography</category>
 <pubDate>Tue, 03 May 2011 04:49:34 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">367 at http://douglast.com</guid>
</item>
<item>
 <title>We Have Not Forgotten</title>
 <link>http://douglast.com/archives/366</link>
 <description>&lt;p class="align-center"&gt;&lt;img src="http://douglast.com/sites/douglast.com/files/not-forgotten-web.png" alt="We Have not Forgotten" /&gt;&lt;/p&gt;
&lt;p&gt;It's hard to believe it's been four years. These images are free to use anywhere you'd like for personal reasons. Other formats could be made available. Let me know where you use them if it's convenient. The images have transparent backgrounds except for the one specifically noted.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://douglast.com/sites/douglast.com/files/not-forgotten.png"&gt;Not Forgotten Image&lt;/a&gt; (Full Size)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://douglast.com/sites/douglast.com/files/not-forgotten-web.png"&gt;Not Forgotten Image for Web&lt;/a&gt; (Shown above)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://douglast.com/sites/douglast.com/files/not-forgotten-web.jpg"&gt;Not Forgotten Image for Web &lt;/a&gt;(white background)&lt;/li&gt;
&lt;li&gt;&lt;a href="http://douglast.com/sites/douglast.com/files/not-forgotten-150.png"&gt;Not Forgotten Image Icon&lt;/a&gt; (150px) &lt;/li&gt;
&lt;/ul&gt;
</description>
 <comments>http://douglast.com/archives/366#comments</comments>
 <pubDate>Sat, 16 Apr 2011 14:59:51 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">366 at http://douglast.com</guid>
</item>
<item>
 <title>Flipboard and Accessibility</title>
 <link>http://douglast.com/archives/365</link>
 <description>&lt;p&gt;&lt;img class="img-left" src="http://douglast.com/sites/douglast.com/files/accessibility.jpg" alt="Accessibility Logo" width="216" height="72" /&gt;I think iPad apps like &lt;a href="http://flipboard.com/"&gt;Flipboard&lt;/a&gt; may turn out to be one of the best things to happen to accessibility in quite a while. Not because they are accessibility tools themselves, because they are not. No, this is a bonus for accessibility because it will let users who would never think about accessibility see the consequences of bad code. Good semantic code with all the style controlled by CSS looks wonderful when it's pulled into Flipboard. Poorly written code using inline styles, spaces, and other tricks to control the design don't fair so well.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/365#comments</comments>
 <category domain="http://douglast.com/category/web-design/accessibility">Accessibility</category>
 <category domain="http://douglast.com/category/ipad">iPad</category>
 <category domain="http://douglast.com/category/web-design/html">HTML</category>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Sun, 27 Mar 2011 02:37:03 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">365 at http://douglast.com</guid>
</item>
<item>
 <title>BlogDesk</title>
 <link>http://douglast.com/archives/364</link>
 <description>&lt;p&gt;&lt;a href="http://www.blogdesk.org"&gt;BlogDesk&lt;/a&gt; is a fairly nice desktop blogging client. In simpler terms it's a piece of software that lets you post to your blog from your desktop without using the web browser. This allows for some added features over a lot of blogging platforms. It supports a wide range of blog platforms including &lt;a href="http://wordpress.org/"&gt;WordPress&lt;/a&gt;, &lt;a href="http://www.sixapart.com/movabletype/"&gt;MovableType&lt;/a&gt;, &lt;a href="http://drupal.org/"&gt;Drupal&lt;/a&gt;, and &lt;a href="http://www.s9y.org/"&gt;Serendipity&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;My thoughts of BlogDesk:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Easy to install&lt;/li&gt;
&lt;li&gt;Easy to setup with your blog&lt;/li&gt;
&lt;li&gt;Supports WordPress custom fields, but doesn't support custom fields in other blog platforms.&lt;/li&gt;
&lt;li&gt;Reasonable formatting and control of text&lt;/li&gt;
&lt;li&gt;No trouble handling images&lt;/li&gt;
&lt;li&gt;Had not trouble pulling in my categories&lt;/li&gt;
&lt;li&gt;Allows editign of older posts, even those written before I installed it.&lt;/li&gt;
&lt;li&gt;You can schedule posts for later&lt;/li&gt;
&lt;li&gt;Spellcheck as you would expect from something like this&lt;/li&gt;
&lt;li&gt;Auto tag generation is a nice touch&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Overall I was impressed. A nice piece of software. My only dissapointment was that it did not support custom fields for anything other than WordPress. I develop with Drupal an I use custom fields extensively.&amp;nbsp; The lack of support for custom field rules out my use of this product and means I will not be suggesting it for most of my clients. For anyone who wants to post to a blog or site without custom fields, I would reccomend it.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/364#comments</comments>
 <category domain="http://douglast.com/category/blogging">Blogging</category>
 <category domain="http://douglast.com/category/social-media">Social Media</category>
 <pubDate>Fri, 25 Mar 2011 12:15:30 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">364 at http://douglast.com</guid>
</item>
<item>
 <title>Drupal Presentation</title>
 <link>http://douglast.com/archives/362</link>
 <description>&lt;p&gt;I gave a presentation to a local social media group called &lt;a href="http://www.ndtweetup.com/2010/10/reminder-ndtweetup-this-thursday-oct-14-at-1130-am/"&gt;NDTweetup&lt;/a&gt; earlier today. I walked through various Drupal capabilities, discussed installation profiles, and showed some examples of Drupal sites. Over the course of the meeting we discussed the versatility and capabilities of Drupal and other &lt;acronym title="Content Management System"&gt;CMS&lt;/acronym&gt; products. Drupal's ability to both generated RSS feeds and to aggregate them was one of the more popular points of discussion. Drupal's feed handling brought up a number of interesting ideas for use in social media. I've listed below the Drupal resources and Drupal sites we discussed.&lt;/p&gt;
&lt;h2&gt;Drupal Resources&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://drupal.org"&gt;Drupal&lt;/a&gt;.org&lt;/li&gt;
&lt;li&gt;&lt;a href="http://openatrium.com/"&gt;Open Atrium&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://managingnews.com/"&gt;Managing News&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://openscholar.harvard.edu/home"&gt;Open Scholar&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Featured Sites&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://cdhs.net/"&gt;Central Dakota Humane Society&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://whitecaprods.com/"&gt;Whitecap Custom Rods&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.nd.gov/amber"&gt;North Dakota Amber Alert&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.nd.gov/ndhp"&gt;North Dakota Highway Patrol&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://douglast.com/"&gt;Thoughts on Design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://rivendesign.com"&gt;Riven Design&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://ndba.org/"&gt;North Dakota Broadcasters Association&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
 <comments>http://douglast.com/archives/362#comments</comments>
 <category domain="http://douglast.com/category/web-design/drupal">Drupal</category>
 <pubDate>Thu, 14 Oct 2010 23:02:52 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">362 at http://douglast.com</guid>
</item>
<item>
 <title>A Link of a Different Color</title>
 <link>http://douglast.com/archives/361</link>
 <description>&lt;p&gt;I've been spending a lot of time reviewing websites lately. I keep seeing the same few mistakes over and over. Some of them may be intentional design choices, but for the most part they seem to be mistakes of omission. What I'm seeing is incomplete CSS for links. Incomplete link CSS does one of two things.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;It can allow the site's presentation to fall back on the browsers default CSS, a poor design decision in my viewpoint.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;It can also be written is such a way as to be applied to all aspects of links. This would make a hovered link unchanged from a regular link.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The styling of links serves a purpose. It identifies links for the user. When a hovered link changes from a non-hovered link, it helps in that identification.&lt;/p&gt;
&lt;p&gt;Let's start with a few basic CSS rules. &lt;a href="http://www.w3.org/TR/WCAG20/"&gt;Modern accessibility standards&lt;/a&gt; suggest that you should use more than just color to identify anything of significance. So the CSS for links should include two variations from traditional text. I'd suggest a distinct color and the traditional underline, but most any two should work.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;a {color:#333300; &lt;/code&gt;&lt;code&gt;font-weight:bold; &lt;/code&gt;&lt;code&gt;}a:link { &lt;/code&gt;&lt;code&gt;text-decoration:underline;}&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Making visited links a slightly different color is also helpful for tracking where you've been in a site.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;a:visited { color:#333333;}&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;I'd also suggest using the hover pseudo class to make the hover state different.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;a:hover{ text-decoration:none;}&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Are we done? Not quite. This is where I keep seeing sites fall short. You also need to define the &lt;a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes"&gt;active and focus states&lt;/a&gt;. Without definition, these will both default to either browser default or your own link CSS.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;a:hover, a:active, a:focus { text-decoration:none;}&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;These three states can be together as shown above, or with completely different CSS, the choice is yours.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/361#comments</comments>
 <category domain="http://douglast.com/category/web-design/accessibility">Accessibility</category>
 <category domain="http://douglast.com/category/web-design/css">CSS</category>
 <pubDate>Fri, 24 Sep 2010 01:03:50 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">361 at http://douglast.com</guid>
</item>
<item>
 <title>Social Media is not the end!</title>
 <link>http://douglast.com/archives/360</link>
 <description>&lt;p&gt;Is your social media strategy backwards? Are you tweeting about what you've posted on &lt;a href="http://www.facebook.com/"&gt;Facebook&lt;/a&gt;? Posting on Facebook about what you're doing on &lt;a href="http://twitter.com/"&gt;Twitter&lt;/a&gt; or your &lt;a href="http://wordpress.com"&gt;Wordpress.com&lt;/a&gt; blog? Social media tools like this are beautiful tools, but they are just tools. Don't let them be the focus. They are to direct traffic, not to be the target of your traffic. Post your content on your own site, and use your social media tools to bring the people to you.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you're directing traffic to your social media tools, your pushing people the wrong way.&lt;/strong&gt;&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/360#comments</comments>
 <category domain="http://douglast.com/category/social-media">Social Media</category>
 <pubDate>Fri, 06 Aug 2010 12:14:24 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">360 at http://douglast.com</guid>
</item>
<item>
 <title>North Dakota Amber Alert</title>
 <link>http://douglast.com/archives/359</link>
 <description>&lt;p&gt;I recently had the pleasure of finishing another &lt;a href="http:/www.nd.gov/itd"&gt;ITD&lt;/a&gt; design project, I was able to work with a number of great people at ITD, as well as the &lt;a href="http://www.nd.gov/ndhp"&gt;NDHP&lt;/a&gt; and &lt;a href="http://www.nd.gov/des"&gt;Department of Emergency Services&lt;/a&gt; to update the Amber Alert website. Like the recent NDHP site, this was both a redesign and a &lt;a href="http://drupal.org"&gt;Drupal&lt;/a&gt; conversion project.&amp;nbsp; Based strongly on the NDHP's design, the Amber Alert site is built using &lt;a href="http://drupal.org/project/zen"&gt;Zen&lt;/a&gt;. My contribution to this site was the Drupal theming.&lt;/p&gt;
&lt;p class="align-center"&gt;&lt;a href="http://www.nd.gov/amber"&gt;&lt;img src="/sites/douglast.com/files/amberalert.jpg" alt="North Dakota Amber Alert screenshot" /&gt;&lt;/a&gt;&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/359#comments</comments>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Fri, 06 Aug 2010 12:05:54 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">359 at http://douglast.com</guid>
</item>
<item>
 <title>Who's your navigation for?</title>
 <link>http://douglast.com/archives/356</link>
 <description>&lt;p class="align-center"&gt;&lt;a href="http://xkcd.com/773/"&gt;&lt;img src="http://imgs.xkcd.com/comics/university_website.png" alt="University website comic" width="541" height="378" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A perfect example of a common navigation problem by &lt;a href="http://xkcd.com/"&gt;xkcd&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;Who is your navigation for?&lt;/h2&gt;
&lt;p&gt;The specific, but diverse populations within a University have&amp;nbsp; caused some horrible navigation choices. &lt;em&gt;Who's your audience?&lt;/em&gt; If a University directs their navigation towards your students, the faculty can't find anything. If they direct it towards the faculty, the students can't find anything. That's not even considering other audiences like parents, sports fans, and potential students.&lt;/p&gt;
&lt;p&gt;It's not a problem specific to Universities, they just make a great scapegoat. The same problem can be seen in much simpler sites. The audience the site design was targeted to, and the &lt;em&gt;real&lt;/em&gt; audience aren't always the same group of people.&lt;/p&gt;
&lt;p&gt;Who was your site designed for? Did you target the right audience? Do you have more than one audience? Are they different enough that it would require compromises be made with aspects of the site like navigation? In the case of Universities, they may even be diverse enough to require different site structure or navigation. State government sites can be the same way. A number of state sites have taken to dividing their home page by audience and giving each audience their own version of the home page. The &lt;a href="http://www.delaware.gov/"&gt;Delaware state government site&lt;/a&gt; is a reasonable example. They use tabs for each primary audience.&lt;/p&gt;
&lt;p&gt;It's unlikely that a personal or small business site would need to go to this extreme, but it is very possible that you're not targeting the right audience. Take a moment and pretend to be a member of your primary audience. Look at your site as if you'd never seen it before. Does the organization and navigation make sense? You might like what you see, but you might be surprised too. Good luck.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/356#comments</comments>
 <category domain="http://douglast.com/category/web-design/accessibility">Accessibility</category>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Fri, 30 Jul 2010 11:56:19 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">356 at http://douglast.com</guid>
</item>
<item>
 <title>Potential Change in Web Accessibility Requirements</title>
 <link>http://douglast.com/archives/355</link>
 <description>&lt;p&gt;&lt;a href="http://www.ada.gov/anprm2010/web%20anprm_2010.htm"&gt;DEPARTMENT OF JUSTICE - Advance Notice of Proposed Rulemaking.&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;"Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities and Public Accommodations"&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;The department of Justice has given advance notice of a proposal to change the regulations for web accessibility requirements for State and local governments. One of the suggestions in the document is to change to the &lt;a href="http://www.w3.org/TR/WCAG20/"&gt;WCAG 2.0 standard&lt;/a&gt;. State and local governments currently are required to meet the &lt;a href="http://www.access-board.gov/508.htm"&gt;Section 508&lt;/a&gt; standard, though a number of them have chosen the more stringent &lt;a href="http://www.w3.org/TR/WCAG10/"&gt;WCAG 1.0&lt;/a&gt; as the state standard. A change to the WCAG 2.0 standard is significant. Raising a site from WCAG 1.0 to WCAG 2.0 can in some cases be simple, but in some cases it can also require a complete redesign.Accessibility needs to be built into a site from the ground up, not as an afterthought. With sites designed around accessibility, a change may not be too difficult. When accessibility was forced onto an inaccessible design the WCAG 2.0 standard may not be within reach without a complete restructuring of the site.This may be a good time to evaluate where your site stands in terms of accessibility. Try out a tool like &lt;a href="http://cynthiasays.com/"&gt;Cynthia Says&lt;/a&gt; and see how your site does. Regardless of the outcome of this proposal, I think that the focus this will bring on accessibility will be a good thing.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/355#comments</comments>
 <category domain="http://douglast.com/category/web-design/accessibility">Accessibility</category>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Wed, 28 Jul 2010 18:07:08 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">355 at http://douglast.com</guid>
</item>
<item>
 <title>North Dakota Highway Patrol goes Drupal</title>
 <link>http://douglast.com/archives/354</link>
 <description>&lt;p&gt;Working at &lt;a href="http://www.nd.gov/itd"&gt;ITD&lt;/a&gt;, I had the opportunity to redesign the &lt;a href="http://www.nd.gov/ndhp"&gt;North Dakota Highway Patrol's website&lt;/a&gt;. This was both a redesign, and a &lt;a href="http://drupal.org"&gt;Drupal&lt;/a&gt; conversion project. Using Drupal allowed us to develop a very nice looking site that can easily be maintained. Content can be maintained by the people who are familiar with the organization, the staff of the NDHP. &lt;a href="http://www.nd.gov/ndhp"&gt;www.nd.gov/ndhp&lt;/a&gt; is built in Drupal using &lt;a href="http://drupal.org/project/zen"&gt;Zen&lt;/a&gt;.&lt;/p&gt;
&lt;p class="align-center"&gt;&lt;a href="http://www.nd.gov/ndhp"&gt;&lt;img src="/sites/douglast.com/files/nd-gov-ndhp.jpg" alt="North Dakota Highway Patrol screenshot" height="461" width="500" /&gt;&lt;/a&gt;&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/354#comments</comments>
 <category domain="http://douglast.com/category/web-design/drupal">Drupal</category>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Fri, 16 Jul 2010 12:19:06 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">354 at http://douglast.com</guid>
</item>
<item>
 <title>Central Dakota Humane Society</title>
 <link>http://douglast.com/archives/353</link>
 <description>&lt;p&gt;Riven Design has &lt;a href="http://www.rivendesign.com/news/central-dakota-humane-society"&gt;converted the Central Dakota Humane Society's website&lt;/a&gt; to &lt;a href="http://drupal.org"&gt;Drupal&lt;/a&gt;.&lt;/p&gt;
&lt;p class="align-center"&gt;&lt;a href="http://cdhs.net"&gt;&lt;img src="/sites/douglast.com/files/www_cdhs_net.jpg" alt="Central Dakota Humane Society screenshot" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://cdhs.net"&gt;new CDHS site&lt;/a&gt; features a pet resource library, galleries of available pets, a news section, and much more.&amp;nbsp; Several custom content types, and extensive use of the &lt;a href="http://drupal.org/project/views"&gt;Views module&lt;/a&gt; allowed us to make the nice looking and easy to maintain. Content is placed in appropriate menus automatically when saved, and the library and pet galleries are created dynamically. This site's theme was developed with subtheme method, using &lt;a href="http://drupal.org/project/zen"&gt;Zen&lt;/a&gt;.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/353#comments</comments>
 <category domain="http://douglast.com/category/web-design/drupal">Drupal</category>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Fri, 09 Jul 2010 11:59:56 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">353 at http://douglast.com</guid>
</item>
<item>
 <title>Basic Website Testing</title>
 <link>http://douglast.com/archives/351</link>
 <description>&lt;p&gt;I've been asked a number of times lately how I test websites that I work on. While I'm never shy about talking about this sort of thing, I thought writing it down might be beneficial.&lt;/p&gt;
&lt;h2&gt;The Basic Browser Check&lt;/h2&gt;
&lt;p&gt;Visually check your site in several browsers. I'd suggest testing pages in a number of browsers. Always include Internet Explorer, preferably several versions. I'd also throw in &lt;a href="http://www.mozilla.com/en-US/firefox/firefox.html"&gt;Firefox&lt;/a&gt;, &lt;a href="http://www.google.com/chrome/intl/en/landing_chrome.html?hl=en"&gt;Chrome&lt;/a&gt;, &lt;a href="http://www.opera.com/"&gt;Opera&lt;/a&gt;, or &lt;a href="http://www.apple.com/safari/"&gt;Safari&lt;/a&gt; as you are able. Bonus points if you're testing in all of these and a few I didn't name. Demerits if your default browser is still IE. Double demerits if you only test in IE.&amp;nbsp; Checking it on both a PC and a Mac is good, adding Linux is better.&lt;/p&gt;
&lt;h3&gt;What do I look for?&lt;/h3&gt;
&lt;p&gt;At this point your looking for basic function. Does the browser display what you expect? Minor spacing variations may be acceptable. A few pixels here or there often make little difference. Sometimes they make a great deal of difference, and you need to be prepared to fix the variations that count. When the difference is 10 pixels between headings and paragraphs versus 11 pixels, you might want to consider how many people will notice versus how much time it will take to fix. If you have misaligned background images, you just buckle down and fix the problem.&lt;/p&gt;
&lt;h2&gt;Raising the Bar - Validation&lt;/h2&gt;
&lt;p&gt;Next step, validate everything. There are a number of ways to check site validation. Find one or more of these that work for you and use them early and often. I list several tools I use on &lt;a href="http://douglast.com/design-resources"&gt;my resources page&lt;/a&gt;, but there are others. &lt;a href="http://www.google.com/search?ie=UTF-8&amp;amp;oe=UTF-8&amp;amp;sourceid=navclient&amp;amp;gfns=1&amp;amp;q=validation+tools"&gt;A Google search for validation tools&lt;/a&gt; should come up with a multitude of choices. I test templates as I develop, then I continue spot checking through the lifetime of the site design. I also use site quality testing tools like &lt;a href="http://www.hisoftware.com/products/compliancesheriffoverview.htm"&gt;Compliance Sheriff&lt;/a&gt;, but that can definitely be overkill for smaller projects.&lt;/p&gt;
&lt;p&gt;If you use Firefox, try the &lt;a href="http://www.hisoftware.com/products/compliancesheriffoverview.htm"&gt;HTML Validator&lt;/a&gt; and &lt;a href="http://www.hisoftware.com/products/compliancesheriffoverview.htm"&gt;Web Developer Toolbar&lt;/a&gt; for testing validation. They let you test HTML, CSS, and JavaScript on the fly.&lt;/p&gt;
&lt;h2&gt;Accessibility&lt;/h2&gt;
&lt;p&gt;This is going to be a sinple explanation of a complex topic, but here are a few ways to test for accessibility issues.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use the &lt;a href="http://www.visionaustralia.org.au/info.aspx?page=628"&gt;Colour Contrast Analyser&lt;/a&gt; to analyze color contrast for accessibility purposes &lt;/li&gt;
&lt;li&gt;Try &lt;a href="http://cynthiasays.com/"&gt;Cynthia Says&lt;/a&gt; to test basic accessibility&lt;a href="http://cynthiasays.com/"&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Test with the &lt;a href="http://www.visionaustralia.org.au/info.aspx?page=614"&gt;Web Accessibility Toolbar&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Try the Firefox accessibility extension too&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;None of these are the perfect tool, but they're all helpful and free.&lt;/p&gt;
&lt;h2&gt;What's it all mean?&lt;/h2&gt;
&lt;p&gt;These are all tests and tools. None of them will give you a perfect site, but they'll let you know what you have. Knowing what the issues are is the first step in solving them.&amp;nbsp; Good luck, I hope all your projects go well. Check back soon, I have a more in-depth look into testing for site quality and accessibility planned for the near future.&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/351#comments</comments>
 <category domain="http://douglast.com/category/web-design/validation-and-testing">Validation and Testing</category>
 <pubDate>Thu, 08 Jul 2010 04:00:21 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">351 at http://douglast.com</guid>
</item>
<item>
 <title>Ze Frank and Jobz</title>
 <link>http://douglast.com/archives/350</link>
 <description>&lt;p&gt;&lt;a href="http://www.zefrank.com/jobz/"&gt;Ze Frank is hiring.&lt;/a&gt; I say this not because I'm interested, but because I like the way he wrote the job descriptions. Two statements jump out at me.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;"You should have sent at least one email to someone you have never met telling them that they should stop using tables." &lt;/li&gt;
&lt;li&gt;The phrase “Please make that look more like a Muppet vomited SteamPunk.” should seem like satisfactory art direction, and to be honest there was no need to use the word “please”.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Email strangers about the perils of table layout? I have to admit I've sent those emails a few times, but I really don't like to. &lt;em&gt;I prefer to use the offending site's contact form.&lt;/em&gt; The second statement confuses me a little though. How could "Muppet vomits Steampunk" be considered a vague artistic direction. I'd only have one question in response to that direction. &lt;em&gt;Which muppet&lt;/em&gt;?&lt;/p&gt;
</description>
 <comments>http://douglast.com/archives/350#comments</comments>
 <category domain="http://douglast.com/category/web-design">Web Design</category>
 <pubDate>Thu, 08 Jul 2010 03:13:08 +0000</pubDate>
 <dc:creator>Douglas T</dc:creator>
 <guid isPermaLink="false">350 at http://douglast.com</guid>
</item>
</channel>
</rss>

