<?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/"
		>
<channel>
	<title>Comments on: Site review: Stonebriar Community Church</title>
	<atom:link href="http://www.mickmel.com/blog/200701/site-review-stonebriar-community-church/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mickmel.com/blog/200701/site-review-stonebriar-community-church/</link>
	<description>Church marketing, SEO and social media.</description>
	<lastBuildDate>Wed, 08 Sep 2010 02:53:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Adam Atwood</title>
		<link>http://www.mickmel.com/blog/200701/site-review-stonebriar-community-church/comment-page-1/#comment-673</link>
		<dc:creator>Adam Atwood</dc:creator>
		<pubDate>Sun, 22 Nov 2009 17:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.churchwebsitehelp.com/20070119/site-review-stonebriar-community-church/#comment-673</guid>
		<description>Jason,
I&#039;m in the business. I am very impressed with the current website, I&#039;m also a member at the Church. Who designed the site? What web design company? It&#039;s really good work, and I&#039;m always looking for good web design partners for my clients.
thanks,
Adam
adam@kilmanatwood.com</description>
		<content:encoded><![CDATA[<p>Jason,<br />
I&#8217;m in the business. I am very impressed with the current website, I&#8217;m also a member at the Church. Who designed the site? What web design company? It&#8217;s really good work, and I&#8217;m always looking for good web design partners for my clients.<br />
thanks,<br />
Adam<br />
<a href="mailto:adam@kilmanatwood.com">adam@kilmanatwood.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Reynolds</title>
		<link>http://www.mickmel.com/blog/200701/site-review-stonebriar-community-church/comment-page-1/#comment-672</link>
		<dc:creator>Jason Reynolds</dc:creator>
		<pubDate>Tue, 31 Jul 2007 23:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.churchwebsitehelp.com/20070119/site-review-stonebriar-community-church/#comment-672</guid>
		<description>Mickey, have you looked at us lately? We are in much better shape. Would love to get your comments on the new site.</description>
		<content:encoded><![CDATA[<p>Mickey, have you looked at us lately? We are in much better shape. Would love to get your comments on the new site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mickey</title>
		<link>http://www.mickmel.com/blog/200701/site-review-stonebriar-community-church/comment-page-1/#comment-671</link>
		<dc:creator>Mickey</dc:creator>
		<pubDate>Fri, 19 Jan 2007 19:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.churchwebsitehelp.com/20070119/site-review-stonebriar-community-church/#comment-671</guid>
		<description>I thought maybe the IE7 thing was just a glitch on my work PC, but it&#039;s doing the same thing to me at home.

Overall, I live the experiencestonebriar site, and I agree with your thoughts behind it.  I was simply trying to be as critical as possible.

I tend to put the church name first so that it&#039;ll show up easier in user&#039;s toolbar and bookmarks.  In both of those cases, you often get 20 characters followed by &quot;...&quot;.  If you have &quot;Vacation Bible Schoo...&quot; in your bookmarks, you have no idea where it&#039;s from.  On the other hand, the text at the beginning is thought to have more SEO weight, so doing it in the order that you suggest certainly could be the way to go.

I can relate to your problems with old content.  We have a similar system set-up with our site, but I&#039;m sure you can find outdated content somewhere.  That was more of a &quot;here&#039;s an old page to fix&quot; comment, rather than pointing out an overall flaw.  Come to think of it, I don&#039;t recall seeing ANY other outdated info.  The &quot;find a problem with this page&quot; could be good, especially since you already have the email/print buttons on every page.

The keyword idea is great!  I was very proud of the search engine on our church site until you mentioned that - now I need to go fix it! :)</description>
		<content:encoded><![CDATA[<p>I thought maybe the IE7 thing was just a glitch on my work PC, but it&#8217;s doing the same thing to me at home.</p>
<p>Overall, I live the experiencestonebriar site, and I agree with your thoughts behind it.  I was simply trying to be as critical as possible.</p>
<p>I tend to put the church name first so that it&#8217;ll show up easier in user&#8217;s toolbar and bookmarks.  In both of those cases, you often get 20 characters followed by &#8220;&#8230;&#8221;.  If you have &#8220;Vacation Bible Schoo&#8230;&#8221; in your bookmarks, you have no idea where it&#8217;s from.  On the other hand, the text at the beginning is thought to have more SEO weight, so doing it in the order that you suggest certainly could be the way to go.</p>
<p>I can relate to your problems with old content.  We have a similar system set-up with our site, but I&#8217;m sure you can find outdated content somewhere.  That was more of a &#8220;here&#8217;s an old page to fix&#8221; comment, rather than pointing out an overall flaw.  Come to think of it, I don&#8217;t recall seeing ANY other outdated info.  The &#8220;find a problem with this page&#8221; could be good, especially since you already have the email/print buttons on every page.</p>
<p>The keyword idea is great!  I was very proud of the search engine on our church site until you mentioned that &#8211; now I need to go fix it! <img src='http://www.mickmel.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Reynolds</title>
		<link>http://www.mickmel.com/blog/200701/site-review-stonebriar-community-church/comment-page-1/#comment-670</link>
		<dc:creator>Jason Reynolds</dc:creator>
		<pubDate>Fri, 19 Jan 2007 18:32:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.churchwebsitehelp.com/20070119/site-review-stonebriar-community-church/#comment-670</guid>
		<description>Thanks for the review, it was very helpful. We are in the middle of a complete overhaul of our site (it is three years old), so we will be sure and take a hard look at the things you point out.

Some responses:
I am not seeing the IE nav problem you are seeing, but the text resize thing is obviously not working. It worked when we implemented it, but some tweaks must have interfered.

The link from the main image on our home page actually takes you to a second site, our welcome site. You can find it at http://experiencestonebriar.org The idea with that site was to provide a place we could point people who are not members/attendees of our church to get familiar with Stonebriar. So on mail pieces, we would include that URL instead of our main site. At the time, this was because we had more visitors than we could handle (we literally had 3-400 new adults every week), so attracting folks from search engines was not a priority (thus the use of flash). So there is some history for you. I agree that the lack of a prominent link back to our main site was an egregious error. At the time we thought it was a good idea.

As for mod_rewrite, we do have human readable urls, but the old urls still work also. The experience site was linking to the old URL and once you have linked in the CMS dynamically keeps generating the messy URLs.

Your suggestion for title tags is solid, though I would move the last part to the front, as I read recently presenting different content in that area for every page is classic SEO... though you obviously still want the other information you suggested. Dashes are nice too, I agree.

Your comment about the newsletter site being old is quite funny, actually. It is the same design, just a different color and different front-end coding. We used tables and other font designation methods because it is the only way to get all email clients to receive the mail. Now, if you are referring to the newsletter archive page, that is being generated dynamically and we never went back to style it. Looks horrible.

The staff section is being generated dynamically and the variables are put into the URL. We have not yet figured out how to rewrite those urls unfortunately.

Our content creators are supposed to use the function in our CMS that takes content offline on certain dates. The VBS page you found should have been offline after the event. I am sure there are places all over our 400+ pages that are like that. Tough call in deciding if you unleash your ministries to contribute content or if you hold the reigns tight and play the gatekeeper. We have decided to let open the flood gates and deal with the problems as they come up, but we need a better method for finding outdated content. Some discussion has been brought up about putting a &quot;Find a problem with this page?&quot; link that would allow surfers to report the problem.

Thanks for the Kudos as well! The site was a great learning opportunity for us and our new site coming out in April should not repeat these mistakes (though we will have others).

Oh, one other thing we created that I think more churches should try to do is our equivalent of AOL Keywords. For instance, type &quot;Mission India&quot; or &quot;missionindia&quot; into our search engine and you are taken straight away to http://www.stonebriar.org/expression/missions/mission-india/ . However, if you type &quot;india&quot; you are presented search results. Any time there is a one for one match between a search term and page/section then we create a reference that takes them there. This also allows us to have print pieces which reference &quot;Stonebriar.org &quot;Keyword: Giving&quot;, etc.

Thanks again for the review!</description>
		<content:encoded><![CDATA[<p>Thanks for the review, it was very helpful. We are in the middle of a complete overhaul of our site (it is three years old), so we will be sure and take a hard look at the things you point out.</p>
<p>Some responses:<br />
I am not seeing the IE nav problem you are seeing, but the text resize thing is obviously not working. It worked when we implemented it, but some tweaks must have interfered.</p>
<p>The link from the main image on our home page actually takes you to a second site, our welcome site. You can find it at <a href="http://experiencestonebriar.org" rel="nofollow">http://experiencestonebriar.org</a> The idea with that site was to provide a place we could point people who are not members/attendees of our church to get familiar with Stonebriar. So on mail pieces, we would include that URL instead of our main site. At the time, this was because we had more visitors than we could handle (we literally had 3-400 new adults every week), so attracting folks from search engines was not a priority (thus the use of flash). So there is some history for you. I agree that the lack of a prominent link back to our main site was an egregious error. At the time we thought it was a good idea.</p>
<p>As for mod_rewrite, we do have human readable urls, but the old urls still work also. The experience site was linking to the old URL and once you have linked in the CMS dynamically keeps generating the messy URLs.</p>
<p>Your suggestion for title tags is solid, though I would move the last part to the front, as I read recently presenting different content in that area for every page is classic SEO&#8230; though you obviously still want the other information you suggested. Dashes are nice too, I agree.</p>
<p>Your comment about the newsletter site being old is quite funny, actually. It is the same design, just a different color and different front-end coding. We used tables and other font designation methods because it is the only way to get all email clients to receive the mail. Now, if you are referring to the newsletter archive page, that is being generated dynamically and we never went back to style it. Looks horrible.</p>
<p>The staff section is being generated dynamically and the variables are put into the URL. We have not yet figured out how to rewrite those urls unfortunately.</p>
<p>Our content creators are supposed to use the function in our CMS that takes content offline on certain dates. The VBS page you found should have been offline after the event. I am sure there are places all over our 400+ pages that are like that. Tough call in deciding if you unleash your ministries to contribute content or if you hold the reigns tight and play the gatekeeper. We have decided to let open the flood gates and deal with the problems as they come up, but we need a better method for finding outdated content. Some discussion has been brought up about putting a &#8220;Find a problem with this page?&#8221; link that would allow surfers to report the problem.</p>
<p>Thanks for the Kudos as well! The site was a great learning opportunity for us and our new site coming out in April should not repeat these mistakes (though we will have others).</p>
<p>Oh, one other thing we created that I think more churches should try to do is our equivalent of AOL Keywords. For instance, type &#8220;Mission India&#8221; or &#8220;missionindia&#8221; into our search engine and you are taken straight away to <a href="http://www.stonebriar.org/expression/missions/mission-india/" rel="nofollow">http://www.stonebriar.org/expression/missions/mission-india/</a> . However, if you type &#8220;india&#8221; you are presented search results. Any time there is a one for one match between a search term and page/section then we create a reference that takes them there. This also allows us to have print pieces which reference &#8220;Stonebriar.org &#8220;Keyword: Giving&#8221;, etc.</p>
<p>Thanks again for the review!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
