<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <channel>
    
    <title>Boyink! Blog</title>
    <link>http://www.boyink.com/splaat/weblog/</link>
    <description>Mostly web stuff from Michael Boyink of Boyink Interactive</description>
    <dc:language>en</dc:language>
    <dc:creator>pmachine@boyink.com</dc:creator>
    <dc:rights>Copyright 2008</dc:rights>
    <dc:date>2008-05-15T13:10:00-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.pmachine.com/" />
    

    <item>
      <title>Fear Behind Namby&#45;Pamby Church Websites</title>
      <link>http://www.boyink.com/splaat/comments/fear-drives-behind-namby-pamby-church-websites/</link>
      <guid>http://www.boyink.com/splaat/comments/fear-drives-behind-namby-pamby-church-websites/#When:14:07:00Z</guid>
      <description><![CDATA[<p>How&#8217;s that for an attention-grabbing headline?&nbsp; Mostly I just wanted to use the phrase namby-pamby to see what kind of search traffic it&#8217;ll bring&#8230;
</p>
<p>
Here&#8217;s what&#8217;s on my mind today - and this is inspired by <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fgodbit.com%2Fforum%2Fviewtopic.php%3Fid%3D2571">this thread</a> over at <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.godbit.com">Godbit</a> which is around the issue of, on a church site, having a member blogroll - a list of links to the blogs published by members of the church.&nbsp; The main issue is around the content of those blogs and how they might or might not reflect well on the church, and what the church might do to mitigate any potential damage through the use of link agreements, positioning statements, review committees, moderators, having the blogroll be located seperately from the main site, etc.
</p>
<p>
It&#8217;s distressing to me, and I think the overall terrible state of church websites can be  - partially at least - traced to some of these issues.
</p><p>It&#8217;s funny - I don&#8217;t consider myself a rebel, a revolutionary, or a renegade.&nbsp; I&#8217;m just a guy in flip-flops, living in a small ranch house in a conservative community, driving a station wagon, and trying to keep the bills paid.&nbsp; But this discussion, the ideas being proposed, and the out and out <i>fear</i> behind some of them really surprises me.&nbsp; That it&#8217;s coming from a group of fellow tech and web-heads is also a surprise.&nbsp; I&#8217;ve been involved in similar discussions with less-tech-savvy pastors and church staff and hearing these concerns from that group is no big surprise.&nbsp; The web is completely and fundamentally changing how we connect and interact with each other and some of those changes are diametrically oppposed to how the church has traditionally functioned.
</p>
<p>
Here, in no particular order, are some of the fears I&#8217;m hearing and my reactions to them.&nbsp; I apologize if they aren&#8217;t quite well-ordered or are repetitive.&nbsp; This is one of those posts that I need to get out so I can move on to the work I really should be doing&#8230;
</p>
<p>
Your members <i>are</i> doing bad things while not in church (and even while in church).&nbsp; It&#8217;s called sin, and we are all born sinners.&nbsp; Since I didn&#8217;t see the notion of using blogs and comments to correct, uplift, or support each other I can only assume the real concern here is protecting and controlling the public image of the church.
</p>
<p>
There&#8217;s a subtle  - yet persistent in all of this discussion - distinction between &#8220;the church&#8221; and &#8220;church members&#8221;.&nbsp;  &#8220;The church&#8221; has an image, &#8220;The church&#8221; can have official or unofficial support of something, etc.&nbsp; I don&#8217;t see that distinction.&nbsp; The church members ARE the church - even our kids know this because we teach it to them in Sunday School.&nbsp; Any time a church building is destroyed by fire you read about the pastor and members saying it was &#8220;just a building&#8221; and &#8220;the church lives on because it&#8217;s people live on&#8221;.&nbsp; 
</p>
<p>
I see no way you could post a disclaimer on a church website blogroll saying &#8220;the views presented in these blogs may not represent that of the church&#8221; - because those bloggers <i>are</i> the church.&nbsp; Their views may disagree with the views of other parts of the church - but that&#8217;s OK because it&#8217;s the truth.&nbsp; I think we need to get over this notion of a church needing to always present a unified front on everything.&nbsp; It&#8217;s just not always true, and trying to hide the fact that it isn&#8217;t always true makes us hypocrites.
</p>
<p>
The internet, blogs, and discussion forums aren&#8217;t allowing any new &#8220;bad things&#8221; to happen.&nbsp; People are sinning, people are disagreeing with the church teaching and people are saying bad things about the church now.&nbsp; Yes&#8212;right now at work, at a coffee shop, at a small group meeting, on the phone or in email.&nbsp; Keeping it off the website doesn&#8217;t make it go away. In short - you have no control over your church image.&nbsp; None.&nbsp; You may think you do, but it&#8217;s a facade of control.
</p>
<p>
Along these lines, I don&#8217;t agree with the idea that a church shouldn&#8217;t set up a means for open conversation (and yes, disagreement) for it&#8217;s members. Disagreement with teaching by leadership should not be discouraged or hidden.&nbsp; When we do so we are hypocrites - with our happy faces on, smiling for the visitors, pretending all is cool.&nbsp; And - sometimes leaders are just flat-out wrong and need to be corrected.
</p>
<p>
Look - the conversation is happening anyway, it&#8217;s more of a decision to be part of it or not, and to be able to provide (on the part of a pastor) direct input, teaching, and correction to the conversation.&nbsp; I think if more churches don&#8217;t start doing this they will quickly find themselves set aside, outmoded, and irrelevant (and isn&#8217;t that - being relevant - what so many churches are after these days?).
</p>
<p>
I just have to wonder - what&#8217;s the real fear here?&nbsp; If the image of the church is tarnished (and is the the big C or little c church we&#8217;re concerned for) - then what?&nbsp; Fewer people come, donations shrink, and staff members have to be let go?&nbsp; We lose the church building?&nbsp; Why is our primary concern for the church image rather than our effectiveness at the task the church was charged with?&nbsp; Why do we what-if all the negatives but not what-if the positives?
</p>
<p>
What could (or would) your church do if it had nothing to lose?&nbsp; No building, no staff, no &#8220;image&#8221;, no worldly possession of any sort?&nbsp; If it&#8217;s different than what you&#8217;re doing now, should it be?
</p>
<p>
I think the church <i>has</i> to go down these paths.&nbsp; We&#8217;ve got to get comfortable with providing places for open and public discussion.&nbsp; We&#8217;ve got to realize that the internet is going to prevent the traditional heirarchies of power and knowledge from being the norm going forward.&nbsp; We&#8217;ve got to get over the impulse to control, and spin, and hide our people.&nbsp; We&#8217;ve got to realize that people will find a place to have their say - and the internet gives them an unlimited audience regardless if we like it or not.&nbsp; 
</p>
<p>
Recommended reading:
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.boyink.com%2Fsplaat%2Fcomments%2Fthe-cluetrain-manifesto-for-churches%2F">The Cluetrain Manifesto for Churches</a>
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.boyink.com%2Fsplaat%2Fcomments%2Fweb-sites-are-easy%2F">Church Web Sites Are Easy</a>
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Furl%3Fsa%3Dt%26ct%3Dres%26cd%3D1%26url%3Dhttp%253A%252F%252Fdjchuang.googlepages.com%252FWeKnowMoreThanOurPastors.pdf%26ei%3D6YafRqnNNY2ajgH3zayADA%26usg%3DAFQjCNEN02wG-quk5qJEvUGNRcKjCH280Q%26sig2%3DVbdU2zlbgu6ggJdn3VWvOw">We Know More Than Our Pastors</a> (PDF) by Tim Bednar
</p>
<p>

</p>]]></description>
      <dc:subject>the&#45;church&#45;online</dc:subject>
      <dc:date>2007-07-19T14:07:00-05:00</dc:date>
    </item>

    <item>
      <title>I Don&#8217;t Care About Your Pretty Building</title>
      <link>http://www.boyink.com/splaat/comments/i-dont-care-about-your-pretty-building/</link>
      <guid>http://www.boyink.com/splaat/comments/i-dont-care-about-your-pretty-building/#When:14:27:00Z</guid>
      <description><![CDATA[<p>I read about another church website launching this week.&nbsp; When I read these announcements I&#8217;m always a bit uncertain if I should go look at the new site.&nbsp; I&#8217;ve been extremely critical about church sites in the past, and swore off of commenting on them&#8212;choosing instead to try to lead by example and create <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.storiesaboutgod.org">a site</a> that demonstrated what I felt was lacking in many church sites.
</p>
<p>
But today I clicked before thinking, went to the new church site, and immediately found myself groaning and shaking my head.&nbsp; Why are we - as the &#8220;online church&#8221; still making the same mistakes that we were making 6, 7 or 8 years ago when building the very first websites for churches?
</p><p>That mistake?&nbsp; Making the most prominent element on the page <b>a picture of the church building</b>.&nbsp; I just don&#8217;t get it.&nbsp; Do we think people choose a church by architectural style?&nbsp; By quality of paint job?&nbsp; By the color of it&#8217;s shingles?&nbsp; The fact that it has a star on top of it&#8217;s steeple?
</p>
<p>
I&#8217;d bet you a fiver if I went to that specific church, walked in the door and asked the pastor, a staff member, or any 5 year old in a Sunday School class to &#8220;tell me what the church is&#8221; they would say with reverence - &#8220;Oh, the church is really the people.&nbsp; The people make it what it is.&nbsp; Without the people it&#8217;s just a building.&#8221;  
</p>
<p>
So where does that thinking go when it comes to designing what - arguably - represents the &#8220;most public face&#8221; of the church?&nbsp;  Why do we suddenly choose pictures of the building as our first impression?&nbsp; It makes me wonder if we <b>truly</b> believe what we say about what the church is.
</p>
<p>
Your visitors may wonder the same thing....
<br />

</p>]]></description>
      <dc:subject>web&#45;implementation, the&#45;church&#45;online</dc:subject>
      <dc:date>2007-03-03T14:27:00-05:00</dc:date>
    </item>

    <item>
      <title>Churches: Stop PDF&#45;ing!</title>
      <link>http://www.boyink.com/splaat/comments/churches-stop-pdf-ing/</link>
      <guid>http://www.boyink.com/splaat/comments/churches-stop-pdf-ing/#When:21:00:00Z</guid>
      <description><![CDATA[<p>OK, so I&#8217;m making up words.&nbsp; Or, <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26lr%3D%26safe%3Doff%26q%3Dpdfing%26btnG%3DSearch">maybe I&#8217;m not</a>.
</p>
<p>
In any case, today&#8217;s message is for churches to stop using the web simply as a online distribution channel for printed items like bulletins and newsletters.
</p>
<p>
I&#8217;ll say that again. In another way, just for the sake of entertainment.&nbsp; If you think your church website is finally &#8220;up to date&#8221; because you just uploaded a PDF version of this month&#8217;s church newsletter, you are mistaken.
</p><p>The issues around PDF web content have <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.useit.com%2Falertbox%2F20030714.html">long</a> been <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.webpagesthatsuck.com%2Fpdf.html">noted</a>, so I don&#8217;t intend this post as a general comment around PDF usage - but more specifically for churches.
</p>
<p>
So why not keep a church website up to date by simply posting PDF versions of the bulletins and newsletters that you&#8217;re already producing?
</p>
<p>
Because overall it shows a misunderstanding of the web - just as in the early days of television most content was repurposed radio dramas  because people just didn&#8217;t see how TV brought new capabilities to exploit.&nbsp; 
</p>
<p>
Specifically, by putting that newsletter and bulletin on your site as web content rather than PDF a church can gain:<ul><li><b>A more flexible and responsive publishing schedule</b><br/>Aren&#8217;t you tired of sounding the &#8220;deadline drumbeat&#8221;?&nbsp; Or staying late on deadline day because *everything* comes in last minute?&nbsp; Or making exceptions for people because of their position in the church?&nbsp; Your website can be updated any time - no deadlines required.&nbsp; Last minute news item?&nbsp; No problem. Finally,  a communications medium that can dance to the beat of the content, rather than the other way around.</li><li><b>Readers on alternate devices</b><br/>I was at a holiday get-together with some other folks from my church this past week.&nbsp; The discussion turned to some content on the church website, and one guy said &#8220;Oh I gotta go read that&#8221;.&nbsp; He pulled out his wireless-enabled cell phone and within 15 seconds or so was reading the content - all possible because it was web content and not something captured in a PDF.&nbsp; And take note, this was no 18 year old geek.&nbsp; This was a police sergeant, a married father of 3 with one kid out of high school.</li><li><b>Readers on slow connections</b><br/>As part of another church engagement last week I talked with a number of the church members.&nbsp; A high percentage were still using dialup connections, and mentioned that they had issues trying to load PDF content.&nbsp; Regardless of how you feel about PDF&#8217;s, the truth is they are another layer of technology, another application that has to load, and why? So the user can see text and images - just like in the browser.&nbsp; What if that PDF content was the critical piece, the &#8220;last straw&#8221; for a visitor in making a decision to visit the church.&nbsp; Or - to cross the line and come to Christ?&nbsp; Why take the risk?</li><li><b>More readers using assitive devices</b><br/>Yes, PDF&#8217;s <i>can</i> be made accessible (readable by people using assistive devices on their computer such as a screen reader, but frankly it takes more work so they are less likely to be.&nbsp; Web content is much more likely to be readable by these devices.</li><li><b>Better searchability</b><br/>Yes, Google can index PDF files - but what if you don&#8217;t use Google?</li><li><b>Visitors</b><br/>Yeah, OK - maybe this is mostly me, but when I see the church website used mainly as a PDF repository I know this a church that&#8217;s behind the times and just doesn&#8217;t &#8220;get&#8221; the web.&nbsp; And if they don&#8217;t get the web, they&#8217;re unlikely to see me darken their door.&nbsp; What if it&#8217;s not just me?</ul></p>]]></description>
      <dc:subject>the&#45;church&#45;online</dc:subject>
      <dc:date>2006-12-18T21:00:00-05:00</dc:date>
    </item>

    <item>
      <title>The ClueTrain Manifesto for Churches?</title>
      <link>http://www.boyink.com/splaat/comments/the-cluetrain-manifesto-for-churches/</link>
      <guid>http://www.boyink.com/splaat/comments/the-cluetrain-manifesto-for-churches/#When:16:07:00Z</guid>
      <description><![CDATA[<p>These markets are conversations.&nbsp; Are churches?
</p><p>The <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.cluetrain.com">Cluetrain Manifesto</a> seeks to tell traditional businesses how the internet is changing the markets they play in.&nbsp; 
</p>
<p>
In the midst of launching a website for a church that seems to be striking some of the same chords, I was curious to see how the Cluetrain&#8217;s <i>95 Thesis</i> would read if I substituted &#8220;Church&#8221; (as in the &#8220;business&#8221; side of a Church, the staff, etc - not in the sense that the congregation is the Church) in place of &#8220;company&#8221;, and &#8220;congregation&#8221; for &#8220;market&#8221;.&nbsp; It&#8217;s a thought-provoker - not a straight carryover in all cases but some of the translated thesis do give pause. 
</p>
<p>
So with apologies to the creators of the original Cluetrain, here&#8217;s the &#8220;Church Cluetrain&#8221;:
</p>
<p><b>Online Congregations...</b>
</p>
<p>
Networked congregations are beginning to self-organize faster than the Churches that have traditionally served them. Thanks to the web, congregations are becoming better informed, smarter, and more demanding of qualities missing from most Churches. 
</p>
<p>
<b>95 Theses</b>
</p>
<p>
1.	Congregations are conversations. 
</p>
<p>
2.	Congregations consist of human beings, not butts in seats. 
</p>
<p>
3.	Conversations among human beings sound human. They are conducted in a human voice. 
</p>
<p>
4.	Whether delivering information, opinions, perspectives, dissenting arguments or humorous asides, the human voice is typically open, natural, uncontrived. 
</p>
<p>
5.	People recognize each other as such from the sound of this voice. 
</p>
<p>
6.	The Internet is enabling conversations among human beings that were simply not possible in the era of mass media. 
</p>
<p>
7.	Hyperlinks subvert hierarchy. 
</p>
<p>
8.	In both internetworked congregations and among intranetworked employees, people are speaking to each other in a powerful new way. 
</p>
<p>
9.	These networked conversations are enabling powerful new forms of social organization and knowledge exchange to emerge. 
</p>
<p>
10.	As a result, congregations are getting smarter, more informed, more organized. Participation in a networked congregation changes people fundamentally. 
</p>
<p>
11.	People in networked congregations have figured out that they get far better information and support from one another than from church staff and leaders. So much for Church rhetoric about community. 
</p>
<p>
12.	There are no secrets. The networked congregation knows more than Churches do about their own communities. And whether the news is good or bad, they tell everyone. 
</p>
<p>
13.	What&#8217;s happening to congregations is also happening among employees. A metaphysical construct called &#8220;The Church&#8221; is the only thing standing between the two. 
</p>
<p>
14.	Churches do not speak in the same voice as these new networked conversations. To their intended online audiences, Churches sound hollow, flat, literally inhuman. 
</p>
<p>
15.	In just a few more years, the current homogenized &#8220;voice&#8221; of church�the sound of mission statements and brochures�will seem as contrived and artificial as the language of the 18th century French court. 
</p>
<p>
16.	Already, Churches that speak in the language of the pitch, the dog-and-pony show, are no longer speaking to anyone. 
</p>
<p>
17.	Churches that assume online congregations are the same congregations that used to sit in the pew on Sunday are kidding themselves. 
</p>
<p>
18.	Churches that don&#8217;t realize their congregations are now networked person-to-person, getting smarter as a result and deeply joined in conversation are missing their best opportunity. 
</p>
<p>
19.	Churches can now communicate with their congregations directly. If they blow it, it could be their last chance. 
</p>
<p>
20.	Churches need to realize their congregations are often laughing. At them. 
</p>
<p>
21.	Churches need to lighten up and take themselves less seriously. They need to get a sense of humor. 
</p>
<p>
22.	Getting a sense of humor does not mean putting some jokes on the church web site. Rather, it requires big values, a little humility, straight talk, and a genuine point of view. 
</p>
<p>
23.	Churches attempting to &#8220;position&#8221; themselves need to take a position. Optimally, it should relate to something their congregation actually cares about. 
</p>
<p>
24.	Bombastic boasts�"We are positioned to become the preeminent provider of XYZ"�do not constitute a position. 
</p>
<p>
25.	Churches need to come down from their Ivory Towers and talk to the people with whom they hope to create relationships. 
</p>
<p>
26.	Public Relations does not relate to the public. Churches are deeply afraid of their congregations. 
</p>
<p>
27.	By speaking in language that is distant, uninviting, arrogant, they build walls to keep congregations at bay. 
</p>
<p>
28.	Most outreach programs are based on the fear that the the &#8220;unsaved&#8221; might see what&#8217;s really going on inside the church. 
</p>
<p>
29.	Elvis said it best: &#8220;We can&#8217;t go on together with suspicious minds.&#8221; 
</p>
<p>
30.	Church loyalty is the denomination&#8217;s version of going steady, but the breakup is inevitable�and coming fast. Because they are networked, smart congregations are able to renegotiate relationships with blinding speed. 
</p>
<p>
31.	Networked congregations can change churches overnight. Networked knowledge workers can change employers over lunch. Your own &#8220;downsizing initiatives&#8221; taught us to ask the question: &#8220;Loyalty? What&#8217;s that?&#8221; 
</p>
<p>
32.	Smart congregations will find churches who speak their own language. 
</p>
<p>
33.	Learning to speak with a human voice is not a parlor trick. It can&#8217;t be &#8220;picked up&#8221; at some tony conference. 
</p>
<p>
34.	To speak with a human voice, churches must share the concerns of their communities. 
</p>
<p>
35.	But first, they must belong to a community. 
</p>
<p>
36.	Churches must ask themselves where their corporate cultures end. 
</p>
<p>
37.	If their cultures end before the community begins, they will have no congregation. 
</p>
<p>
38.	Human communities are based on discourse�on human speech about human concerns. 
</p>
<p>
39.	The community of discourse is the congregation. 
</p>
<p>
40.	Churches that do not belong to a community of discourse will die. 
</p>
<p>
41.	Churches make a religion of security, but this is largely a red herring. Most are protecting less against competitors than against their own congregation and staff. 
</p>
<p>
42.	As with networked congregations, people are also talking to each other directly inside the Church�and not just about rules and regulations, boardroom directives, bottom lines. 
</p>
<p>
43.	Such conversations are taking place today on church intranets. But only when the conditions are right. 
</p>
<p>
44.	Churches typically install intranets top-down to distribute HR policies and other corporate information that workers are doing their best to ignore. 
</p>
<p>
45.	Intranets naturally tend to route around boredom. The best are built bottom-up by engaged individuals cooperating to construct something far more valuable: an intranetworked church-wide conversation. 
</p>
<p>
46.	A healthy intranet organizes workers in many meanings of the word. Its effect is more radical than the agenda of any union. 
</p>
<p>
47.	While this scares Churches witless, they also depend heavily on open intranets to generate and share critical knowledge. They need to resist the urge to &#8220;improve&#8221; or control these networked conversations. 
</p>
<p>
48.	When Church intranets are not constrained by fear and legalistic rules, the type of conversation they encourage sounds remarkably like the conversation of the networked marketplace. 
</p>
<p>
49.	Org charts worked in an older economy where plans could be fully understood from atop steep management pyramids and detailed work orders could be handed down from on high. 
</p>
<p>
50.	Today, the org chart is hyperlinked, not hierarchical. Respect for hands-on knowledge wins over respect for abstract authority. 
</p>
<p>
51.	Command-and-control management styles both derive from and reinforce bureaucracy, power tripping and an overall culture of paranoia. 
</p>
<p>
52.	Paranoia kills conversation. That&#8217;s its point. But lack of open conversation kills Churches. 
</p>
<p>
53.	There are two conversations going on. One inside the Church. One with the congregation. 
</p>
<p>
54.	In most cases, neither conversation is going very well. Almost invariably, the cause of failure can be traced to obsolete notions of command and control. 
</p>
<p>
55.	As policy, these notions are poisonous. As tools, they are broken. Command and control are met with hostility by intranetworked knowledge workers and generate distrust in internetworked congregations. 
</p>
<p>
56.	These two conversations want to talk to each other. They are speaking the same language. They recognize each other&#8217;s voices. 
</p>
<p>
57.	Smart Churches will get out of the way and help the inevitable to happen sooner. 
</p>
<p>
58.	If willingness to get out of the way is taken as a measure of IQ, then very few Churches have yet wised up. 
</p>
<p>
59.	However subliminally at the moment, millions of people now online perceive Churches as little more than quaint legal fictions that are actively preventing these conversations from intersecting. 
</p>
<p>
60.	This is suicidal. Congregations want to talk to Churches. 
</p>
<p>
61.	Sadly, the part of the Church a networked market wants to talk to is usually hidden behind a smokescreen of hucksterism, of language that rings false�and often is. 
</p>
<p>
62.	Congregations do not want to talk to flacks and hucksters. They want to participate in the conversations going on behind the church firewall. 
</p>
<p>
63.	De-cloaking, getting personal: We are those congregations. We want to talk to you. 
</p>
<p>
64.	We want access to your church information, to your plans and strategies, your best thinking, your genuine knowledge. We will not settle for the 4-color brochure, for web sites chock-a-block with eye candy but lacking any substance. 
</p>
<p>
65.	We&#8217;re also the workers who make your churches go. We want to talk to seekers directly in our own voices, not in platitudes written into a script. 
</p>
<p>
66.	As congregations, as workers, both of us are sick to death of getting our information by remote control. Why do we need faceless bulletins and newsletters to introduce us to each other? 
</p>
<p>
67.	As congregations, as workers, we wonder why you&#8217;re not listening. You seem to be speaking a different language. 
</p>
<p>
68.	The inflated self-important jargon you sling around�in the meetings, at your services�what&#8217;s that got to do with us? 
</p>
<p>
69.	Maybe you&#8217;re impressing your big givers. Maybe you&#8217;re impressing other church leaders. You&#8217;re not impressing us. 
</p>
<p>
70.	If you don&#8217;t impress us, your staff and programs are going to take a bath. Don&#8217;t they understand this? If they did, they wouldn&#8217;t let you talk that way. 
</p>
<p>
71.	Your tired notions of &#8220;the congregations&#8221; make our eyes glaze over. We don&#8217;t recognize ourselves in your projections�perhaps because we know we&#8217;re already elsewhere. 
</p>
<p>
72.	We like this new marketplace much better. In fact, we are creating it. 
</p>
<p>
73.	You&#8217;re invited, but it&#8217;s our world. Take your shoes off at the door. If you want to barter with us, get down off that camel! 
</p>
<p>
74.	We are immune to advertising. Just forget it. 
</p>
<p>
75.	If you want us to talk to you, tell us something. Make it something interesting for a change. 
</p>
<p>
76.	We&#8217;ve got some ideas for you too: some new tools we need, some better service. Stuff we&#8217;d be willing to volunteer for. Got a minute? 
</p>
<p>
77.	You&#8217;re too busy &#8220;doing church&#8221; to answer our email? Oh gosh, sorry, gee, we&#8217;ll come back later. Maybe. 
</p>
<p>
78.	You want us to pay? We want you to pay attention. 
</p>
<p>
79.	We want you to drop your trip, come out of your neurotic self-involvement, join the party. 
</p>
<p>
80.	Don&#8217;t worry, you can still pass the collection plate. That is, as long as it&#8217;s not the only thing on your mind. 
</p>
<p>
81.	Have you noticed that, in itself, money is kind of one-dimensional and boring? What else can we talk about? 
</p>
<p>
82.	Your product broke. Why? We&#8217;d like to ask the guy who made it. Your corporate strategy makes no sense. We&#8217;d like to have a chat with your CEO. What do you mean she&#8217;s not in? 
</p>
<p>
83.	We want you to take 50 million of us as seriously as you take one reporter from Christianity Today. 
</p>
<p>
84.	We know some people from your church. They&#8217;re pretty cool online. Do you have any more like that you&#8217;re hiding? Can they come out and play? 
</p>
<p>
85.	When we have questions we turn to each other for answers. If you didn&#8217;t have such a tight rein on &#8220;your people&#8221; maybe they&#8217;d be among the people we&#8217;d turn to. 
</p>
<p>
86.	When we&#8217;re not busy being your &#8220;target market,&#8221; many of us are your people. We&#8217;d rather be talking to friends online than watching the service. That would get your name around better than your entire mission strategy. But you tell us speaking to the congregation is the Pastor&#8217;s job. 
</p>
<p>
87.	We&#8217;d like it if you got what&#8217;s going on here. That&#8217;d be real nice. But it would be a big mistake to think we&#8217;re holding our breath. 
</p>
<p>
88.	We have better things to do than worry about whether you&#8217;ll change in time to get our business. Business is only a part of our lives. It seems to be all of yours. Think about it: who needs whom? 
</p>
<p>
89.	We have real power and we know it. If you don&#8217;t quite see the light, some other outfit will come along that&#8217;s more attentive, more interesting, more fun to play with. 
</p>
<p>
90.	Even at its worst, our newfound conversation is more interesting than most services, more entertaining than any TV sitcom, and certainly more true-to-life than the church web sites we&#8217;ve been seeing. 
</p>
<p>
91.	Our allegiance is to ourselves�our friends, our new allies and acquaintances, even our sparring partners. Churches that have no part in this world, also have no future. 
</p>
<p>
92.	Churches are spending billions of dollars on Y2K. Why can&#8217;t they hear this market timebomb ticking? The stakes are even higher. 
</p>
<p>
93.	We&#8217;re both inside Churches and outside them. The boundaries that separate our conversations look like the Berlin Wall today, but they&#8217;re really just an annoyance. We know they&#8217;re coming down. We&#8217;re going to work from both sides to take them down. 
</p>
<p>
94.	To traditional churches, networked conversations may appear confused, may sound confusing. But we are organizing faster than they are. We have better tools, more new ideas, no rules to slow us down. 
</p>
<p>
95.	We are waking up and linking to each other. We are watching. But we are not waiting.&nbsp;
</p>]]></description>
      <dc:subject>boyink&#45;articles, web&#45;strategy, the&#45;church&#45;online</dc:subject>
      <dc:date>2006-11-14T16:07:00-05:00</dc:date>
    </item>

    <item>
      <title>Web Sites Are Easy</title>
      <link>http://www.boyink.com/splaat/comments/web-sites-are-easy/</link>
      <guid>http://www.boyink.com/splaat/comments/web-sites-are-easy/#When:16:02:00Z</guid>
      <description><![CDATA[<p>An article about building church websites.&nbsp; This originally appeared as a guest column over at <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.healyourchurchwebsite.com">HealYourChurchWebsite.com</a>.
</p><p>Piece &#8216;o cake, really.
</p>
<p>
Yeah - I know. You wouldn&#8217;t think so, the way MeanDean carries on <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.healyourchurcwebsite.com">here</a>.&nbsp; With all his ranting and raving and &#8220;healing&#8221; of church websites gone bad, you might think that building a &#8220;good&#8221; church website (or any website, for that matter) is next to impossible, achievable only by <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fslashdot.org%2F">Slashdot</a> reading PDA-carrying geek who keeps a Wi-Fi enabled laptop on the bed stand for those middle-of-the-night  <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26ie%3DUTF-8%26q%3Ddream%2Bblog">dream-blogging </a>episodes.
</p>
<p>
Phooey, I say.&nbsp; Building a website that would pass even the &#8220;Mean&#8221; test is easy.
</p>
<p>Well....
</p>
<p>
Yes, qualifier time.&nbsp; Building a &#8220;good&#8221; website from a technical and presentation perspective&#8212;with a pleasing color palette, validated and accessible css-driven code, logical and well-organized navigation, proper copyright notice and privacy policy, along with any number of features like RSS feeds and daily Bible verses is easy.&nbsp; Even enabling the site to be frequently updated by technophobes by building it on a content management system is easy.&nbsp; Cheap, even.
</p>
<p>
These aspects of building a good website are easy because they&#8217;re challenges common to all websites, so those of us interested in building good church websites get a free ride on the backs of all the commercial developers out there.&nbsp; Commercial enterprise produces tools like <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.visibone.com%2Fcolorlab%2F">color choosers</a>, <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.inknoise.com%2Fexperimental%2Flayoutomatic.php">CSS-based layout generators</a>, <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.accessify.com%2Ftools-and-wizards%2Flist-o-matic%2Flist-o-matic.asp">navigation generators</a> and <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.truste.org%2Fabout%2Fmaterials_and_reports.php">privacy policy models</a>.&nbsp; If you get stuck trying to work with some of these tools, there are countless help resources on the web - <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fgroups.yahoo.com%2Fsearch%3Fquery%3Dweb%2Bdevelopment%26submit%3DSearch">mailing lists</a>, <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26ie%3DUTF-8%26q%3Dweb%2Bdevelopment%2Bdiscussion%2Bforum">discussion forums</a>, or <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26safe%3Doff%26c2coff%3D1%26q%3Dweb%2Bdevelopment%2Bblog">blogs</a> where technical issues are discussed and solved.
</p>
<p>
But, the minute you move past the technical challenges and begin to ask questions like &#8220;What should this website say?&#8221; or &#8220;What should this website *do* for the church?&#8221;, or &#8220;How will we know if the site is successful?&#8221; or &#8220;what will we put there for members vs. non members?&#8221; you are guaranteed to get blank stares, drooping jaws, and schedule delays.
</p>
<p>
Content.&nbsp; What is it about content?&nbsp; Mention the importance of having good content during the site construction process, and you&#8217;ll get immediate agreement, heads nodding, everyone knows &#8220;content is king&#8221; on the web.&nbsp; Bill Gates did, <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.microsoft.com%2Fbillgates%2Fcolumns%2F1996essay%2Fessay960103.asp">back in 1996</a>.&nbsp; <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.gerrymcgovern.com%2F">Gerry McGovern</a> has made a career out of web content - writing articles and books, and speaking to conferences and corporate customers about web content.&nbsp; Your site-team will probably have content ideas galore - the possibilities are always endless and brainstorming is fun.
</p>
<p>
So why is it then, when it comes time to post some content to the freshly-developed church web site so often church web-builders are left to &#8220;bulletin-diving&#8221; or &#8220;repurposing&#8221; content from existing newsletters or brochures?&nbsp; Why is the website so often updated reactively (if at all)? 
</p>
<p>
Gerry McGovern, in his article <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.gerrymcgovern.com%2Fnt%2F2004%2Fnt_2004_08_23_website_management.htm">Websites: easy to start, hard to manage&#8221;</a> says <blockquote>&#8220;One of the biggest problems websites face is that they lack proper planning in the design and development phase. Generally, the design of the website tends to overreach, in that what is built requires more staff to professionally manage than are available.&#8221;</p></blockquote>
<p>
I&#8217;m not convinced it&#8217;s a planning problem.&nbsp;  I&#8217;ve been involved on site projects where the planning was quite detailed, formulating content needs from audience research, then tweaking needs by factoring in the business or organizational goals and staff skill set and availability.&nbsp; But plans are just that - plans - and they&#8217;re rarely executed word for word.&nbsp; Sometimes both the plan and the site collect the same dust.
</p>
<p>
So where is the disconnect? 
</p>
<p>
I think the main issue behind poor websites&#8212;church or business&#8212;is that the people responsible for the site don&#8217;t understand that the true power of the web is storytelling.
</p>
<p>
Eh?&nbsp; Storytelling you ask?&nbsp; Shall we gather our laptops around a campfire now? Hear me out&#8230;
</p>
<p>
Curt Cloninger writes in his <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.alistapart.com"> AListApart</a> article,<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.alistapart.com%2Farticles%2Fstorytelling%2F">A Case for Web Storytelling&#8221;</a>:<blockquote>&#8220;Is the web a global network of connected computers? No, that�s the Internet. Is the web hyper text transfer protocol? Well, technically. But if the web is to be understood as a communications medium (the only useful way to understand it), then it must be more than computers talking to each other. Otherwise, mere data exchange would succeed. But the web is not a global network of connected computers. The web is a global network of connected people. And story-telling is still the most effective way to emotionally impact people.&#8221;</p></blockquote>
<p>
Cliff Allen echoes the same idea in his <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com">ClickZ</a> article <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fexperts%2Farchives%2Fmkt%2Fprecis_mkt%2Farticle.php%2F830031">Tell a Story to Engage Your Audience&#8221;</a>:<blockquote>&#8220;There are many ways to organize product information to communicate with an audience. Facts are typically grouped by such things as how a product is used, what it&#8217;s priced at, or what is known about a particular audience. However, corporate web sites have overlooked a technique that people have used for thousands of years to convey information: storytelling.&#8221;</p></blockquote>
<p>
He goes on to say:<blockquote>&#8220;It&#8217;s a little surprising that most corporate web sites don&#8217;t take advantage of this technique to capture attention and lead prospects to make a purchase or inquiry. Most corporate web sites present product information as a snapshot - saying here are all the reasons why you&#8217;ll like our product. They don&#8217;t recognize that the decision to buy is a process: A prospect becomes a customer by recognizing a problem, learning about solutions, researching products, and, finally, making the decision to purchase product A instead of product B.&#8221;</p></blockquote>
<p>
So here&#8217;s the core frustration of what&#8217;s starting to become a personal rant (sorry Dean, you did ask for something I was &#8220;passionate about&#8221;..<img src="http://www.boyink.com/images/chipper/wink.png" width="17" height="16" alt="wink" style="border:0;" />).&nbsp; In one corner, we have the church website.&nbsp; No, let&#8217;s not call it a website.&nbsp; Let&#8217;s call it a &#8220;Story Container&#8221;.&nbsp; A searchable, accessible, readable, always-available, hyperlinked, cross-referenced story container.&nbsp; In the other corner, the Church has the best story.&nbsp; Indeed - <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.gospelcom.net%2Frbc%2Fds%2Fq0406%2F">The Greatest Story Ever Told</a>.&nbsp; And countless related personal stories - stories of great faith, triumph over addictions, persistence through illness, gain from loss, and undeserved grace.
</p>
<p>
But we go on&#8230; presenting our churches like products - telling people why they&#8217;ll like our church (Relevant! Great Music! Fresh Coffee!) but so rarely simply <i>telling the stories</i> of what our church, our faith, and our God has meant to us, and the true change seen in our lives because of it.&nbsp; What is it going to take to wake the modern church to the power of connecting the two, and filling our websites with our own stories?
</p>
<p>
It&#8217;s those stories that members need to tell and visitors need to hear.&nbsp; Those stories are going to move people closer to God.&nbsp; And if our church websites aren&#8217;t moving people closer to God then we&#8217;re wasting our time.
</p>
<p>
<i>C&#8217;mon.&nbsp; Tell me a story of when God was good to you.&nbsp; Oh..before you start...I&#8217;ll bet there are other people that would like to hear it too.&nbsp; Can I put it somewhere where they will find it when they need to?</i>
</p>]]></description>
      <dc:subject>boyink&#45;articles, web&#45;strategy, the&#45;church&#45;online</dc:subject>
      <dc:date>2006-11-14T16:02:00-05:00</dc:date>
    </item>

    <item>
      <title>Helloooooo Christian Non Profits &#45; Don&#8217;t Buy that Email List!</title>
      <link>http://www.boyink.com/splaat/comments/helloooooo-christian-non-profits-dont-buy-that-email-list/</link>
      <guid>http://www.boyink.com/splaat/comments/helloooooo-christian-non-profits-dont-buy-that-email-list/#When:15:58:00Z</guid>
      <description><![CDATA[<blockquote>&#8220;We are committed to responsible information handling and will respect your privacy.&#8221; </blockquote><p>Sounds nice doesn&#8217;t it?&nbsp; I mean, who would expect <i>anything different</i> from a Christian non-profit than responsible information handling?
</p>
<p>
But wait - in order to use email as an effective marketing vehicle you need a big ole list of email addresses to send it to.&nbsp; Preferably the email addresses of people in your target market - in this case Christians who are active online and likely to respond to your offer of online training.
</p>
<p>
Oh, you haven&#8217;t been building that list yourself?&nbsp; No sweat!&nbsp; There are <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26lr%3D%26q%3Demail%2Blists%2Bfor%2Bsale%26btnG%3DSearch">plenty of  businesses</a> just itching to rent or sell you a list to use.&nbsp; Very cheaply, in some cases.
</p><p>So there you have it - a cheap, existing audience ready-made for your product or service.&nbsp; Put the message together, pay the list provider, send out your message, and lean back in your chair, arms resting behind your head - just waiting to see those responses pour in.
</p>
<p>
Ain&#8217;t the internet grand?
</p>
<p>
Well, not always.
</p>
<p>
You see - you just became a <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FSpammer">spammer</a>.&nbsp; And by doing so you&#8217;ve put  the reputation of your organization on the line.
</p>
<p>
Yeah - I know.&nbsp; The list provider told you the list was &#8220;clean&#8221; - meaning the addresses were from people who have indicated that they are willing to receive messages such as yours.
</p>
<p>
Well, guess what.&nbsp; They lied.&nbsp; How do I know?
</p>
<p>
In Clear Creek Baptist Bible College&#8217;s case, the email was sent to &#8220;hycw@boyink.com&#8221;  That&#8217;s an email address I <b>only use</b> to post comments to <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.healyourchurchwebsite.com">HealYourChurchWebsite.com</a>.&nbsp; Which means whoever put this email list together did it by <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FEmail_harvesting">email harvesting</a>.
</p>
<p>
The only &#8220;responsible information handling&#8221; in this day and age is to build your own email list - in an <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FOpt-in_e-mail_advertising">opt-in</a> fashion.&nbsp; Yes, it takes longer - but you should know the best way is never the easy way.
</p>
<p>
C&#8217;mon folks...can we stop looking so incompetent when it comes to using the Internet for Christian purposes?&nbsp; It&#8217;s embarassing already....
</p>
<p>
More on the subject: <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.boyink.com%2Fportfolio_comments%2F894_0_4_0_M9%2F">Are Unsolicited Church E-mails Considered Spam?</a>.
</p>]]></description>
      <dc:subject>boyink&#45;articles, the&#45;church&#45;online</dc:subject>
      <dc:date>2006-11-14T15:58:00-05:00</dc:date>
    </item>

    <item>
      <title>Are Unsolicited Church E&#45;mails Considered Spam?</title>
      <link>http://www.boyink.com/splaat/comments/are-unsolicited-church-e-mails-considered-spam/</link>
      <guid>http://www.boyink.com/splaat/comments/are-unsolicited-church-e-mails-considered-spam/#When:15:52:00Z</guid>
      <description><![CDATA[<p>A position statement on the use of broadcast email by churches.
</p><p><b>Church Email Mailing List Position Statement</b>
</p>
<p>
<b>Disclaimer</b>
</p>
<p>
The opinions and positions covered in this paper are not to be construed as legal advice.&nbsp; There is  no guarantee that by following these recommendations the reader will avoid either legal action or blacklisting as a result of sending out email.&nbsp; This document is meant to serve as a professional opinion only, with quotes and web links as references where appropriate.
</p><p><b>Position Summary</b>
</p>
<p>
<b><i>Broadcast email lists used by churches should be populated using a self-service, user &#8220;double opt-in&#8221; approach, only, ever. </b></i>
</p>
<p>
Any other approach violates several agreements with internet service providers, and is unethical as it abuses the private property of individuals and businesses.&nbsp; It also puts a church&#8217;s ability to communicate using it&#8217;s website or email  - any email - at risk.
</p>
<p>
It&#8217;s also clear that pursuing an opt-out approach would set a bad example for the people who attend a church  - if they see the church leadership using the approach they may feel it&#8217;s OK to add neighbors or other non-attendees to the list in the name of evangelism.&nbsp; This would greatly increase the risk of being blacklisted.
</p>
<p>
Moving away from the self-service model also means church staff will be interacting with mail list users more - getting responses to the emails, help with change of email addresses, etc.
</p>
<p>
If the church&#8217;s desire is long-term management of mailing lists consisting of hundreds of recipients, look for a robust list management tool where subscriptions can be tracked closely - with audit trails for subscriptions and unsubscriptions.&nbsp; This evidence would be necessary in the event of being blacklisted or sued.
</p>
<p>
The remainder of this document provides the references used in formulating the position summary, with definitions of various mailing list related terms, links to laws regarding email, references to the various agreements that might exist between a church and internet service providers, input from the email marketing business community as to what constitutes &#8220;accepted professional standards of conduct&#8221; and mailing list management guidelines for preventing abuse.
</p>
<p>
<b>Definitions of Mailing List-Related Terms</b>
</p>
<p>
- Opt out<blockquote>(1) type of program that assumes inclusion unless stated otherwise.
<br />
(2) to remove oneself from an opt-out program.
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.marketingterms.com%2Fdictionary%2Fopt_out%2F">http://www.marketingterms.com/dictionary/opt_out/</a></blockquote>
<p>
- Opt in/Double Opt In<blockquote>Email that is explicitly requested by the recipient
</p>
<p>
The definition of opt-in email has been a matter of intense debate.
</p>
<p>
&#8220;single opt-in&#8221; vs. &#8220;double opt-in&#8221;
</p>
<p>
The term single opt-in simply means that actions were taken to sign up for the email in question. The term double opt-in means that the subscriber has actively confirmed their subscription, typically by responding to an automatically-generated message sent to the email address. Proponents of double opt-in may not actually use that term, as they feel any email labeled &#8220;opt-in&#8221; must be verified.
</p>
<p>
 <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.marketingterms.com%2Fdictionary%2Fopt_in_email%2F">http://www.marketingterms.com/dictionary/opt_in_email/</a></blockquote>
<p>
- Spam<blockquote>&#8220;Internet spam is one or more unsolicited 1 messages, sent or posted as part of a larger collection 2 of messages, all having substantially identical content. 3&#8221;
<br />
 
<br />
 <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.monkeys.com%2Fspam-defined">http://www.monkeys.com/spam-defined</a></blockquote>
<p>
This <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.google.com%2Fsearch%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26c2coff%3D1%26safe%3Doff%26oi%3Ddefmore%26q%3Ddefine%3ASpam">Google Search</a> provides some additional definitions of Spam.
</p>
<p>
- Blacklists<blockquote>&#8220;A Blacklist is a database of known internet addresses (or IP&#8217;s) used by persons or companies sending spam. Various ISP&#8217;s and bandwidth providers subscribe to these blacklist databases in order to filter out spam sent across their network or to their subscribers.&#8221;
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.spam-blockers.com%2FSPAM-blacklists.htm">http://www.spam-blockers.com/SPAM-blacklists.htm</a></blockquote>
</p>
<blockquote>&#8220;Like most public blacklists, SpamCop is a guilty-until-proven- innocent system. If a single SpamCop user reports your message as being spam, you are added to its blacklist. Email administrators at ISPs and corporate IT departments who visit the list frequently, may then block your incoming mail to all their users.&#8221;

<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.emailsherpa.com%2Fbarrier.cfm%3FcurrentID%3D2212">http://www.emailsherpa.com/barrier.cfm?currentID=2212</a></blockquote>
<p>
<b>State and Federal Laws</b>
</p>
<p>
Church email is  subject to current applicable state and federal laws :
</p>
<p>
A Summary of State Spam Laws:
<br />
 <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.spamlaws.com%2Fstate%2Fsummary.html">http://www.spamlaws.com/state/summary.html</a>
</p>
<p>
Federal CAN-SPAM law:
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.spamlaws.com%2Ffederal%2F108s877.html">http://www.spamlaws.com/federal/108s877.html</a>
</p>
<p>
Applicability to Non-Profits:<blockquote>&#8220;Until the issue is clarified, it is recommended that non-profits comply with the CSA.&#8221; <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.arentfox.com%2Fpublications%2Falerts%2Falerts2004%2Falert2004-01-07kaminski.html">Link >></a></blockquote>
<p>
View of CSA in the Marketplace:<blockquote>Politicians Send Spammers Holiday Gift
<br />
&#8220;The main flaw in the Act is that it allows unsolicited commercial e-mail&#8212;otherwise known as spam&#8212;to be sent as long as it includes an opt-out option, a valid subject line and a working return email address. That&#8217;s not exactly prohibitive. Indeed, rather than punish or even curtail the act of spamming, what the bill actually does is legitimize it, as industry observers pointed out in a recent Datamation article. 
</p>
<p>
&#8220;This piece of legislation is telling people that as long as they don&#8217;t lie, spam is all right,&#8221; said Ray Everett-Church, chief privacy officer of the ePrivacy Group, a Pennsylvania-based company that makes anti-spam software.
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.internetnews.com%2Fcommentary%2Farticle.php%2F3288991">http://www.internetnews.com/commentary/article.php/3288991</a></blockquote>
</p>
<blockquote>&#8220;Anti-spam legislation, the CAN-SPAM Act, hasn&#8217;t made a dent in the volumes of unsolicited messages, according to a new survey by the Pew Internet &amp; American Life Project. In fact, nearly one-quarter of the respondents reported a greater influx of spam in their personal e-mail accounts since Jan. 1, 2004, when the legislation went into effect.&#8221; <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fresources%2Femail_reference%2Fresearch_reports%2Farticle.php%2F3328251">Link >></a></blockquote>

<blockquote>&#8220;What&#8217;s clearest in the CAN-SPAM law is there&#8217;s not a federal permission standard for e-mail marketing. This may not change most e-mail marketers&#8217; acquisition practices, but it certainly creates a baseline for e-mailers who may be concerned with whether they need permission for e-mail prospecting. The expectation is e-mailers won&#8217;t look to the law as a best practice, but rather to industry resources such as ClickZ to help guide the way.&#8221;<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fexperts%2Fem_mkt%2Fem_mkt%2Farticle.php%2F3291461">Link >></a></blockquote>
<p>
<b>Business Agreements</b>
</p>
<p>
Church  email communications are subject to a number of agreements between the church and the providers of the  internet services required to deliver the church&#8217;s email.
</p>
<p>
- Website Host
</p>
<p>
If the church website is hosted off-site, there is typically a policy regarding email.&nbsp; An example:<blockquote>&#8220;We do not allow UCE (Unsolicited Commercial Email), also known as spam, to be sent from our email servers, issued with a &#8220;reply to&#8221; address on our servers, or that advertises a URL on our servers. UCE includes unsolicited messages sent via email, posted on messagboards/newsgroups, or otherwise electronically sent to anyone not specifically requesting the information. This includes spam that is sent from your CGI scripts, whether sent by you or not. Additionally a $75 cleanup fee will be charged to your account, should our investigations confirm that bulk spam was sent from your account.&#8221;
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=https%3A%2F%2Fwww.bitserve.net%2Fagreement.html">https://www.bitserve.net/agreement.html</a></blockquote>
<p>
- Internet Service Provider
</p>
<p>
Churches accesses the Internet through the services of an internet service provider, who will also have a use agreement.&nbsp; Here is an example:<blockquote>&#8220;You agree not to engage in any conduct known as &#8220;Spamming.&#8221; Spamming includes, but is not limited to (1) the bulk sending of unsolicited messages, or the sending of unsolicited e-mails which provoke complaints from the recipients; (2) the sending of junk e-mail; (3) the use of distribution lists that include people who have not given specific permission to be included in such distribution processes; (4) posting commercial ads to USENET newsgroups that do not permit it; (5) posting articles containing binary encoded data to a non-binary newsgroup; (6) excessive and repeated posting off-topic users, including but not limited to transmitting any threatening, libelous or obscene material, or material of any nature which could be deemed to be offensive; and (7) the e-mailing of age-inappropriate communications or content to anyone under the age of 18.&#8221;
</p>
<p>
 <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.tdstelecom.com%2Fpartners%255Cprod_internet_tos.asp">http://www.tdstelecom.com/partners%5Cprod_internet_tos.asp</a></blockquote>
<p>
- Other &#8220;Upstream&#8221; Service Providers
</p>
<p>
Typically an email will go across wires owned by many entities.
</p>
<p>
Reference:
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Ftechsupport.charterpa.net%2Frouting%2Fflow.htm">http://techsupport.charterpa.net/routing/flow.htm</a>
</p>
<p>
Each of these entities has a terms of use agreement which may have spam-related provisions.&nbsp; Examples from some of the &#8220;Backbone&#8221; service providers:
</p>
<p>
- MCI:<blockquote>&#8220;Sending unsolicited mail messages, including, without limitation, commercial advertising and informational announcements, is explicitly prohibited. A user shall not use another site&#8217;s mail server to relay mail without the express permission of the site. &#8220;
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fglobal.mci.com%2Fterms%2Fa_u_p%2F">http://global.mci.com/terms/a_u_p/</a></blockquote>
<p>
- AT&amp;T:<blockquote>&#8220;Spam/E-mail/Usenet Abuse is prohibited on AT&amp;T IP related Services. Examples of Spam/E-mail/Usenet Abuse include but are not limited to the following activities: 
</p>
<p>
using another site&#8217;s mail server to relay mail without the express permission of the site;
</p>
<p>
using IP addresses that the Customer does not have a right to use;
</p>
<p>
collecting the responses from unsolicited electronic messages; 
</p>
<p>
maintaining a site that is advertised via unsolicited electronic messages, regardless of the origin of the unsolicited electronic messages; 
</p>
<p>
sending electronic messages with petitions for signatures, or any chain mail related materials; 
</p>
<p>
sending unsolicited electronic messages with charity requests;
</p>
<p>
sending messages that are harassing or malicious, or otherwise could reasonably be predicted to interfere 
<br />
with another party&#8217;s quiet enjoyment of the AT&amp;T IP related Services or the Internet (e.g., through language, frequency, size or otherwise); 
</p>
<p>
sending bulk (i.e., twenty-five or more recipients) electronic messages without identifying, within the message, a reasonable means of opting out from receiving additional messages from the sender; 
</p>
<p>
sending electronic messages that do not accurately identify the sender, the sender&#8217;s return address, the e-mail address of origin, or other information contained in the subject line or header;
</p>
<p>
distributing or using software designed to promote the sending of unsolicited bulk electronic messages; 
</p>
<p>
using distribution lists containing addresses that include those who have opted out; 
</p>
<p>
posting a single message, or messages similar in content, that could reasonably be expected to provoke complaints, to more than 10 online forums or newsgroups; 
</p>
<p>
posting messages to or canceling or superseding messages on an online forum or newsgroup in a manner that violates the rules of the forum or newsgroup or that contain forged header information; and
<br />
sending bulk electronic messages in quantities that exceed standard industry norms or that create the potential for disruption of the AT&amp;T network or of the networks with which AT&amp;T interconnects.&#8221;
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.business.att.com%2Fdefault%2F%3Fpageid%3Daup%26branchid%3Daup">http://www.business.att.com/default/?pageid=aup&amp;branchid=aup</a></blockquote>
<p>
Qwest:
<br />
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.qwest.com%2Flegal%2FAcceptable_Use_Policy_202.pdf">http://www.qwest.com/legal/Acceptable_Use_Policy_202.pdf</a>
</p>
<p>
<b>Employer Internet Acceptable Use Policies</b>
<br />
Corporate email addresses are considered corporate assets by the companies that pay for the ability for their employees to send email.&nbsp; As such their use is often covered by an Internet Acceptable Use Policy written and enforced by the company.
</p>
<p>
Here is an example from Herman Miller, a Fortune 500 company in Michigan:<blockquote>&#8220;Information technology is a company asset made available to a Herman Miller, Inc., employee so that he/she can meet the informational needs of employees in providing products and services to the  company&#8217;s customers and meet the administrative, development, and technical-assistance needs of employees in fulfilling their work responsibilities. &#8221;</p></blockquote>
<p>
<b>Internet Professional Community References</b>
<br />
In addition to knowing what the government says is legal, and what businesses include in their terms of use agreements, the Internet Community provides direction on what&#8217;s considered to be &#8220;conforming to accepted professional standards of conduct&#8221;, or &#8220;ethical&#8221;.
</p>
<p>
<b>&#8220;Netiquette" Demands Permission:</b><blockquote>Courtesy #7:
<br />
&#8220;Never, ever, ever, never send anyone an email about anything (especially your product or service) if the recipient did not specifically email you for that information and you are responding to their request.&#8221;
<br />
 <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.getnetiquette.com%2Fcourtesy7.html">http://www.getnetiquette.com/courtesy7.html</a></blockquote>
</p>
<blockquote>Netiquette: The Advertising Flame:
<br />
&#8220;Consider this: in conventional direct mail, a 2% response rate is considered decent. If your company experiments with unsolicited direct email, don&#8217;t be surprised if you get a 98% response, from people flaming you for clogging up their electronic mailboxes.&#8221;

<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.albion.com%2Fnetiquette%2Fbook%2F0963702513p79.html">http://www.albion.com/netiquette/book/0963702513p79.html</a></blockquote>
<p>
<b>The Legitimate Business World Recommends Opt- In only:</b>
</p>
<blockquote>Consumer Privacy: Some Email Marketing Best Practices
<br />
&#8220;Many marketers have translated the laws into practice and assert that it is acceptable, but not recommended, to send email to an individual with whom they have an existing business relationship. However, the preferred approach from legal and consumer standpoints is to deliver email messages only to those individuals who have explicitly consented to receive the email. Gathering an opt-in from consumers is essential for gaining their trust, retaining their business, and minimizing legal risks.&#8221;

<p>
&#8220;It is clear that offering consumers explicit notice about email collection, gathering consent through an opt-in process, and providing the ability for an individual to opt out in every email sent will enable you to foster trust and ultimately retain your customers longer. Review your email marketing practices with your legal counsel, determine the level of risk you are comfortable with, and make sure you&#8217;re operating within the law and building trust and loyalty among your customers to maximize the effectiveness of your marketing program.&#8221;
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fexperts%2Fem_mkt%2Fopt%2Farticle.php%2F835841">http://www.clickz.com/experts/em_mkt/opt/article.php/835841</a></blockquote>
</p>
<blockquote>Opting for Results
<br />
&#8220;Permission marketing&#8221; is the buzzword for the politically correct way to manage your customer relationships today. It means you must have consent before you email anything to anybody. There&#8217;s opt-in and opt-out, double opt-in and double opt-out, and lots to talk about, but here&#8217;s one simple fact right up front: Someone who fails to opt-out has not opted in.&#8221;

<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fexperts%2Fdesign%2Ftraffic%2Farticle.php%2F843491">http://www.clickz.com/experts/design/traffic/article.php/843491</a></blockquote>
</p>
<blockquote>How NOT to Promote Your E-business:
<br />
&#8220;It only takes one message to shut your site down.&#8221;

<p>
&#8220;It really is simple to stay out of trouble&#8212;just don&#8217;t ever email anyone without their permission.&#8221;
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fsellitontheweb.com%2Fezine%2Fopinion064.shtml">http://sellitontheweb.com/ezine/opinion064.shtml</a></blockquote>
</p>
<blockquote>Growing an E-Mail List: Five Practical Tips:
<br />
&#8220;You always want to bring in new opt-in subscribers, enough, at least, to replace the e-mail addresses lost each month (via hard bounces and unsubscribes).&#8221;

<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fexperts%2Fem_mkt%2Fopt%2Farticle.php%2F3329951">http://www.clickz.com/experts/em_mkt/opt/article.php/3329951</a></blockquote>
</p>
<blockquote>- Permission to Spam?
<br />
&#8220;When requesting permission to deliver future e-mail communications, be very explicit about how the address will be used. Make it clear what kind of communication the individual is agreeing to receive and at what frequency. An opt-in for a certain type of communication does not constitute broad permission to blast away at that person&#8217;s inbox with different categories of messaging, unless that broad permission is explained and agreed to upfront. Someone who opts in to receive a newsletter about personal health may not be thrilled to unexpectedly receive an unrequested travel newsletter, a third-party promotion, or a monthly company update from the same organization.&#8221;

<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.clickz.com%2Fexperts%2Fem_mkt%2Fopt%2Farticle.php%2F2179291">http://www.clickz.com/experts/em_mkt/opt/article.php/2179291</a></blockquote>
<p>
<b>Basic Mailing List Management Guidelines for Preventing Abuse</b>
<br />
We recommend the mailing list guidelines found at:
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.mail-abuse.com%2Fsupport%2Fan_listmgntgdlines.html">http://www.mail-abuse.com/support/an_listmgntgdlines.html</a> 
</p>]]></description>
      <dc:subject>boyink&#45;articles, the&#45;church&#45;online</dc:subject>
      <dc:date>2006-11-14T15:52:00-05:00</dc:date>
    </item>

    <item>
      <title>Church Web Sites &#45; What We Don&#8217;t Know</title>
      <link>http://www.boyink.com/splaat/comments/church-web-sites-what-we-dont-know/</link>
      <guid>http://www.boyink.com/splaat/comments/church-web-sites-what-we-dont-know/#When:16:09:00Z</guid>
      <description><![CDATA[<p>Three things we don&#8217;t know about church web sites; How Christians use the web, what a Church site should be, and how to measure the success of a Church site.
</p><p>A recent discussion on the Churchsite Chat Yahoo! Group has been quite thought provoking.&nbsp; It started when a webmaster for a small church noted that not much traffic was going past his home page, and asked how to get people to go deeper.&nbsp; The resulting discussion tells me there are three basic things that we don&#8217;t know regarding church websites:
</p>
<p>
<b>1. How Christians (and people interested in Christianity) Use the Web  </b>
<br />
Some of the thought-provoking comments from the discussion:
<br />
<ul>
<li>&#8220;Remember most people who will come by your site are not local and will never attend your church. What do you have for them?&#8221;</li>
<li>&#8220;Start to think like a web surfer. Ask yourself, if I came to a page like mine, what would make me go deeper into a web site? Put that on your front page. But remember nearly always more people will come by your front page than stay around. Surfers are notorious for being easily bored.&#8221;</li>
</ul>
<p>
I&#8217;m going to go out on a limb here - in light of any data to the contrary -  and say that Christians are no different from the average web user, and that 1997-esque web surfing is dead.&nbsp; People are going to the web, and your church site, with a specific task to do, or question to answer&#8212;let&#8217;s forget about having to entertain easily-bored surfers.&nbsp; But what content should your church site have then?&nbsp; Aha - there&#8217;s the second thing we don&#8217;t know:
</p><p><b>2.What a Church Web Site Should Be:</b>
<br />
Comments from the Churchsite-chat discussion:
<br />
<ul>
<li>&#8220;considering the time you need to spend developing and maintaining a church site, if it&#8217;s done SOLELY for advertising purposes, it probably isn&#8217;t worth the time involved.&#8221;</li>
<li>&#8220;If I was looking for a church web site locally it would probably be because I had been invited to a meeting there and no one had given me the directions on how to get there. I would also be interested in seeing how that church fitted into its local community. So what groups met there and when would be useful information to include.&#8221;</li>
<li>&#8220;more people check the weather daily than any other online info...making the addition of a weather module one of the best ways to attract return visitors.&#8221;</li>
<li>&#8220;I think if you want your church website to have an evangelistic input to the local community, then a community-resource page(s) is very useful&#8221;</li>
<li>&#8220;a good number of church sites create a &#8220;portal page&#8221; for their visitors...they can make that page their personal homepage so that every time they log onto the internet they can see church events, weather, community events, and more on a single page.&#8221;</li>
<li>&#8220;if all one has on a church site is a picture of the church, names of the staff and a program of events, that you really have missed an opportunity and are doing a lot of work for a very limited purpose. If someone is looking for a church, the majority will turn to the Yellow Pages before they will the WWW&#8221;</li>
<li>&#8220;I can see why we would put up community news, weather, sports, etc. While I haven&#8217;t heard a pastor give sports scores from the pulpit, I have heard many make reference to a big game as a peg for a sermon. The same with weather and news and entertainment. Besides, maybe some Christians would like to have their local church set up as their home page and get such dynamic content.&#8221;</li>
</ul>
<p>
Many interesting ideas.&nbsp; The trouble is, for people involved with building church sites, there&#8217;s no existing research to authoritatively show what it is that  people coming to a church site want, need, or expect, as exists for other audiences.&nbsp; And lacking any direction, it&#8217;s easy to see why church site builders so often go for what Dean Peters at <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.healyourchurchwebsite.com">http://www.healyourchurchwebsite.com</a> calls &#8220;Jesus Junk&#8221;.&nbsp; But I&#8217;m starting to think that Jesus Junk is the symptom, and this church-site identity crisis is really the root problem.&nbsp; Lacking any concrete data, though, discussions about church sites break down into &#8220;what I think&#8221; type arguments. 
</p>
<p>
So here&#8217;s what I think.&nbsp; Maybe I spend too much time on the business side of bulding web sites, but for me the first and primary thing a church web site should do is present what is unique about that church - and that really starts with the journalistic basics of &#8220;who, what, where, when, why, how&#8221;.&nbsp; Getting this part done right is fundamental and your first priority.&nbsp; 
</p>
<p>
What this unique content <b>doesn&#8217;t include</b> is the local news, sports, and weather.&nbsp; Given that to an individual web user the entire internet is the same distance away, and takes the same effort to get to, there is just no good reason to give up your church&#8217;s valuable home page space to this type of content.&nbsp; Based on our knowledge of &#8220;direct driving&#8221; on the net, people wanting weather will go to weather.com - even if your feed is from weather.com.&nbsp; Weather from a weather site will be perceived as being more up to date, and more trustworthy than that same weather presented in the context of a church site. The average user is confused by the function of the home page button, for goodness sake - what do they know about dynamic syndicated content?
</p>
<p>
And what&#8217;s it say, really, when someone comes to your church&#8217;s home page and the &#8220;best thing ya got&#8221; isn&#8217;t about the church?&nbsp; Would you direct newcomers to your church building to TV&#8217;s showing local weather?&nbsp; Would you ask your pastor to give high school football updates mid-sermon?&nbsp; Sounds silly to even ask, no?
</p>
<p>
And once the basics are down?&nbsp; Then what?&nbsp; Your choices are either build to support the community within the church, or build to support the community outside the church.&nbsp; I recommend the first.&nbsp; Build tools that nurture and support the community already happening inside the church.&nbsp; Put up discussion boards for small groups to use, or for digital small groups to form within the church.&nbsp; Create email lists for prayer needs, or bible studies.&nbsp; Build group blogs for volunteer groups that need a way to organize and administer their outreach.&nbsp; 
</p>
<p>
Why this inner focus rather than external?&nbsp; Because the value will be more immediately apparent to the you, and the rest of the church.&nbsp; You&#8217;ll hear people talk about connecting via these tools.&nbsp; You&#8217;ll see reference to them in other publications the church does.&nbsp; You&#8217;ll create a buzz within the attendees of your church.&nbsp; You&#8217;ll be able to roughly measure the effectiveness of what you&#8217;ve built by how often you hear that buzz.&nbsp; Which brings us to (and helps get around) the last thing we don&#8217;t really know about church web sites:
</p>
<p>
<b>3.How To Measure the Success of a Church site</b>
<br />
Snippets from the Churchsite-Chat group discussion:
<br />
<ul>
<li>&#8220;Most of the hits come in..&#8221; </li>
<li>...church sites don&#8217;t get the traffic we would like, many who do get that traffic...</li>
<li>...regional search engines to drive the traffic to your site.. </li>
<li>...gets over 500 hits a month&#8230; </li>
<li>...high search engine ranking for keywords relating&#8230; </li>
<li>...The test of course is the number of hits the page gets...</li>
</ul>
<p>
Here&#8217;s the problem: hits are meaningless.&nbsp; Site traffic levels fail the &#8220;so what?&#8221; test.&nbsp; Even in the business world, looking at traffic levels as a success metric has been questioned for a couple of years now.&nbsp; If the bottom-line businesses struggle to connect traffic levels to web site value, how can the Church?&nbsp; If the Church is about changed lives,  then what&#8217;s the metric we can use to measure the effect of all that web traffic?
</p>
<p>
This comment from the Churchsite chat discussion really caught my eye:
</p>
<p>
<i>&#8220;Of course,traffic isn&#8217;t the point of having a church website...it&#8217;s creating more community to further the gospel&#8221;.</i>
</p>
<p>
Amen.&nbsp; But let&#8217;s do that by nailing the basics, then building community from the inside-out where the results are more immediately apparent.
</p>
<p>
And let&#8217;s think about how we can, collectively, somehow produce the professional level research that might help answer some of these things we don&#8217;t know about church web sites.&nbsp; 
</p>
<p>
I&#8217;m open to ideas.
</p>]]></description>
      <dc:subject>boyink&#45;articles, web&#45;strategy, the&#45;church&#45;online</dc:subject>
      <dc:date>2006-10-21T16:09:00-05:00</dc:date>
    </item>

    <item>
      <title>Culture :: Helping The Church With Design And Technology</title>
      <link>http://www.boyink.com/splaat/comments/culture-helping-the-church-with-design-and-technology/</link>
      <guid>http://www.boyink.com/splaat/comments/culture-helping-the-church-with-design-and-technology/#When:17:12:00Z</guid>
      <description><![CDATA[<blockquote>Eighteen months ago I knew virtually nothing about websites, web design or anything else. To me, terms like HTML, CSS, RSS, and the like were all worse than &#8220;Greek to me&#8221; - at least I sensed some purpose to knowing Greek as a pastor. Techno-jargon seemed far less important.&nbsp; But after a year of working through website stuff for the church, here is what I’ve learned: <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.betachurch.org%2Fculture%2Farchives%2F2006%2F01%2Ftop_ten_things.php">Link to BetaChurch Article >></a></blockquote><p>Yes, another article on church web design.&nbsp; I&#8217;ve been (or have tried to be) quiet on the this topic lately, because I&#8217;m not actively engaged in building any church websites so was starting to feel like a &#8220;Monday morning quarterback&#8221;.
</p>
<p>
There&#8217;s a difference with this article, though, that makes it worth linking to.&nbsp; 
</p><p>Ben Dubow, the author, isn&#8217;t a web developer&#8212;he&#8217;s the pastor of <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.spcc-storrs.org%2F">St. Paul&#8217;s Collegiate Church at Storrs</a> in Connnecticut.
</p>
<p>
Here&#8217;s a few of Ben&#8217;s &#8220;Ten Things to Know About Your Church Website&#8221;:<blockquote><ul><li>1. The web is probably the first place people look for a church&#8212;before the yellow pages, newspaper, or anything else.</li><li>2. Prospective visitors have already formed an idea about your church based on your website - good or bad.</li><li>3. A website communicates your &#8220;true values&#8221; to people.</li></ul></blockquote>
<p>
Good stuff.&nbsp; I&#8217;m encouraged to hear these words coming from the Pastor of the church.&nbsp; I&#8217;d love to see Ben&#8217;s article get picked up and published in other places where Pastors with less of an &#8220;Internet Mindset&#8221; will read it.
</p>
<p>
<a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.christianitytoday.com">Christianity Today</a> - are you listening?
<br />

</p>]]></description>
      <dc:subject>web&#45;implementation, the&#45;church&#45;online</dc:subject>
      <dc:date>2006-01-19T17:12:00-05:00</dc:date>
    </item>

    <item>
      <title>Church Web Adviser Newsletter</title>
      <link>http://www.boyink.com/splaat/comments/church-web-adviser-newsletter/</link>
      <guid>http://www.boyink.com/splaat/comments/church-web-adviser-newsletter/#When:21:14:00Z</guid>
      <description><![CDATA[<blockquote>Church Web Adviser was created exclusively for busy church leaders who understand the important role a powerful Web site can play in Christian ministry today, but who also face the realities of limited time, finances and staffing. <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.churchwebadviser.com%2F">ChurchWebAdviser.com</a></blockquote><p>Since so much traffic to Boyink.com is by those interested in church websites, I thought I would mention a new publication - <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.churchwebadviser.com%2Furl">Church Web Adviser</a>, published by <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.comresources.com">Communication Resources</a>.
</p>
<p>
I just received a copy of this last week, and have to say that I&#8217;m impressed with the quality and content that I see in the premier issue.&nbsp; Authors include Kevin D. Hendricks of <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.churchmarketingsucks.com%2Furl">ChurchMarketingSucks.com</a>,  Mike Atkinson of <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.uneeknet.com%2Furl">uneekNet.com</a>, Lou Hornberger of <a href="http://www.boyink.com/splaat?URL=http%3A%2F%2Fwww.youthspecialties.com%2Farticles%2Fputer%2F">Youth Specialties</a>, and others (including a small submission on church blogging by yours truly).
</p>
<p>
Topics besides blogging include web pages for children&#8217;s ministries, online photo albums, selecting a host for your church site, how to connect with worshippers online, and a bunch more.
</p>
<p>
While it may seem strange to subscribe to a traditional printed newsletter to learn about websites, we web-heads need to remember that not everyone is so averse to the printed page.
</p>
<p>
For $99/year, if getting a regular newsletter mailed to your church staff increases the interest and involvement in adding quality and value to your church website then it&#8217;s money well spent, even if it doesn&#8217;t appear in a browser window....<img src="http://www.boyink.com/images/chipper/wink.png" width="17" height="16" alt="wink" style="border:0;" />
</p>]]></description>
      <dc:subject>web&#45;implementation, the&#45;church&#45;online</dc:subject>
      <dc:date>2005-12-08T21:14:00-05:00</dc:date>
    </item>

    
    </channel>
</rss>