Search Our Story with Firebird

One of the nice things about writing a weblog is that it becomes a useful resource full of your thoughts and ideas over time–a searchable diary, of sorts. I realized this when I went back to search for something I had written about some time ago and it occurred to me: why not be able to search from my browser the same way I use Firebird to search Google or Dictionary.com? A quick Google search turned up some code to do exactly this.

You, too, can search Our Story right from Mozilla Firebird (and you are using Mozilla Firebird, aren’t you?). Just click the link under the Search box labeled “Search with Firebird.” The link will download and automatically install the search plugin for your browser. Once that’s completed, you can use the handy search box located in the top of the browser window to search this site.

More information:

* Asa Dotzler: finally! searching made easy
* Mark Paschal: Search your weblog with Mozilla

If you’re feeling energetic, you may also want to check out our Templates page to help you integrate such a search into your own Movable Type powered site. Modifications were made to our incSearch and JavaScript templates. A new template, fbSearchPlugin, was added which actually contains the plugin code.

Sasha in the Limelight

Montclair Times: Sasha finds a home. Then came the happy day, in June of this year, when Sasha was finally adopted by a family–Ken and Sarah Walker of Wharton. ‘It was one of the nicest things that happened here in quite a while,’ Young said.

Hey, that’s us. :)

When we adopted Sasha earlier this summer, the staff at the shelter made us promise to let them know how she was doing. So, about two weeks ago, Sarah had sent off some cute photos of Sasha to the kind people over at PAWS. They weren’t the best photos that we had, but we thought they helped convey how much fun we were having with our new pet.

A week later, we get a message on the answering machine from a photographer who wanted to come take our photo with Sasha. Apparently, the email we had sent to the shelter had made its way over to the Montclair Times–they wanted to do a community piece on our adoption! After a few phone calls trying to plan logistics with the photographer, they finally decided to use one of the email photos. We gave some quotes to Mary Anne to run, and there you have it. :)

Sasha has been a huge blessing to our family. Sarah, who absolutely loves animals, has been so happy with a dog to take care of and love. Despite the bad press that pit bulls have, Sasha has been great with people. She loves hanging out in the park, meeting new people, and watching TV (much to our surprise!).

More reading:

* Welcome Home, Sasha — written when we first adopted Sasha
* Gratuitous Pet Photos — photos of Sasha doing, like, dog stuff
* PAWS Website — get one of your own!

Small group training and the ever-present urge to consume

In an effort to better lead Ironworks, Sarah and I decided to attend “Turbo-Training” at the Village Church. The training class is focused on helping small-group leaders sharpen their existing skills and acquire new ones in leading prayer & sharing, Bible study, and worship. Although the training is focused on helping leaders of TVC home fellowship groups, we thought it would be a great fit for helping us learn to lead our New Jersey small group.

Today was the introductory class which offered a fascinating perspective on the Village Church’s philosophy on small groups. Scott Greider–one of the “coaches” for small group ministry–noted that because our church doesn’t own a building in the city, they tend to view small groups as absolutely critical to the health of the church. This struck me as profoundly Biblical. Shortly after the disciples receive the Holy Spirit in Acts 2, the early church was suffering from persecution, making it practically impossible to meet together in a central location. It’s also largely believed that Timothy pastored a few dozen home churches (as opposed to one, monolithic congregation) in Ephesus.

The identity of a church around 50 or 100 AD had to be found in its people, not its stuff.

For whatever reason, the 21st century American church has lost touch with this idea. “Come to our services,” we say. “Play basketball in our gymnasium! Ride in our elevators! Observe our monumental cathedral and participate in our nationally-competing choir! Eat in our Saddleback ShallowCreek®-branded Taco Bell and Pizza Hut! Shop in our three-story bookstore (complete with gourmet coffee shop)! Our 7,500-member congregation is the largest bastion of Christian culture this side of Heaven–surely God is pleased with our elephantine worship services!”

