| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Mar | Jul » | |||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | ||||
- Changing Church (1)
- Developing a Vision (2)
- Keeping up with our Kids (3)
- Soul Searching (1)
- Uncategorized (1)
- Using a Blog (1)
- Web Site (1)
- 18. July 2008: Confirmation Camp-Thursday
- 16. July 2008: Day 3 at Lutherdale
- 15. July 2008: Confirmation Camp-Tuesday
- 12. July 2008: What does it mean to be a Christian
- 27. April 2008: Crash Helmets & Pastor Hileman's Sermon
- 2. April 2008: Some thoughts about Jean Lunt's Sunday Presentation
- 1. April 2008: Developing a Web site for the church
- 8. March 2008: Hello world!
Blogroll
Developing a Web site for the church
We have decided that we need to beef up our web site, and that this should be a major initiative for this year. We are learning that this will be a complicated process.
Many have thoughts about what should be included, and maybe, what should not. How do you present the church? For whom are is the web site primarily intended? Certainly we think that it should be visitor friendly, but we also know that it should provide members with useful information.
Being late with informaiton or out of date is a serious issue that we will have to address. How do we address that. We have come to realize that depending on one volunteer to post everything is too much for one person. It would be best for multiple people to be able to post, but then one loses certain control issues. Issues such as “are we representing the church, especially for the visitor, with a consistent message” or if linking to other websites, are those sites theologically consistent with the church’s theology.
Other issues will deal with the flow and artistic look of the site. What some people think flows nicely, others will think is cumbersome and difficult. What some people think is important information about the church, others will look at and think is “insider” speak that will disenfranchise the visitor. Some may think we should have less information, but what does that do for the inquiring visitor who is looking for the meat the church has to offer. Even if a primary emphasis is for the visitor, shouldn’t the website be a primary place for people to see if Sunday School is held this week or what time people are needed for the clean up following the rummage sale? There will also be differences of opinion about the artistry. Should we be simple and use two primary colors, or maybe use the pastels with a rolling screen and a calendar link page.
As we work to develop a website, the biggest problems I see are 1) agreeing as to how to put this together and developing a similar philosophy, and 2) providing material to our web designer in a timely manner. Any thoughts as to how to clarify and provide this?
2. April 2008 at 00:52
I like the thoroughness of your summary John.
When agreeing on how to put it together: perhaps having a vote on the options presented, if more than one. My thought is that having a similar philosophy should begin with all involved agreeing on how this project fits our Mission statement. Then perhaps agreeing on the goals.
One way for the responsible individual to get info to the web designer on time, is to partner with another person whose role is only to hold the other accountable for their duties. In a friendly way, of course, set some kind of deadline between the two for submitting material or updates to the designer. As the deadline approaches, the one reminds, calls or encourages the other to get it completed. Just some of my thoughts.
G.