<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
<title>Blog</title>
<link>http://www.monkdevelopment.com/blog/</link>
<description />
<lastBuildDate>Wed, 22 May 2013 15:36:26 GMT</lastBuildDate>
<language>en-us</language>
<copyright>Copyright 2013 Monk Development</copyright>
<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/monkdev/blog" /><feedburner:info uri="monkdev/blog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>monkdev/blog</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
  <title>Communicating to Your Entire Church Through the Church Website</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/PVDMTTh5ZJI/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/communicating-to-your-entire-church-through-the-church-website/</guid>
  <pubDate>Tue, 21 May 2013 15:36:23 GMT</pubDate>
  <description>Quick: What's the most effective method your church uses to move people through the discipleship process? In other words, how do you get new visitors to join? And once they've joined, how do you get members engaged in the life of the church?</description>
  <content:encoded><![CDATA[<p>Quick: What's the most effective method your church uses to move people through the discipleship process? In other words, how do you get new visitors to join? And once they've joined, how do you get members engaged in the life of the church?</p>
<p>Verbal announcements? Bulletins? Smoke signals? Begging? Pleading?</p>
<p>What if I told you one of the most effective ways to move church members through your discipleship process was with your website? Would you believe me?</p>
<p>Anticipating some skepticism, here are three examples of churches who clearly communicate the discipleship process with their website.</p>
<h2>Highland Park United Methodist</h2>
<p><a href="http://www.hpumc.org/"><img src="http://d305057cc27ddd3811ea-f956112674501ff644933e3baa18005a.r38.cf2.rackcdn.com/uploaded/h/0e2143103_highland-park-screen-cap.png" alt="Highland Park Screen Cap" title="Highland Park Screen Cap" width="580" style="margin-top: 10px; margin-bottom: 10px;" /></a></p>
<p>One of the most helpful items on Highland Park's website is the STARTINGPOINT button at the bottom of their image rotators.</p>
<p>StartingPoint is the <strong>major</strong> discipleship opportunity for the church. Directing traffic to this specific <em>ahem</em> <em>starting point</em> is smart for two reasons:</p>
<ol>
<li>It captures the homepage traffic magic and places a highly-visible call-to-action where people are most likely to see it.</li>
<li>When people click, it communicates there is more to being a member of Highland Park than simply attending on Sundays.</li>
</ol>
<p>From the StartingPoint page:</p>
<p style="padding-left: 30px;"><em>StartingPoint is for anyone who wants to learn more about HPUMC. Attending is the first step in becoming a member. </em></p>
<p>This last sentence moves new visitors and regular attenders into a deeper relationship with the church by suggesting membership. Brilliant.</p>
<hr style="border: 1px #e1e1e1 solid; margin: 20px 0;" />
<h2>Eagle Brook Community Church</h2>
<p>Eagle Brook is one of those rare churches that gets simplicity. Simple does not mean simplistic. In fact, the exact opposite is often true.</p>
<p><a href="http://eaglebrookchurch.com/"><img src="http://d305057cc27ddd3811ea-f956112674501ff644933e3baa18005a.r38.cf2.rackcdn.com/uploaded/e/0e2143117_eagle-brook-screen-cap.png" width="580" height="395" alt="_Eagle Brook Screen Cap" title="_Eagle Brook Screen Cap" style="margin-top: 10px; margin-bottom: 10px;" /></a></p>
<p>Simple website design and information architecture is incredibly complex. It takes time, effort, thinking, pruning, and constantly asking the question, "does this need to go here?"</p>
<p>What you get with Eagle Brook is a home page that communicates something to every persona within the discipleship process of a church:</p>
<ol>
<li><strong>New visitors</strong>: Locations and service times, plus a dedicated "I'm New" section to ensure people coming for the first time know what to expect.</li>
<li><strong>Regular attenders</strong>: The "Next Steps" section is specifically for people who want to grow in their commitment to the church community. Appropriately named and no doubt creates movement along the <a href="http://www.monkdevelopment.com/blog/serve-your-church-with-web-analytics/">mission process</a>.</li>
<li><strong>Active members:</strong> The "Giving" tab allows members to easily give with just three clicks. (Our research shows members who attend the church longer are more likely to give regularly online.) The "Latest Message" page is also targeted towards active members.</li>
<li><strong>Mature disciples:</strong> For the full-fledged disciple-makers of Eagle Brook, we go back to the "Next Steps" section. Mature disciples can search for opportunities where they can serve, both locally and globally.</li>
</ol>
<p>The Eagle Brook home page works because it communicates <em>something</em> to <a href="http://www.monkdevelopment.com/what-we-do/strategy-services/">every persona within the church.</a></p>
<hr style="border: 1px #e1e1e1 solid; margin: 20px 0;" />
<h2>Port City Community Church</h2>
<p>The beautifully-designed website of Port City Church clearly communicates it's a church whose desire is to be known.</p>
<p>Much like Eagle Brook's website, Port City communicates to each persona in the mission process design continuum.</p>
<p><a href="http://www.portcitychurch.org/"><img src="http://d305057cc27ddd3811ea-f956112674501ff644933e3baa18005a.r38.cf2.rackcdn.com/uploaded/p/0e2143121_port-city-screen-cap.jpg" width="580" height="419" alt="_Port City Screen Cap" title="_Port City Screen Cap" style="margin-top: 10px; margin-bottom: 10px;" /></a></p>
<p>For new members, the "I'm New" button as the first item in the top navigation practically screams, "click me!" Port City</p>
<p>Regular attenders are encouraged to take "Next Steps" to further integrate into the communal life of the church. (The "Events" tab at the top is a genius way to <a href="http://www.monkdevelopment.com/blog/serve-your-church-with-web-analytics/">create movement among regular attenders.</a>)</p>
<p>Active members can easily join a small group by registering for MYPC3, the online portal for church members. MYPC3 is the place where "you can search for a Small Group, stay in touch with other volunteers and/or your small group through group calendars and communications, donate online or view your giving statement."</p>
<p>Mature disciples can pick from the opportunities listed in MYPC3 or from the long list of <a href="http://www.portcitychurch.org/volunteer/">volunteer opportunities</a> at Port City.</p>
<h2>Conclusion</h2>
<p>Even though these churches serve different populations and communities, they all share one thing in common: movement. The home page clearly communicates to the various groups within the church, while maintaining a crystal-clear focus on the mission. That, dear readers, is a hard thing to do.</p>
<p><strong>If you do nothing else:</strong> Does your church website have the same clear path for involvement? Does it create movement among your members? If not, <a href="http://www.monkdevelopment.com/what-we-do/strategy-services/">let us help you create a mission process design.</a></p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/PVDMTTh5ZJI" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/communicating-to-your-entire-church-through-the-church-website/</feedburner:origLink></item>
<item>
  <title>What Church Communicators Crave in a CMS</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/0KrMa3PqvAc/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/what-church-communicators-crave-in-a-cms/</guid>
  <pubDate>Tue, 14 May 2013 15:11:57 GMT</pubDate>
  <description>We wanted to know what church communicators need out of a CMS (content management system). We thought and thought and thought. And then we asked some of the best and brightest communicators we knew: "What do you need most?"</description>
  <content:encoded><![CDATA[<p>We wanted to know what church communicators need out of a CMS (content management system). We thought and thought and thought. And then we asked some of the best and brightest communicators we knew: "What do you need most?"</p>
<p>Turns out church communicators aren't shy about voicing their opinion. We love that. There was a lot of wisdom in their answers. Gold nuggets we wanted to share with you.</p>
<p>We distilled the most-requested features and needs were and put them in an easy-to-read list below. Check it out.</p>
<h2>What Church Communicators Need From a Website Solution</h2>
<p><strong>Need #1: Easy-to-use CMS</strong></p>
<p>"We wanted to have as many pages as we wanted. Easy navigational setup was a must. We also wanted a template that was easy-to-use but provided a polished web presence. None of our staff are HTML coders! Our church also needed online giving&mdash;our previous host could not do that." Rachel Allen, <a href="http://www.centralbiblemiami.org/">Central Bible Church</a></p>
<p><strong>Need #2: Strategic website alignment with mission</strong></p>
<p>"We had no purpose, direction, or mission with our old site. We wanted to work with a partner who had a strategy component <s></s> we needed that element to better think through the purpose of our website." Don Wamboldt, <a href="http://worshipcenter.org/">Worship Center</a></p>
<p><strong>Need #3: Control over events</strong></p>
<p>"We are so community-driven, we needed more control over our ability to coordinate events." Eric Wafforde and Alison Aars, <a href="http://www.hpumc.org/">Highland Park United Methodist Church</a></p>
<p><strong>Need #4: Flexibility to edit content</strong></p>
<p>"The most crucial need we had was being able to edit our site as-needed. We wanted something we could edit and keep up with ourselves. We didn&rsquo;t want to be spending a lot of time on the website and miss out on ministry opportunities." Myke Wilkerson, <a href="http://truevinechurch.org/">True Vine Church</a></p>
<p>"We needed a design overhaul and also wanted easy-to-manage content. I need something I can tweak on my own without having to contact a web developer." Greg McIntyre, <a href="http://wcmc.ca/">Wilmot Centre Missionary Church</a></p>
<p>"Keeping content updated on our site is difficult because our current system isn't easy to use. I need the ability to have several leaders within our church update their own content. People aren't doing it now because the system is too difficult to use. Even when they do update content, our people are having issues with the design and layouts of the pages." Mike Galvin, <a href="http://holyfamilyfishers.org/">Holy Family Episcopal Church</a></p>
<p><strong>Need #5: Multimedia integration</strong></p>
<p>"The way our site looks and the ability to edit and use video are my main concerns." Mark Davis, <a href="http://westwindschurch.com/">WestWinds Church</a></p>
<p>"I wanted a solution that would be intuitive, fluid, and easy for people who have other responsibilities and aren&rsquo;t web programmers or content managers. We wanted a solution that offered a wide range of features and designs that allowed flexibility and graphic elements in stills, slideshows or video." - David Skidmore,&nbsp;<a href="http://www.diomil.org/">Diocese of Milwaukee</a></p>
<h2>Conclusion</h2>
<p>It's clear church communicators have specific needs when it comes to a CMS. What needs do you and your team have? Simply put, what makes you happy when you're creating, managing, and updating content for your church website?</p>
<p><strong>If you do nothing else:</strong> Take a look at how <a href="http://www.monkdevelopment.com/eagle-brook-church-case-study/">Monk Development helped Eagle Brook Church</a> navigate the same challenges listed above.</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/0KrMa3PqvAc" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/what-church-communicators-crave-in-a-cms/</feedburner:origLink></item>
<item>
  <title>FREE RESOURCE: What Every Web Geek Needs to Know About Building a Church Website</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/zZgZA9Ks10k/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/free-resource-what-every-web-geek-needs-to-know-about-building-a-church-website/</guid>
  <pubDate>Sat, 11 May 2013 03:36:45 GMT</pubDate>
  <description />
  <content:encoded><![CDATA[<p><a href="http://www.monkdevelopment.com/free-download-what-every-web-geek-needs-to-know/" style="line-height: 1.7;"><img src="http://d305057cc27ddd3811ea-f956112674501ff644933e3baa18005a.r38.cf2.rackcdn.com/uploaded/a/0e2076001_april-580x125.jpg" width="580" height="125" alt="april-580x125" title="april-580x125" style="margin-top: 10px; margin-bottom: 10px;" /></a></p>
<p>If you&rsquo;re a technically-minded person (or you work with a technically-minded person) we&rsquo;ve learned quite a bit about you. Our experience has shown us you care deeply about using technology to tell the story of your church.</p>
<p>That's why we've put together this helpful resource to focus in on the things you care about when working with a church website.</p>
<p>By downloading this free ebook, you will learn:</p>
<ol>
<li>The main responsibilities of a technically-minded person working on a church website</li>
<li>What technically-minded people most need in a church website solution (and why it matters)</li>
<li>Looking at how the flexibility, scalability, and usability of a church website solution all affect the happiness level of a technically-minded person</li>
<li>The true cost of choosing an open-source solution for your church website</li>
</ol>
<p>Over the years, we've worked with dozens of technically-minded people and they all seem to need a church website solution that will give them freedom in three areas:</p>
<ol>
<li>Flexibility</li>
<li>Scalability</li>
<li>Usability</li>
</ol>
<p>Use this resource to help identify your needs for each specific area. As always, this resource is free and instantly downloadable here:</p>
<p><a href="http://www.monkdevelopment.com/free-download-what-every-web-geek-needs-to-know/">What Every Web Geek Needs to Know About Building a Church Website</a></p>
<p><strong>If you do nothing else:</strong> Send this link to someone you know who is technically-minded. You'll be their hero!</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/zZgZA9Ks10k" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/free-resource-what-every-web-geek-needs-to-know-about-building-a-church-website/</feedburner:origLink></item>
<item>
  <title>The 5 Biggest Challenges Facing Church Communicators</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/ZiGa-ab0SWE/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/the-5-biggest-challenges-facing-church-communicators/</guid>
  <pubDate>Mon, 06 May 2013 17:26:26 GMT</pubDate>
  <description>If you're in church communications, you're going to run into some difficulties.

As we talk to more and more church communicators, we've noticed specific problems areas arise time and again. See if you don't identify with some of the issues presented on this list.</description>
  <content:encoded><![CDATA[<p>If you're in church communications, you're going to run into some difficulties.</p>
<p>As we talk to more and more church communicators, we've noticed specific problems areas arise time and again. Most of these pains stem from a lack of cohesive missional direction within an organization.</p>
<p>At MonkDev we've coached numerous churches and helped them establish missional goals. (If you think this might be your church, <a href="http://www.monkdevelopment.com/blog-contact-us-consult/">please let us know</a>. We're here to help!) Without some outside help, these issues might not ever get resolved.</p>
<p>In the meantime, see if you don't identify with some of the issues presented on this list.</p>
<p><strong>5. Moving from gatekeeper to consultant.&nbsp;</strong>Our CEO, Drew Goodmanson, often says communication professionals need to move to be consultants working with ministry leaders to be effective in using technology to achieve their ministry goals. Their role must shift from the "rubber stamp people" to the "how can we resource you to achieve your goals?" people.</p>
<p><strong>4. Overall communications strategy.</strong> When we talk to church communicators, the tension they're feeling often comes from a lack of missional focus. Sure, there's usually a vague mission statement in place somewhere, but it hasn't permeated the entire organization. Communication requires a subject&mdash;an end point. Too often, church communicators feel like they're trying to hit a moving target. If the mission isn't clear, the communication surrounding the mission won't be either.</p>
<p><a href="http://www.monkdevelopment.com/what-we-do/strategy-sessions/">Missional alignment</a> helps direct the course for focused posting. Combine alignment with our <a href="http://ekklesia360.com/get-started">easy-to-use technology</a>, and you have a strategy to help you create your ministry goals online.</p>
<p><strong>3. Content strategy for the website.&nbsp;</strong>A website exists to convey who you are as a church to those outside the organization. It can also actively move people through the discipleship process of your church. The only kicker? It needs to be focused. The content on your website needs to cut like a laser beam, not blast like a shotgun. Does each word have a purpose? If not, it's time to look into a&nbsp;<a href="http://www.monkdevelopment.com/blog-contact-us-consult/">content strategy.</a></p>
<p><strong>2. Budget constraints.</strong> One of the most mentioned obstacles is budget restrictions. Communication folks simply feel like they don't have enough in the budget tank to go as far as they'd like. Thankfully, there are affordable, free, and near-free solutions to do a lot of the church communications heavy-lifting. MonkDev's Instasite solution, for instance, can get your church into a <a href="http://www.ekklesia360.com/#/explore">responsive design church website</a> for less then the cost of most iPads. (If you want further penny-pinching tips, check out&nbsp;<a href="http://www.churchmarketingsucks.com/2013/04/5-ways-to-do-church-communication-on-the-cheap/">this great post from Church Marketing Sucks.</a>)</p>
<p><strong>1. Time. </strong>Who's got the time? Not church communicators. Whether it's&nbsp;facing the challenge of navigating internal deadlines, a stalled project, or the cyclical Sunday deadline, church communicators nearly always operate under a time crunch. Simply put, there's a&nbsp;<em>lot</em> to get to for a church communicator throughout the week: bulletins, blog posts, posters, signage, emails, <a href="http://my.ekklesia360.com/updates/100723-document-approval.php">document approval</a>, editing, writing, designing, announcements, slide decks...<em>WHEW!&nbsp;</em>Finding enough time in the week to get everything done is a major challenge for church communicators.&nbsp;</p>
<p>If you're feeling the pinch, know there's an entire team here at MonkDev waiting to help. We've built modules to help church communicators leverage what time they <em>do&nbsp;</em>have. Easy-to-edit <a href="http://www.monkdevelopment.com/blog/announcing-easy-to-implement-staff-pages/">Staff Pages</a>, role assignments (so you don't get stuck in the bottleneck), and a ministry-minded team&nbsp;to help you and your staff so you aren't stuck doing support. <a href="http://ekklesia360.com/get-started">Let's talk!</a></p>
<h2>Conclusion</h2>
<p>Any way you slice it, church communicators have a tremendous responsibility to communicate a timeless message in a economic and interesting way. We'll lead you through that process here on the blog in the next few weeks.</p>
<p><strong>If you do nothing else:</strong> What's one common challenge you face as a church communicator? Let us know in the comments. Try and surprise us!</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/ZiGa-ab0SWE" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/the-5-biggest-challenges-facing-church-communicators/</feedburner:origLink></item>
<item>
  <title>What Every Web Geek Needs to Know About Open Source</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/3ecLkO9L8YE/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-open-source/</guid>
  <pubDate>Mon, 22 Apr 2013 22:29:08 GMT</pubDate>
  <description>One of the most oft-asked questions we get here at MonkDev is, "Is Ekklesia 360 built on WordPress or another open-source site?"

The quick answer is, "no." While there are a lot of fantastic open-source solutions available, churches must realize implementing one of them isn't necessarily free.</description>
  <content:encoded><![CDATA[<p><em>This is a continuation of our "What Every Web Geek Needs to Know" series. <a href="http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-church-website-technology/">Click here</a> to read last week's post.</em></p>
<p>One of the most oft-asked questions we get here at MonkDev is, "Is Ekklesia 360 built on WordPress or another open-source site?"</p>
<p>The quick answer is, "no." While there are a lot of fantastic open-source solutions available, churches must realize implementing one of them isn't necessarily free. Scaling an open-source solution takes skill, time, and commitment.</p>
<h2>The True Cost of Open-Source</h2>
<p>The cost of open-source is hidden in the time and money involved with installing the software, customizing it, installing plug-ins, and maintaining the software with upgrades and security patches.</p>
<p>Unless you have a savvy volunteer who can devote part-time hours to maintaing your site, most churches will need someone to dedicate time to managing their software. Someone like Tom.</p>
<p>Therein lies the problem. As we've noted, Techie Tom is busy. Whether it's helping other team members connect to wifi, researching the latest load times for the church's servers, or showing the executive team on the best way forward for the church website, adding huge website responsibilities to Tom's work load makes him unhappy. Having an available technical resource to call when they need to get things done is a <strong>huge</strong> plus.</p>
<h2>Freeing Tom Up to Focus</h2>
<p>Tom will gravitate towards a solution that frees him up to focus on ministry by handling all technical details for him. This means he can focus on what he does best&mdash;whatever it may be&mdash;and not get stuck in the doldrums of software maintenance.</p>
<p>A system like the one MonkDev offers has the flexibility and customization Techie Tom likes. Ekklesia 360 has the <em>oomph</em> to satisfy even the most technically-minded Toms around.</p>
<p>We've thought through how a sermon can be uploaded and distributed online and for maximum impact and reach. Think of MonkDev as another member of your church staff, thinking ahead about future technical needs and consistently working in the background with your team in mind.</p>
<p>A technical person like Tom doesn't want to spend hours "creating" or "modifying" a website. A solution built to work out-of-the-box to accomplish the common goals for church websites&mdash;increase awareness, engage members, deepen relationships&mdash;is highly appealing to Tom.</p>
<h2>Tom's Mission, Should He Choose to Accept It</h2>
<p>Imagine a solution that provides a high level of customization right out of the gate, and you've found something that'll make Tom a happy man. Tom wants to know he can dive into the website and make any modifications and customizations himself if he has the time. He also wants to know he can pick up the phone and get help from a trusted source, should he need it.</p>
<p>(Our Instasite option was built with this in mind. It can work for 90% of churches right out of the box. Tom can add logos, colors, and content without having to turn to anyone else.)</p>
<p>Ultimately, Techie Tom is passionate about much more than technology. He's all about seeing the tools he uses on a daily basis for the spread of the gospel.</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/3ecLkO9L8YE" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-open-source/</feedburner:origLink></item>
<item>
  <title>What Every Web Geek Needs to Know About Church Website Technology</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/InMpLOrsidI/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-church-website-technology/</guid>
  <pubDate>Mon, 15 Apr 2013 14:08:54 GMT</pubDate>
  <description />
  <content:encoded><![CDATA[<p><em>This is the second post in our &ldquo;What Everyone Needs to Know About Building a Church Website&rdquo;. <a href="http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-building-a-church-website/">Read the previous post here</a>.</em></p>
<p>On a given day, Tom finds himself doing everything from onboarding new staff with phone, Internet, email, computer, etc., to updating computers with new software releases, to reviewing church data and presenting it to church leadership, to maintaining the ChMS (Church Management System) and troubleshooting problem areas.</p>
<p>Whew! Tom's duties are vast and varied. While there are nuances depending on what type of context Tom finds himself in (e.g. large or small), Tom is a doer at the core of his being.</p>
<p>Being a doer, Tom needs to know what goes in to building the church website.</p>
<h2>What Web Geeks Care About</h2>
<p>If you're using a CMS (Content Management System), he'll want to know a few things about the platform before getting started:</p>
<p><strong>Control Panel.</strong> How easy is the "back end" to work with? What settings can he change from the admin panel itself? Simply put, what can Tom tweak without having to dig into the guts of the system. At the same time, Tom doesn't want something wimpy. The control panel has to be more than just a WYSIWYG editor!</p>
<p><strong>User Roles. </strong>In some settings, Tom will be working with other people to ensure the site is running in tip-top shape. Can he easily assign user roles to other people (e.g. admin, editor, user, etc.), controlling the level of content they have access to? (Ekklesia 360 has this nifty little feature.) If Tom is responsible for the upkeep of the site, he wants to ensure any changes made, content or otherwise, are approved by him first.</p>
<p><strong>FTP Access.</strong> Tom will want to know if he can work with the site at the FTP level. FTP (file transfer protocol) simply means users who have access can log in and play with files and code at a base level. Think of FTP as mixing the concrete for a house's foundation. Tom digs access, so having the ability to do this is key.</p>
<p>For instance, when Monk clients request this feature, it allows them to edit the files that power the layout and design of their site. (FTP access also provides them access to advanced CMS modules such as Monklets and Templates, which is where things really get fun!)</p>
<p><strong>Codebase Access.</strong> Warning: highly specialized web geekery talk ahead! If Tom is of a particular techie type, he'll want the ability to create code he can plug in to your chosen CMS. Officially it's called "application programming interface," or API. Unofficially, it's the ability to take a technology product and customize it to your liking. Think of it as a synergistic online version of "Pimp My Ride". Yeah, like that.</p>
<p>I'm going to throw a few terms under this category Tom also cares about. The first being "proprietary," the second being "open-source."</p>
<p><strong>Proprietary:</strong> Roughly speaking, Tom would use this term if he's referring to a company's product. (For instance, Ekklesia 360 is MonkDev's proprietary software.) When a company develops a solution, it's theirs.</p>
<p><strong>Open-Source:</strong> When a website solution is open, it means anyone can make changes to it. It's a little more complex than that, but in essence, you can contribute to the development of an open-source solution in one form or another. Ekklesia 360 is a closed system, but there is an API (see above) to let Tom make certain changes if he'd like.</p>
<p>Of course, an open-source solution like WordPress comes with the challenge of maintaining code and upgrades all by your lonesome. We've seen some nasty situations where volunteers maintaing a church's open-source website essentially take it hostage. Ekklesia 360, by contrast, is maintained by our ministry-focused team, letting churches focus on creating great content for their people.&nbsp;</p>
<h2>Conclusion</h2>
<p>Tom is a doer. He wants to work with a team to build the best solution possible for his church. These are some the things he cares about. If you work with a Techie Tom, it would be helpful to know</p>
<p><strong>If you do nothing else:</strong> What are some of the other technology needs Tom is concerned about?</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/InMpLOrsidI" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-church-website-technology/</feedburner:origLink></item>
<item>
  <title>What Every Web Geek Needs to Know About Building a Church Website</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/XPSj2qdxh-U/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-building-a-church-website/</guid>
  <pubDate>Tue, 09 Apr 2013 21:02:36 GMT</pubDate>
  <description />
  <content:encoded><![CDATA[<p>Different people need different things out of your church's website.</p>
<p>While this is true at a user level, it's also true at a staff level. No matter who you have on your team, or where you fall in the chain of command, getting the church website up and running truly takes a village.</p>
<p>Last week <a href="http://www.monkdevelopment.com/blog/everything-you-need-to-know-about-building-a-church-website/">we told you about a new series</a> on the blog called "Everything You Need to Know About Building a Church Website." We'll be giving you a guide for working on a website with any and all personality types.</p>
<p>This week we're focused on dishing the dirt about Techie Tom.</p>
<p>Tom is a doer. He fixes anything and everything that has to do with church computers. He changes settings on servers, sets up email accounts, and troubleshoots when the office printer doesn&rsquo;t work.</p>
<p>Tom will most likely be asked to take any tech product the church invests in out for a &ldquo;spin&rdquo; to see what it can do. He cares deeply about the church website, focusing on the granular mechanical details rather than how it looks.</p>
<p>Stop right there. Pause for a moment and get someone in mind for the Techie Tom persona. This is going to be a lot more fun if you have a face for Tom. (It doesn't haven't to be a male, either. Just someone who embodies the characteristics described above.)</p>
<p>Got it? Good. Here's a little bit more on our pal Tom.</p>
<h2>Tom's Daily Tasks</h2>
<p>Tom's "official title" can include anything from "webmaster" to "tech director" to "director of technology" to "IT guy." His talents are wide and varied.</p>
<p>Here's a spectrum of responsibilities, listed from smaller church environments to larger, to give you an idea of Tom's daily tasks. In small contexts, Tom can be found doing one (or more) of the following:</p>
<ol>
<li>Onboarding new staff with phone, Internet, email, computer, etc.</li>
<li>Updating computers with new software releases</li>
<li>Works on the backend of the website</li>
<li>Build multimedia capabilities of the website</li>
<li>Technical administration and help desk support for the staff</li>
</ol>
<p>In larger contexts, Tom does these things:</p>
<ol>
<li><span style="font-size: 14px; line-height: 23px;">Reviews church data and presents it to church leadership<br /></span></li>
<li><span style="font-size: 14px; line-height: 23px;">Makes decisions based on data</span></li>
<li><span style="font-size: 14px; line-height: 23px;">Pulling and running technical performance reports and troubleshooting problem areas</span></li>
<li><span style="font-size: 14px; line-height: 23px;">Maintaining the ChMS (Church Management System)</span></li>
</ol>
<p><span style="font-size: 14px; line-height: 23px;">This list certainly isn't exhaustive, but it does provide a range of Tom's daily duties given the context he finds himself in.</span></p>
<p>If you come across Tom in the wild, he'll be seated behind a computer screen, usually with a frantic staff member at his side screaming, "all I did was download this one little file and my whole computer went berserk!"</p>
<h2>Tom's Main Responsibilities</h2>
<p>As it pertains to the website, Tom focuses on keeping things going on the "guts" level. Backend servers, software updates, building website multimedia capabilities&mdash;this is what Tom lives for.</p>
<p>As with anyone technically-minded, Tom falls into the <em>de facto</em> tech support role. He may or may not like this role and he may or may not let you know his opinion. Kind of like this:</p>
<p><iframe width="540" height="405" src="http://www.youtube.com/embed/ETYThmhPLRc?rel=0" frameborder="0" allowfullscreen=""></iframe></p>
<h2>What Tom Needs in a Website</h2>
<p>Tom wants to make sure the church is spending money only when it needs to. Tom is concerned about having all the necessary technical resources for the church (e.g., bandwidth, server space, etc.) as it pertains to the website.</p>
<p>He needs to have clear technical documentation of what any third-party website provider offers. He'll be using this documentation in discussing website options with other key staff leaders.&nbsp;True to his "doer" nature, Tom likes to be involved in the website buying/building process.</p>
<p><strong>Conclusion:</strong> Know anyone like that? Should we add anything to the list of Tom's characteristics?</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/XPSj2qdxh-U" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/what-every-web-geek-needs-to-know-about-building-a-church-website/</feedburner:origLink></item>
<item>
  <title>Everything You Need to Know About Building a Church Website</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/sxkzMa5qwJk/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/everything-you-need-to-know-about-building-a-church-website/</guid>
  <pubDate>Tue, 02 Apr 2013 16:35:13 GMT</pubDate>
  <description>I was at a conference not too long ago where the instructor talked about "Saddleback Sam." Sam is one of the most influential people at Saddleback Church. He's involved in many of the major decisions and is constantly on the minds of the leaders at Saddleback.</description>
  <content:encoded><![CDATA[<p>I was at a conference not too long ago where the instructor talked about "Saddleback Sam." Sam is one of the most influential people at Saddleback Church. He's involved in many of the major decisions and is constantly on the minds of the leaders at Saddleback.</p>
<p>Only Sam doesn't exist. At least, not physically. He's a persona the good folks at the church developed to typify their average attender. When decisions need to be made, the question arises, "how would this affect Sam?" Here he is for your point of reference:</p>
<p><img src="http://d305057cc27ddd3811ea-f956112674501ff644933e3baa18005a.r38.cf2.rackcdn.com/uploaded/s/0e1459961_saddleback-sam.jpg" width="550" height="815" alt="Saddleback Sam" title="Saddleback Sam" style="margin: 10px auto; display: block;" /></p>
<p>The leadership team at Saddleback wants to ensure their decisions aren't being made in a vacuum. This is why Sam is profoundly helpful. It puts flesh-and-blood to a very large community. Putting a face on a crowd is a smart way to keep your community front-and-center.</p>
<p>I'm sure Sam has his limitations. A single characterization can't accurately describe an entire congregation. But the point isn't to describe <em>everyone.</em> It's to typify what a person attending Saddleback thinks, cares, and dreams about. (There's also a Saddleback Samantha, but I couldn't find her in similar diagram form. I'm sure she's pleasant, though!)</p>
<h2>Profiling the Concerns of Church Staffers</h2>
<p>We're starting a new series on the blog called "Everything You Need to Know About Building a Church Website." No matter who you have on your team, or where you fall in the chain of command, we want to give you a guide for working on a website with any and all personality types.</p>
<p>Much like "Saddleback Sam," we'll profile the following types in the weeks ahead:</p>
<ol>
<li><span style="font-size: 14px; line-height: 1.7;">Techie Tom </span></li>
<li><span style="font-size: 14px; line-height: 1.7;">Communicator Connie </span></li>
<li><span style="font-size: 14px; line-height: 1.7;">Executive Pastor Ernie</span></li>
</ol>
<p>The goal is to show you what each person is concerned about and how to facilitate discussions with each one. If you're on a church staff and need to get a website updated, refreshed, or built, you won't want to miss this series.</p>
<p>We'll start with Techie Tom next week. But just so you're not chomping at the bit, here's a little preview of what we'll be unpacking:</p>
<p style="padding-left: 30px;"><em>Tom is a doer. He fixes anything and everything that has to do with the computers. He changes settings on servers, sets up email accounts, and troubleshoots when the office printer doesn&rsquo;t work. He&rsquo;ll most likely be asked to take any tech product the church invests in out for a &ldquo;spin&rdquo; to see what it can do. Tom cares deeply about the church website, focusing on the granular mechanical details rather than how it looks.</em></p>
<p>Know anyone like that? Are <em>you</em> a Techie Tom? If so, what's the best way to work with your personality type when tackling the building of a website?</p>
<p><strong>Conclusion:</strong> Do you have a "Saddleback Sam" for your church? Should all churches build personas like this?</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/sxkzMa5qwJk" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/everything-you-need-to-know-about-building-a-church-website/</feedburner:origLink></item>
<item>
  <title>Free Executive Summary for the 2012 State of the Church Online Report</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/ngWlRyg39yc/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/free-executive-summary-for-the-2012-state-of-the-church-online-report/</guid>
  <pubDate>Tue, 26 Mar 2013 20:07:03 GMT</pubDate>
  <description />
  <content:encoded><![CDATA[<h2><a href="http://www.monkdevelopment.com/free-download-executive-summary-2012-state-of-the-church-online-report/"><img src="http://d305057cc27ddd3811ea-f956112674501ff644933e3baa18005a.r38.cf2.rackcdn.com/uploaded/m/0e1459865_march-580x125.jpg" width="580" height="125" style="margin-top: 10px; margin-bottom: 10px;" /></a></h2>
<h2>Executive Summary for State of the Church Online Report</h2>
<p>Every church has different personas that make up the congregational body. Each of these personas&mdash;New Visitor, Return Visitor, Engaged Member, and Mature Disciple&mdash;all need different things from portions of the church website.&nbsp;<span>Creating a website where participation occurs is something we call Mission Process Design: intentionally crafting an online discipleship path for users.</span></p>
<p>Based on data that has been gathered from 50 churches, large and small, urban and rural, and every denomination spread across the United States, it is safe to say having an interactive online community is vital to the life of a church.&nbsp;</p>
<p>Continue reading the executive summary for the upcoming 2012 State of the Church Online report. Download it for free here: <a href="http://www.monkdevelopment.com/free-download-executive-summary-2012-state-of-the-church-online-report/">2012 State of the Church Online Executive Summary.</a></p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/ngWlRyg39yc" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/free-executive-summary-for-the-2012-state-of-the-church-online-report/</feedburner:origLink></item>
<item>
  <title>Profiling Church Website Personas: Engaged Member &amp; Mature Disciple</title>
  <link>http://feedproxy.google.com/~r/monkdev/blog/~3/_3s2x4cIrZU/</link>
  <guid isPermaLink="false">http://www.monkdevelopment.com/blog/profiling-church-website-personas-engaged-member-mature-disciple/</guid>
  <pubDate>Wed, 20 Mar 2013 16:19:09 GMT</pubDate>
  <description>Every church has different personas that make up the congregational body. Each of these personas—New Visitor, Return Visitor, Engaged Member, and Mature Disciple—all need different things from portions of the church website.</description>
  <content:encoded><![CDATA[<p>Every church has different <em>personas</em> that make up the congregational body. Each of these personas&mdash;New Visitor, Return Visitor, Engaged Member, and Mature Disciple&mdash;all need different things from portions of the church website.</p>
<p>We started profiling these personas <a href="http://www.monkdevelopment.com/blog/profiling-church-website-personas/">last week here on the blog</a>, so today we want to finish out the group with Engaged Member and Mature Disciple.</p>
<p>Again, we'll be revealing what our research shows as the most important sections for each of these two groups. Understanding the needs of each group is a critical path for creating an effective church website.</p>
<h2>Engaged Member</h2>
<p>An engaged member is someone who's been at the church for over two years but no more than ten. They'll be familiar with the church, the community, programs, and events the church offers. They'll want to know things like:</p>
<p><strong>Event Registration.</strong> How do they sign-up for classes, events, and programs on your website? This group showed the highest demand for an easy-to-use online registration process. Like the other groups, the website is most helpful to them in facilitating connection to the community.</p>
<p><strong>Email Newsletter.</strong> Engaged members want their information delivered via email. Make sure there are easily identifiable places on your website to sign-up for e-blasts. (You do have those in place, right?)</p>
<p><strong>Facebook Fan Page.</strong> Because engaged members are familiar with the church, they're looking to connect relationally with other members of the community. More than any other social network, Facebook emerged as a front runner for this specific group. Judging by the data, if you were to poll your Facebook community on how long they've been attending your church, most of them will have been there for 2+ years.</p>
<h2>Mature Disciple</h2>
<p>We're defining "mature disciples" as community members who have been at the church for 10+ years and self-identify as a Christian. Simply put, these are your "go-to" people; the folks you couldn't do ministry without!</p>
<p>Here's what interests mature disciples most on your church's website:</p>
<p><strong>Text Updates.</strong> Although this isn't a distinct function of a church website, mature disciples were most likely to indicate a strong preference for receiving informational text updates from the church. You can facilitate this connection by offering simple ways for members to sign-up for text updates on your church website. Services like <a href="http://jarbyco.com/">Jarbyco</a> and <a href="http://tatango.com">Tatango</a> are helpful when considering how to do text updates.</p>
<p><strong>Small Groups/Home Groups.</strong> Not surprisingly, mature disciples wanted to know where to access information specific to small groups. Although this element of church life is important for all personas, mature disciples seem to be seeking out this information more than any other group.</p>
<p><strong>Email Newsletter.</strong> Again, the longer someone attends a church, the more likely they are to opt-in to email updates. Relationships are formed, ministry allegiances are fortified, and people want to know what's going on in the life of the church. Much like the engaged members, mature disciples proactively seek out information. Make it easy for this group to find email updates.</p>
<h2>Conclusion</h2>
<p>Community life is at the center of both of these groups interaction with the church website. The more you can facilitate specific connections to the community for these two groups, the more successful your website will be.</p>
<p><strong>If you do nothing else:</strong> Please <a href="http://monkdevelopment.com/news">join our newsletter</a> to receive exclusive access to our next white paper report, "2012 State of the Church Online."</p><img src="http://feeds.feedburner.com/~r/monkdev/blog/~4/_3s2x4cIrZU" height="1" width="1"/>]]></content:encoded>
<feedburner:origLink>http://www.monkdevelopment.com/blog/profiling-church-website-personas-engaged-member-mature-disciple/</feedburner:origLink></item>
</channel>
</rss>