We raise funds for building additions to accommodate ever-greater entertainments. We tear up the ground to lay foundations for Christian mini-malls. We throw concerts to raise awareness for our products.

“Come for the singing; stay for the low, low discount prices!”

But Peter’s church and Timothy’s church had no choice but to be defined by the individual relationships among the Christians. They simply had nothing else to demonstrate before the world–no building funds, no marketing campaigns, no t-shirts.

Just relationships. And having people over a lot.

But the power that was displayed by this unbranded, dedicated group of people! Lives were being changed. Families were reconciling. People were rejecting their stubborn selfishness and replacing it with a concern for the broken-hearted. No one in those budding churches had anything else to occupy their time but caring about and investing their lives in other people.

And, that’s just it, isn’t it? If we’re not taking care of the deep, unspoken needs of people, what’s the point? We’re just another competitor in the marketplace, peddling our wares in the hopes of turning a buck. “To the praise and glory of God!”–yeah, sure.

Sarah and I are so thankful to be attending a church that approaches this truth with integrity. We’re looking forward to see what these next weeks in training have in store for us.

“I was young and I needed the money”
“I had money, and I needed more money”
“I was filthy rich–all I wanted was love. And a little more money…”

Steve Taylor, Cash Cow (A Rock Opera In Three Small Acts)

The Road to Section 508

Well, this was inevitable: Our Story is now Section 508 compliant. That means that people with disabilities are better able to explore this site due to slight tweaks here and there in our code. If this sounds esoteric to you, you might want to check out these links.

Mark Pilgrim: The myths of web accessibility. The next time someone stands up in a design meeting and claims that you don’t have any blind customers, ask them if they care about search engine placement. Then remind them that Google is a blind user who reads the entire Internet every month, and then reports what it sees to millions of its closest friends.

Nic Steenhout: Accessibility: Build it, and They Will Come. I asked Pete to put in a ramp. He then asked me, ‘why should I put a ramp in? You’re the only customer I have in a wheelchair.’ I asked him why he thought that was.

Jim Byrne: This HTML Kills. Anti-discrimination legislation in Britain and in America is increasing awareness of accessibility. The Americans with Disabilities Act makes it illegal for companies offering services on the web to discriminate against people with disabilities. There are already examples of citizens taking action against companies with inaccessible websites.

Section 508, by the way, is a set of accessibility guidelines that are required by government agencies and businesses by law. It’s been in place since 2001. WAI, on the other hand, is a set of guidelines determined by the World Wide Web Consortium–the standards body for the Internet. These guidlines have been a W3C recommendation since 1999.

Accessibility is both easy and hard to do for your site. It’s hard in the sense that retrofitting any website with any new technology is just difficult. This is a huge argument against XHTML and CSS right now–it’s simply too costly to overhaul the site, and who has the money? But, it’s also easy in the sense that, if your site is reasonably well laid-out, it doesn’t take a lot to reach section 508 or WAI priority 1 compliance. The trick is to decide how well-structured you’re going to make your website. If you’re stuck using web design techniques from the mid-nineties, then working towards a well-structured site will not only offer you better accessibility, but less bandwidth used (com’on, you are paying for your bandwidth, aren’t you?) and easier maintainability. Google also rewards well structured pages. No, seriously, it does.

Once your markup validates, taking care of accessibility issues is a lot simpler–there are far fewer errors that come out of the validator, and the ones that do are reasonably intelligible. I recommend checking out Mark Pilgrim‘s online book, Dive Into Acessibility. Going through the instructions there alone got me to Section 508 compliance. A few more tweaks here and there qualified the site for WAI priority 1 accessibility.

Unfortunately, though, that’s as far as I got. The only thing keeping this site from priority 2 accessibility is this problem: “Do not use the same link phrase more than once when the links point to different URLs.” What that means is that there are links on this site that use the same exact text, but point to different places–namely the “n Comments” links. There will be the occassion, from time to time, when two blogs will have the same number of comments and will break this rule for priority 2 accessibility. The Bobby validator would seem to imply that changing the title attribute of the offending <a> tag would solve the problem, but it didn’t. Interestingly enough, another validator, “Cynthia Says” let me off with a warning about repeated link phrases. Hm. Jukka Korpela notes this as being an odd behavior in the Bobby validator–even the W3C home page has repeated link phrases that point to different locations.

