What would you find on Jesus' website?

In the second part of a series on website content, we will discuss questions that arrise based from the premise "If Jesus Had A Website..." in order to better analyze approaches and expectations of church website content.

 


When we asked "Why would Jesus have a website?", we found that that there were two main purposes for having a website:

  1. Creating a place for existing members to keep up-to-date on church events, announcements, and other information.
  2. Reaching out to non-members.
Keeping both these purposes in mind, we must also carefully decide what sections we would like to have in our website. To begin with, there are some key sections that should always be addressed on a church website:

 

  • Welcome - Every church should have a greeting section to their website, and it should probably be the first thing a visitor to your website reads. Typically, this welcome is directed towards non-members, but it's probably a good idea to keep it light and informal to make it inviting to all.
  • Contact Information - Members and non-members alike will need to have access to contact information, including, but not limited to, the church's address (street and mailing if needed), phone number, and e-mail. Directions and a map are strongly recommeded as well.
  • Church History - You should probably include a brief history of your church for non-members. Some people like to know what kind of environment they are getting into, and the church history is a good way to see that. Is it a new, budding church, or is it long established as part of the community? What are the major milestones in the history church? Just as each church is different, each visitor to your site is looking for different things in a church, so present them with the information they need to make an informed decision whether your church is the right one for them.
  • Ministries - A listing of ministries that your church provides or is involved in, along with a brief discription, is an essential tool for both members and non-members. For members, it provides a directory of different services provided by the church as well as groups to get involved with. For non-members, a collection of your church's ministries is a clear indicator of the priorities and passions of the church.
  • Pastor's Page - Every church website needs a place for the current pastor/reverend/father/etc. to introduce themselves to non-members who may be curious about your church's leadership. In the case of a change in this leadership, this page can also be important for existing members as well. Encourage your pastor to make this space their own.
  • Vision Statement - Once you've covered where your church as been and where you are now, it's important to address where your church is going. What are the ideals of your ministries? What role does your church want to play in the community? What services would you like to provide as a church in the future? Again, these can be key points for a non-member who is looking for a new church, or someone who unsaved in search of Truth. These also provide a defined set of goals for members of the church to refer to as well.

Make sure these sections are a part of your site, as they include the information that is most likely to be requested by a visitor to your site.

While this information builds a good structure for your website, if only this information were available it would seem kind of barren. In the next segment of this series, we'll discuss some of the other sections you may also want to include in your website that can provide a sense of liveliness to your church's site. Stay tuned!

Why would Jesus have a website?

In the first part of a series on website content, we will discuss questions that arrise based from the premise "If Jesus Had A Website..." in order to better analyze approaches and expectations of church website content.


So, why would our savior have a website?

Would He have a Blog to tell friends and family how His day went and what was bothering Him at that point in time? Probably not. How about a collection of links to all the neat stuff He's found online? Doubtful. Maybe He'd start a business selling WWJCD bracelets? Nah.

Just as Jesus went out into the real world to spread the Word of God and prepared his disciples to do likewise, today Jesus would be reaching out into cyberspace to spread the Word of God online. He spent His time on earth teaching the people he encountered about the ways of God, and then preparing them and comissioning them to go out into the world and share the gospel.

Even in this basic realization, we can see that a church website must serve double duty. It must reach out to the lost and encourage a search of Truth, as well as strengthen and connect those who have already come to Christ.

At one point in time, it was thought that a church website was effective enough if it listed the name of the church, where it was located, service times, and maybe a few blurbs about the pastor and major activities. However, in today's internet atmosphere, where people have greater expectations for all sites thanks to the increase in user participation within the web community, this basic information is not enough. Without addressing needs of the lost as well as the saved, many church websites will flounder and potentially even fail completely.

Creating a balance between these two goals is also a difficult task. If we create the site to be too "Member Friendly", then we will not devote enough attention to those who may be seeking. If we commit too many resources to reaching out to non-Christians, then existing members and fellow Christians will not participate to grow an online community for your church. We want to strive for the goal of creating a site where non-Christians can come and begin to quench their thirst for truth, as well as create an active community of believers. After all, is this not what Christ demonstrated to us in his life?

