To start with:

Let us suggest some starting point ideas. In first place you need to think of what you want, and what your church needs might be regarding a web presence. Just to have a web without defining its purpose is paramount to keeping a horse in a flat. Defining purposes lead us to the right choices when building the website.

Look around:

A good practice is to browse the Internet and look at other churches' or business' websites. You can get a "feeling" from those websites, or you might like the design, or the colors, or the overall structure, and so on. Although our goal is not to copy other people's websites, nevertheless this would give us a clearer picture of what you have in mind. Some times it is much easier to say "I want something like this" than explain in words what you want, especially when it comes to people who have little or no experience with the World Wide Web.

Visibility:

We will provide you with a fully operational website, and also will make sure that your website becomes highly visible in the web, so that it would be very easy to find using a search engine. It will be your responsibility to provide us with accurate information. We will update the website in a timely manner, or eventually provide you with means to add content by yourself.

Internal Accessibility:

This has two sides. On one hand the website has to be accessible and easy to navigate. This side of the coin is mainly our responsibility by building the website in a way that it does not become "clogged" in internet standards, and by suggesting you what materials to put or not to put (for example some fancy add-ons might look like, well...fancy, but they might as well slow down your page to unbearable levels, especially for people connecting via a phone line).

Linked Accessibility

This is the other side of the above coin. Let me use an example, what would be the use of building a sanctuary up on a hill, which everybody could see from afar off, if you do not build a road to get there, or if you build the walls without any doors? This is exactly what happens with many websites which are beautifully built, with state-of-the-art technology, but where you cannot find a straight way to communicate with the real people behind the website. If you or your church people will not be "available" in the above sense, then you do not need a website.

Information:

When people browse to a website they get there because of either curiosity, or they stumble across the site, or they are looking for something. Whichever the case, what they need is information. Your website has to provide exactly that. If all what you put in your church website is a few paragraphs about how good your church is, a few pictures of the building, and the address, not many people would bother to get to your place to check you out. For example, I use to browse the web when I need to buy something, before actually going to buy it, but if the website does not show me prices, I do not care how good their store is, I will not drive up there to check it. A website needs to show who you are, the people, what you are about, how to get in touch. In an overall sense you need to provide people with reasons why they would want to get in touch with you, and obviously the way to get to contact you.

Package Options