For more resources on Accessibility, you may want to check out these links:

* Dive Into Mark: Accessibility
* Jeffrey Zeldman: Accessibility and Section 508
* A List Apart: Accessibility
* World Wide Web Consortium: Web Content Accessibility Guidelines
* Section508.gov

Update: Rather than trying to deal with what otherwise seems like a bug in the Bobby validator, I’ve settled on posting a WAI badge–rather than an AAA badge–on the footer of Our Story. As best I can tell, this site is in compliance with the World Wide Web Consortium Accessibility Initiative, Priority 3.

OBX 2003

What happens when you mix a crazed family of canopy-loving Scots and their loved ones together in the Outer Banks of North Carolina, and it rains all week? Um, not much, but we have photos. ;-)

Speaking of New Features

Well, glad that that‘s settled. It’s been so frustrating having the site down over the past week because there’s so much stuff I’ve wanted to blog about. :)

Vacationing in rainy North Carolina and an over-night Linux install of Apache, PHP, MySQL, Perl, phpMyAdmin, MovableType and all their dependencies (which was actually quite easy with Ximian’s Red Carpet software) enabled me to do some serious blog tweaking last week. It was nice because there were a lot of things that I’d seen around and wanted to do, but just didn’t have the time. So, without further delay:

Our Story now sports a spiff navigational aid: the breadcrumb trail. In order to get the metaphor, click on the permanent link for this entry and look at the navigation bar. Then, think Hansel & Gretel. The code required to put this together was just some clever manipulation of MT Date tags and some good old text links. The cool thing is that this is a site-wide feature, so every page on this site can be navigated “backwards” through a “hierarchy” using the trail. The trail just uses a regular-old <p> tag rather than an unordered-list, but I’m open to encouragement on that. :) Inspiration from Adam Kalsey and Mark Pilgrim, but the real reason I put this together is because we now feature an expanded archives selection.

You can now choose to navigate our archives by date, category, citation, and quotation. The new pages made the site archives a bit cumbersome to navigate, which necessitated a new navigational metaphor. The quotation/citation archive is actually a feature that Mark invented [PG] in his quest to support semantic markup. The citations page lists people (or organizations) that we’ve cited here by the number of citations in descending order. The quotations page lists websites that we’ve quoted by using the cite attribute in the <q> and <blockquote> tags. Pilgrim uses a custom solution that he wrote in Python. It’s taken a while for the blogging community to catch up, but Kevin Shay wrote an MT Plugin that generates these pages called MT Collect. Highly recommended. For information as to how to use this plugin, you could peruse our improved Templates page.

The Templates page displays links to almost all of the templates used to power Our Story. The page features descriptions of what each template does on the site and–here’s a real Ken qua geek moment–the date of the last change to that template. What I did was link some text files to my MT template code, so any time I change a template, its text file is updated automatically. The date on the templates page is generated dynamically with a little PHP that checks the last modified date of the template text file, so I never have to think about it.

I also made some more changes to the Mig Photo pages for user-friendlier layout and to help them conform to the breadcrumb trail structure.

I pulled more hard-coded references to kennsarah.net and “Ken & Sarah” out of the templates and replaced them with the corresponding MT variable tags (this was just necessary to get the site running on my laptop anyway).

Finally, I added a blurb about the Schmoze on the About page.

Whew!

Gender and the Kingdom

The past several Bible studies that I’ve led at Ironworks have had to do with this whole notion of what roles women play in the Christian church. This has certainly been the biggest challenge for me as a teacher and a small-group leader in that it involves tactfully navigating highly contentious issues.

