<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Top Five Ways You Know The Redesign of Your Nonprofit Web Site Went Bad</title>
	<atom:link href="http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/feed" rel="self" type="application/rss+xml" />
	<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad</link>
	<description>Confessions of a Non-Profit Executive Director</description>
	<lastBuildDate>Mon, 15 Mar 2010 09:12:34 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Build A Nonprofit’s Technology Assets From The Ground Up, Part 2 OF 4</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-100338</link>
		<dc:creator>Build A Nonprofit’s Technology Assets From The Ground Up, Part 2 OF 4</dc:creator>
		<pubDate>Wed, 22 Apr 2009 00:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-100338</guid>
		<description>[...] you should certainly shoot for  the strong graphical quality of the websites listed here despite what I have to say about them.  Being a good looking website has all sorts of benefits to it like getting people to buy into [...]</description>
		<content:encoded><![CDATA[<p>[...] you should certainly shoot for  the strong graphical quality of the websites listed here despite what I have to say about them.  Being a good looking website has all sorts of benefits to it like getting people to buy into [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Benamer</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-100208</link>
		<dc:creator>Allan Benamer</dc:creator>
		<pubDate>Tue, 03 Mar 2009 22:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-100208</guid>
		<description>I hear ya! Please report back on how it all turns out either on your blog or here. And trust me, this isn&#039;t something limited only to Australia or the US. It&#039;s somewhat endemic to our sector (although the for-profit sector has its own egregious examples). </description>
		<content:encoded><![CDATA[<p>I hear ya! Please report back on how it all turns out either on your blog or here. And trust me, this isn&#039;t something limited only to Australia or the US. It&#039;s somewhat endemic to our sector (although the for-profit sector has its own egregious examples).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason King</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-100202</link>
		<dc:creator>Jason King</dc:creator>
		<pubDate>Mon, 02 Mar 2009 09:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-100202</guid>
		<description>I&#039;m currently undertaking a similar exercise with the websites of 120 small nonprofits in Victoria, Australia; very few of them are beautiful or inspirational but it will be interesting to see whether I find more or fewer coding errors than you did. Few so far have valid HTML. 
 
The good news is that I now see more CSS than table-based layouts. The main technical problems I&#039;ve found are: 
 
- No CMS or sometimes an awful custom-built CMS; 
- Meaningless URLs. 
- Uninformative title tags or they&#039;re identical on all pages. 
- they&#039; never check the stats or don&#039;t have the password. 
- Website created in Microsoft Publisher (ok, only one of those so far). </description>
		<content:encoded><![CDATA[<p>I&#039;m currently undertaking a similar exercise with the websites of 120 small nonprofits in Victoria, Australia; very few of them are beautiful or inspirational but it will be interesting to see whether I find more or fewer coding errors than you did. Few so far have valid HTML. </p>
<p>The good news is that I now see more CSS than table-based layouts. The main technical problems I&#039;ve found are: </p>
<p>- No CMS or sometimes an awful custom-built CMS;<br />
- Meaningless URLs.<br />
- Uninformative title tags or they&#039;re identical on all pages.<br />
- they&#039; never check the stats or don&#039;t have the password.<br />
- Website created in Microsoft Publisher (ok, only one of those so far).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Examples of inspirational nonprofit web design &#171; Nonprofit web design &#171; by Jason King</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-100201</link>
		<dc:creator>Examples of inspirational nonprofit web design &#171; Nonprofit web design &#171; by Jason King</dc:creator>
		<pubDate>Mon, 02 Mar 2009 09:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-100201</guid>
		<description>[...] a contrary note, as Confessions of a Nonprofit Executive Director points out, web beauty is only skin-deep and whilst the 40 inspirational website all look great, they&#8217;ve not all been well coded (but [...]</description>
		<content:encoded><![CDATA[<p>[...] a contrary note, as Confessions of a Nonprofit Executive Director points out, web beauty is only skin-deep and whilst the 40 inspirational website all look great, they&#8217;ve not all been well coded (but [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Build A Nonprofit&#8217;s Technology Assets From The Ground Up, Part 2 OF 4 &#124; Non-Profit Tech Blog</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-100139</link>
		<dc:creator>Build A Nonprofit&#8217;s Technology Assets From The Ground Up, Part 2 OF 4 &#124; Non-Profit Tech Blog</dc:creator>
		<pubDate>Wed, 18 Feb 2009 14:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-100139</guid>
		<description>[...] you should certainly shoot for  the strong graphical quality of the websites listed here despite what I have to say about them.  Being a good looking website has all sorts of benefits to it like getting people to buy into [...]</description>
		<content:encoded><![CDATA[<p>[...] you should certainly shoot for  the strong graphical quality of the websites listed here despite what I have to say about them.  Being a good looking website has all sorts of benefits to it like getting people to buy into [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Benamer</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-99483</link>
		<dc:creator>Allan Benamer</dc:creator>
		<pubDate>Mon, 19 Jan 2009 13:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-99483</guid>
		<description>Understood, O Boy. I think that&#039;s one of the reasons I started blogging. It was kinda clear to me that nonprofit management tends to think of technology as an afterthought and a whole lot of issues break down in the manner you described. It has always been my hope that nonprofit management would read blogs like mine so that they can avoid many of the pitfalls that can occur when dealing with technology issues. </description>
		<content:encoded><![CDATA[<p>Understood, O Boy. I think that&#039;s one of the reasons I started blogging. It was kinda clear to me that nonprofit management tends to think of technology as an afterthought and a whole lot of issues break down in the manner you described. It has always been my hope that nonprofit management would read blogs like mine so that they can avoid many of the pitfalls that can occur when dealing with technology issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: O Boy</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-99471</link>
		<dc:creator>O Boy</dc:creator>
		<pubDate>Mon, 19 Jan 2009 05:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-99471</guid>
		<description>The real issue that vendors - whether they offer networking, web sites, software etc.. take advantage of the fact that nonprofits don&#039;t usually know what a complete end product looks like. They charge full rates for half finished work, because its easy, quick and no one usually finds out until the next vendor comes in. I won&#039;t even get into the number of sub par CMS software packages that have been dumped on nonprofits. SMH. Quite a few IT employees at nonprofits are also taking advantage of their employer&#039;s lack of knowledge.  </description>
		<content:encoded><![CDATA[<p>The real issue that vendors &#8211; whether they offer networking, web sites, software etc.. take advantage of the fact that nonprofits don&#039;t usually know what a complete end product looks like. They charge full rates for half finished work, because its easy, quick and no one usually finds out until the next vendor comes in. I won&#039;t even get into the number of sub par CMS software packages that have been dumped on nonprofits. SMH. Quite a few IT employees at nonprofits are also taking advantage of their employer&#039;s lack of knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Benamer</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-99229</link>
		<dc:creator>Allan Benamer</dc:creator>
		<pubDate>Sat, 10 Jan 2009 12:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-99229</guid>
		<description>Carlos, I looked up &quot;keyword stuffing&quot; (just to jog my memory) on Wikipedia and it states:  
  
&lt;blockquote&gt;Keyword stuffing occurs when a web page is loaded with keywords in the meta tags or in content. The repetition of words in meta tags may explain why many search engines no longer use these tags.&lt;/blockquote&gt;  
  
Historically, people used to do keyword stuffing within the meta tags. At least, that&#039;s how I remember it back in the day. People did end up doing it within content (hidden divs and other crap like that) but the &quot;original&quot; attempts at keyword stuffing were within the meta tags.  
  
And no, donors don&#039;t make donation decisions based on whether a site has &lt;TITLE&gt; tags. However, Google does make decisions on your PageRank based on those simple tags being used properly. Basically, they just ask you not to abuse HTML for your nefarious SEO purposes. I tend to agree.  
  
I think some of these sites were using CMS software yet not using them properly. You can see them having a space for META description or keywords but there was nothing in there. It was weird to look at.  
  
Sure, some of these sites could be using server log files on the backend. I&#039;ve found server log files to be useful but they&#039;re not as accepted as Google Analytics is these days when you&#039;re discussing your site traffic. This is a decision about the social acceptability of your stats more than &lt;a href=&quot;http://en.wikipedia.org/wiki/Web_analytics#Logfile_analysis_vs_page_tagging&quot; rel=&quot;nofollow&quot;&gt;a discussion about the technical merits of log file analysis vs. Javascript-based trackers&lt;/a&gt;.  
  
We definitely agree -- let&#039;s get nonprofit managers thinking more about how their sites can be managed to their mission statements and not to their egos. </description>
		<content:encoded><![CDATA[<p>Carlos, I looked up &quot;keyword stuffing&quot; (just to jog my memory) on Wikipedia and it states:  </p>
<blockquote><p>Keyword stuffing occurs when a web page is loaded with keywords in the meta tags or in content. The repetition of words in meta tags may explain why many search engines no longer use these tags.</p></blockquote>
<p>Historically, people used to do keyword stuffing within the meta tags. At least, that&#39;s how I remember it back in the day. People did end up doing it within content (hidden divs and other crap like that) but the &quot;original&quot; attempts at keyword stuffing were within the meta tags.  </p>
<p>And no, donors don&#39;t make donation decisions based on whether a site has &amp;lt;TITLE&gt; tags. However, Google does make decisions on your PageRank based on those simple tags being used properly. Basically, they just ask you not to abuse HTML for your nefarious SEO purposes. I tend to agree.  </p>
<p>I think some of these sites were using CMS software yet not using them properly. You can see them having a space for META description or keywords but there was nothing in there. It was weird to look at.  </p>
<p>Sure, some of these sites could be using server log files on the backend. I&#39;ve found server log files to be useful but they&#39;re not as accepted as Google Analytics is these days when you&#39;re discussing your site traffic. This is a decision about the social acceptability of your stats more than <a href="http://en.wikipedia.org/wiki/Web_analytics#Logfile_analysis_vs_page_tagging" rel="nofollow">a discussion about the technical merits of log file analysis vs. Javascript-based trackers</a>.  </p>
<p>We definitely agree &#8212; let&#39;s get nonprofit managers thinking more about how their sites can be managed to their mission statements and not to their egos.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Thomas</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-99227</link>
		<dc:creator>Carlos Thomas</dc:creator>
		<pubDate>Sat, 10 Jan 2009 06:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-99227</guid>
		<description>Allan, I read the link you posted about Google and keywords. This does not talk about the META tag at all, but seems to discuss the use of keywords within your page. I would not fault any site for not using the keyword META tag. The description tag is generally a good idea because Google uses the content from this tag in the results pages. 
 
I&#039;m all for standards-compliant code, but I think it&#039;s way more important to have a decent looking website with accessible information. Everything comes down to the goals for your website. I don&#039;t think too many donors are basing donations decisions on most of the criteria you mentioned. 
 
In terms of web analytics packages, it is also possible some of these website could have server-side software doing this task. 
 
Your overall point that orgs need to think about functionality, not only form is right on. It takes more than a good design to make a website that works. And a website that works really needs to include title tags. </description>
		<content:encoded><![CDATA[<p>Allan, I read the link you posted about Google and keywords. This does not talk about the META tag at all, but seems to discuss the use of keywords within your page. I would not fault any site for not using the keyword META tag. The description tag is generally a good idea because Google uses the content from this tag in the results pages. </p>
<p>I&#039;m all for standards-compliant code, but I think it&#039;s way more important to have a decent looking website with accessible information. Everything comes down to the goals for your website. I don&#039;t think too many donors are basing donations decisions on most of the criteria you mentioned. </p>
<p>In terms of web analytics packages, it is also possible some of these website could have server-side software doing this task. </p>
<p>Your overall point that orgs need to think about functionality, not only form is right on. It takes more than a good design to make a website that works. And a website that works really needs to include title tags.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nonprofit tech blog about proper NGO websites - ben</title>
		<link>http://www.nonprofittechblog.org/top-five-ways-you-know-the-redesign-of-your-nonprofit-web-site-went-bad/comment-page-1#comment-99157</link>
		<dc:creator>Nonprofit tech blog about proper NGO websites - ben</dc:creator>
		<pubDate>Tue, 06 Jan 2009 20:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.nonprofittechblog.org/?p=3704#comment-99157</guid>
		<description>[...] some small things, standards for web design Nonprofits should bother having on their web presence. You can read the post here. And heres my comment about it: All in all, NGOs should consider using one of the plenty available [...]</description>
		<content:encoded><![CDATA[<p>[...] some small things, standards for web design Nonprofits should bother having on their web presence. You can read the post here. And heres my comment about it: All in all, NGOs should consider using one of the plenty available [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