Handling these two assignments does take a lot of time and effort, which should help emphasize their importance for your church website. Thoughout the rest of this series, we will be addressing the key aspects of effective website content. Among other issues, we'll address:

  • what should and should not be included
  • the importance of tone
  • audience considerations

If you have any more suggestions for topics that you'd like to see addressed in the coming weeks, please contact us at webmaster@ifjesushadawebsite.net.

State of the Website Content: Static vs. Dynamic

For all webmasters, one of the key decisions to make when implementing a website is whether content of the site will be of a static or dynamic nature. The reason this decision is important is because it will influence every design decision you make from here on out for the site. Neither way of presenting content is wrong, but each each manner has it's pros and cons to take into consideration.

Static Content

Static website content means that the content of the web page is saved to disk within the page's display information, and the page is passed to the requesting browser without alterations. Typically, static pages are designed solely in HTML (HyperText Markup Language), which defines the framework in which the content will be viewed. Since this article is geared towards webmasters, we'll assume that you're already familiar with the majority of the language.

PROs:

  • All web hosts support the use of HTML.
  • Pages will produce identical output whenever and wherever they are loaded.
  • Static content is extremely easy to test in the development stages, helping prevent errors.
CONs:
  • All content changes must be made directly to the file on the web host's server.
  • Content changes must be made by someone familiar with at least the basic workings of HTML (often leading to a greater burden on most webmasters).
  • Some popular dynamic features, such as forums and interactive calenders, are very difficult to implement in a static environment.

Dynamic Content

Dynamic website content is content that inserted into a display framework by a program or script when the page is called by a requesting web browser. This can be as simple as a counter or current date and time information, or as complex as custom user management and interfaces. Many of these scripts work together with HTML in order to produce robust and flexible content possibilities. Most web sites with dynamic content also rely on the use of a database as well, which is used to store the information for retrieval.

One of the nice features of using dynamic content is the ability to update content in a database through the web interface. This allows individuals who may not be familiar with the formatting tags of HTML to easily update information that will be posted on the site. While the initial preparation of these tools may take a substantial amount of time, once they are implemented, very little upkeep is required on the part of the webmaster.

In order to implement dynamic website content, you will need to select a program/script and a database server to work with. You will find that many web hosts will provide hosting packages that combine at least one program or script along with a database to use for storing content. Some of the common options include:

  • Programs/Scripts
    • Active Server Pages (ASP) - ASP is Microsoft's server-side scripting language that is typically paired with IIS on computers running some version of Windows
    • ColdFusion - ColdFusion is Macromedia's tag-based programming lauguage for writing internet-based applications
    • JavaScript - JavaScript is an object-based scripting language that is used for web applications as well as other projects
    • PHP - PHP is a general-purpose scripting language best suited for web development.
  • Database Servers
    • Microsoft SQL - Microsoft SQL Server is the software giant's primary and most powerful database tool, and has a number of useful management applications that accompany it.
    • MySQL - MySQL is a free, Open-Source database server for which there are a number of 3rd party management application.
    • Oracle - Oracle is an extremely powerful database server that is distributed by the world's largest enterprise software company.

In the coming weeks, we will be addressing the differences in each one of these alternatives in more detail so that you can find the one that best fit your needs. However, the use of dynamic website content typically has the following strengths and weaknesses:

PROs:

  • Separation of the content from the design framework of the page, allowing for more flexibility.
  • The ability to create powerful custom tools for the management and presentation of your site, or implement pre-made packages that can be altered to fit your sites needs.
  • Most web hosts provide one or more of these tools along with their standard hosting packages, meaning no extra costs for you!
CONs:
  • There is a substantial learning curve for these dynamic languages/scripts and database servers.
  • Due to the use of dynamic content, there is more greater chance of errors occuring if content is not handled properly, so more development is required.
  • The use of additional applications may require more upkeep of the site's framework.
The vision you and your church or group have for the site and the resources you have available will greatly impact the decision of how you want to handle your content. Static web content is still the standard for many pages on the web. However, with the growth of user participation in the web leading to the flourishing of dynamic content on almost every major site, I recommend trying to work towards the dynamic approach. Not only will you be able to have a database record of everything on your site, but you will be able to port that content between languages/scripts over time if need be. While it does require more time and effort, the rewards are well worth it!

BlogCFC was created by Raymond Camden. This blog is running version 5.9. Contact Greg