On the one hand, I’m flirting with an idea of equality that would instantly label me as a flaming liberal and considered theologically weak in some circles. For, indeed, the churches that have most quickly espoused complete equality of the sexes, it would seem, have just as quickly unburdened themselves of a meaningful Christology. Gender equality, one would surmise, is a slippery slope that leads inevitably to a flimsy, humanistic theology.

On the other hand, though, I risk being labeled a raging fundamentalist. To even imply that women might not be “equals” with men (whatever that means) will, in the best of situations, raise the eyebrows of some, and, in the worst, raise the ire of others. To espouse such notions would be to take seriously the scribblings of a dead religion that has only sought to dehumanize the race in an effort to maintain patriarchal power structures.

And so it goes. I exaggerate a bit only to bring out the difficulty in trying to find a true, Biblical solution to the question of how men and women function together in the church. Forget social norms for a moment. This is an issue that has been debated for hundreds of years, and I’ve yet to see a compelling argument that summarizes a cut-and-dry solution. Even in my own experience, I’ve seen several different answers to the question of equality: InterVarsity believes in complete equality of the sexes, but they’re a parachurch organization that might not be strictly bound to church dictates laid out by the Scriptures; our old church stratified men and women, determining that women were not fit to teach over men; The Village Church seems to compromise the two by allowing women to participate in every aspect of church leading, short of ordination (becoming a pastor/shepherd). In passing, I’ve also been to a funeral where a woman preached and to a wedding that was conducted by both a woman and man.

Through much prayer and study of the Scriptures in the last two months, I’ve been having a great time uncovering some of the issues and mysteries surrounding this question. It’s also made for exciting opportunities in Ironworks to engage our minds and have great conversation around the issue. I’ve also learned quite a bit about taking risks in leadership. Here are the passages we’ve looked at in the past four studies:

* Acts 18:18-28
* Galatians 3:15-29
* 1 Timothy 2
* 1 Corinthians 11:2-16

Throughout the passages, I’ve tried to maintain an overarching focus on the context of what is being said. Each of those passages have verses that, when taken out of their context, could lead to confusing or heavy-handed beliefs about what women and men should be doing in the church. However, believing that the Scriptures are consistent, our goal at Ironworks has been to read the passages in both the context of the book (i.e. What is Paul saying to Timothy? What are Priscilla and Acquilla trying to accomplish? What other instruction has Paul given to the Galatian and Corinthian churches at this point?) as well as the context of other books (i.e. Do Paul’s words in 1 Corinthians 14 contradict what he said in Galatians 3?). In striving for this level of intellectual integrity, I think we’ve made some great gains in grappling with the question of how gender plays into the Kingdom.

Our most recent study was on 1 Corinthians 11, which, as it turns out, is one of the most bizarre and challenging passages on this topic. I had originally intended to give an inductive study of the passage, but, over the course of my study, found myself drowning in meanings for the passage. I didn’t get it and couldn’t understand how Paul’s words here seemed to negate everything we’d studied up to this point. I had put my fair share of preparation in (about 3-4 hours by Friday afternoon) and still had very little to show for it–it was depressing.

I did remember running across a study online that not only seemed to be a balanced study of the texts we were looking at, but also purported to resolve the dissonance of 1 Corinithians 11. When I went back and found the study (which, in and of itself, was a miracle), it was like a lifesaver had been thrown to me. I was so enthralled with it that I decided to share it with the group in its entirety. My study plan was this: spend 15 minutes doing objective group observations to effectively present the problem of the passage, spend about 30 minutes reading the lesson, and the remainder of the time in discussion.

I told everyone that I would link over to the study that was read for further reflection. As promised, it’s here: The Writings of Paul – 1 Corinthians 11 & 14. It was part of a series entitled “Women: A Biblical Perspective,” which can be found towards the bottom of this page. As far as I can tell, this study was given by a woman named Nancy Giessler, who serves on the elder board at Valley View Community Church, in Audubon, PA. I invite everyone to check out the study that we read and continue the discussion.