AKMA's Random Thoughts

July 15, 2003

Technology for Congregations Part Two

In yesterday’s post and the comments that hang thereon (again in response to interlocutory friend Danya), I ventured toward a description of what congregations ought to be doing online. Before I get to that stage, though, I should add a note or two about the “why” part of the enterprise.

Namely: almost every congregation already has a web presence of some kind or another. The phone number is probably available online. A denominational center lists the address, phone number, and leaders’ names. Congregants may refer to their congregation online. News reports mention congregations. A parish that decides to disregard the Web isn’t therefore absent from the Web — it’s ceding the Web to what others say about the congregation. Moreover, it’s practically putting a “We’re clueless and uninterested” sign out to potential congregants who use the Web to sound out spiritual homes. “Please go away and don’t bother us” doesn’t communicate a congregational ethos I’d commend to anybody.

Although the community’s relation to any given congregation usually begins and ends with the facade and signposts, that same congregation can offer a sense of its identity and ethos that radiates through the walls by constructing a web site that reflects those characteristics. Resist the temptation to devise an illusory ideal identity! That’s not only not conversational, it’s manipulative and self-defeating. Anybody who spends a few days in the bosom of Congregation Simchat Torah or St. Willibrord’s Church will find out, without much effort, what the congregation’s priorities and sentiments are like. It’s the on-way, broadcast model of communication: since no one’s likely to buy air time to run commercials that say, “Don’t believe what Congregation Simchat Torah says about itself!” boradcast advertisements tend toward a sales pitch rather than mutual learning.

The more candor you can turn loose on a congregational web site, the better people will know the congregation, for better or worse; that exercise alone may make it worth building a conversational web site. If it turns out that the conversation turns acrimonious, if it engages nobody’s attention, the congregation benefits from knowing that. I don’ suppose that a congregational web site only serves its function if it’s a dainty, pretty, happy representation of the community. Indeed, (again), I hope that no congregation would devise such a site unless they turn out to be a dainty, pretty, happy community. Starting a congregational conversation online opens up a tremendous means for collective self-discovery.

If the site includes writings from congregational leaders, they’l benefit from feedback from both congregants and community. At the same time, visitors will have the opportunity to learn what the leaders of St. Willibrord’s have to say; maybe it would be worth coming to the synagogue to meet them, or ask them about the spiritual dilemma you’ve been wrestling with.

That all entails standing out in public, with all our charms and deficiencies, and taking the accolades and brickbats that come from letting the world know what we’re really about. That may be risky — and I’ve talked about that already, and will revisit the topic — but this is not a new risk, it’ a risk the roots of which have been hidden by the relative difficulty of finding out in person about our congregations. I think that would make a good Part Three.

Posted by AKMA at July 15, 2003 01:06 PM | TrackBack
Comments

Okay, see my comment #2 on yesterday's post. To recap, I think it's a great idea, but it does require getting around congregational egos and fundraising agendas, and may involve some of the Official People Of The Congregation desperately trying to do spin control re: the postings of its audience. AKMA, if you can figure out how to get around THAT, let me know--I may have some work over here in Jewy Jewville for ya.

Posted by: Danya at July 15, 2003 10:51 PM

One small comment related to experiences making our parish web site happen is over maintaining freshness of the 'factual' content. It has taken several years to get to the point where the parish office workflow makes the calendar, notice sheets etc appear automatically on the web site. While I agree 110% about expressing the 'voice' of the congregation, the hygiene factors are also important, and I'd suggest a web site that says "out of date" is almost as harmful as no web site at all...

Posted by: Simon Phipps at July 16, 2003 07:59 PM

Since the Heap has no definite rules as to where it will create space for you, there must be some way of figuring out where your new space is. And the answer is, simply enough, addressing. When you create new space in the heap to hold your data, you get back an address that tells you where your new space is, so your bits can move in. This address is called a Pointer, and it's really just a hexadecimal number that points to a location in the heap. Since it's really just a number, it can be stored quite nicely into a variable.

Posted by: Tobias at January 13, 2004 12:17 PM

But variables get one benefit people do not

Posted by: Benedict at January 13, 2004 12:17 PM

Since the Heap has no definite rules as to where it will create space for you, there must be some way of figuring out where your new space is. And the answer is, simply enough, addressing. When you create new space in the heap to hold your data, you get back an address that tells you where your new space is, so your bits can move in. This address is called a Pointer, and it's really just a hexadecimal number that points to a location in the heap. Since it's really just a number, it can be stored quite nicely into a variable.

Posted by: Bridget at January 13, 2004 12:17 PM