New Site - First Baptist Church of Wichita, KS

Events happening in the community are now at Drupal community events on www.drupal.org.
boyfly's picture

After 18 months of volunteer development work we launched a new website for our church, First Baptist of Wichita, Kansas. It was a great learning experience and we are all big fans of Drupal as a result. Comments and/or questions are welcome!

The site is at http://fbc-wichita.org

The site was built with Drupal 6. The theme was built from "scratch" starting with the blank Zen theme. Modules in use are:
Audio - for importing sermons
CCK & Views - used in a couple places but not as much as we probably should have
Path - to make nice URLs!
Taxonomy - for sorting audio files and other stuff
GCal Events - for the front page "Events" sidebar
GMap - for the location map
Contact Forms - for individual contact forms
Dynamic Display Block - for the frontpage slideshow
Dynamic Persistent Menu - for the main drop-down menu
SimpleMenu - for a clean, out-of-the-way admin and user menu (only for authenticated users)
Google Analytics - for site statistics
Wysiwyg - for more simple content editing

Comments

nice site

esbon's picture

Is it my Internet or the site is very slow.

site speed

Branjawn's picture

Site works fine for me.

I really like the layout and all design aspects. Can you speak more as to how many people were involved and what kind of response you are receiving from your congregation?

I volunteered to create a site for my church that just launched this month. There's a lot of complaining from older folks and it's a one man show so I don't have anyone to take some of the work load from me. I'm curious as to how other churches do it.

We were fortunate to have a

boyfly's picture

We were fortunate to have a number of talented people to work with, all members of our church and most of them professionally trained for each of their roles. Our team consisted of 6 people:

2 Content Writers
2 Web Programmers
1 Graphic Designer
1 Photographer

With the launch of the site we created some user roles that give permissions to edit certain parts of the site. Staff from around the church were then assigned these roles and trained to maintain the site.

So far the response from the congregation has been great. This site is a HUGE improvement over their previous site, plus it adds some neat abilities such as streaming the sermons online and dedicated pages for our various congregations. So far we have not heard any negative comments.

menus

Branjawn's picture

One more thing, how did you make the cool menu with the second level appearing underneath on mouseover? Really smooth stuff you have going on there!

And who did your logo design? Was that in house? It's genius. I know I shalt not covet, but I wish I was on the team at your church! :P

We used the Dynamic

boyfly's picture

We used the Dynamic Persistent Menu module.
http://drupal.org/project/dynamic_persistent_menu

If I remember correctly, the only modification we made to the module was that we force it to display the related submenu if the page you are currently looking at is a part of that menu.

I need to go read the fine print on a stone tablet...

cliff's picture

Boyfly, I need to find out if I'm breaking the Tenth Commandment by coveting your team. I wish I had even two helpers who understood that a website is more than a picture of the church with links to one page for each committee. Also, I would love to have a congregation that's willing to participate in all the activities involved in developing an effective site.

You and your team have done a marvelous job. I like that your design is distinctive enough that all the WordPressers can't recognize it as a Drupal site right off the bat.

I do have two recommendations for improvements, though:

  • Adding another footer. The University of Prince Edward Island, in telling about re-theming their site, mention (scroll down to the h3 "Footer") that they discovered that a footer with tons of links in it worked amazingly well. Check out the UPEI site and see what you think. I get the sense that it was out of frustration that they came up with this answer — nothing else worked, so why not? What would I put in such a footer for your site? I would start by repeating every link in your primary and secondary menus (by "secondary," I mean the ones that appear on rollover), except for "Home" and "Contact." In this footer, I would make each of the remaining five primary items a column head, and put its respective secondary items beneath it. In a sixth column, I would have the Login link, then links for RSS, Twitter, Facebook, and so on, and perhaps a link back to "Home" at the very bottom. Except for the Login link in column 6 and your copyright statement (which would go at the very bottom of the page), I think I would leave everything else in your current footer just as it is, above this new footer. One advantage of this approach is that, without being ostentatious, it puts a "Give" link on every page. Imagine how frustrating it can be to learn from the site of a nonprofit that you would love to support what it does, but to not be able to find a link that will let you do so. These informative footers aren't that common. I've seen them done well (I think UPEI's qualifies as "done well"), but I've seen them done poorly (and I'll let those sites remain anonymous, mainly because I can't remember where they were). So don't wreck your site to add it, but do think about it.
  • I'm still learning to build calendars myself, but I would see about developing a way to filter the view. It would be great to let the user choose to see only the events for young adults, or events for children (and their parents!), or just committee meetings, and so on. This feature would also alleviate the visual clutter the calendar of any healthy church produces. If I figure out how to do this, I will add a post to the "Churches" group. I guess I should start by searching for the answer — maybe the solution is already published somewhere on drupal.org.

I'm really impressed with your site. You've set a high standard for the rest of us to emulate.

Thanks for the constructive

boyfly's picture

Thanks for the constructive feedback. I like it.

I like the idea of a footer with all the links in it. I've seen them around the interwebs. Something in the back of my mind has been to figure out a way for the site to be usable on mobile devices because the current drop down menu is sketchy at best with touch screens. I think an expanded footer would solve that problem in addition to the other benefits you listed. My biggest problem is that the graphic designer almost certainly will not sign off on it... we will have to work on her.

I'm not real happy with the calendar, but the Google calendar integration was the simplest way we could implement a robust calendar that can be maintained by the church office. We do intend to split it up into different sections (each with their own calendar, selectable at the top right of the page), but the holdup right now is just the "information overload" for the office staff. They are getting the hang of using Google calendar and we will continue showing them how to do more and more with it as time goes on.

One other thing I'll mention

boyfly's picture

One other thing I'll mention that is related to the footer with links... I was concerned when creating the site's menu that people would click the top level of the menu before realizing there was a drop down and then would never bother to explore the second level of the menu. The analytics report is showing that this is not a problem as the majority of pages being visited are a part of the menu's second level.

You're probably OK for mobile

cliff's picture

I did a little more playing around on your site and rereading of information on usability and accessibility, and I realized that there is one feature of your secondary menus that is contributing to their success:

  • Each of the middle five items on your primary menu produces its own secondary menu on hover.
  • People who navigate by keyboard or some other tool other than a mouse cannot access these items. People who use screen readers will similarly be disadvantaged. Each secondary menu will appear as they progress through the primary menu, but, by the time they get to the block containing the secondary menus, they will have disappeared. So for people doing mouseless navigation (this includes your mobile users as well as people using screen readers), the secondary menus are neither perceivable nor operable. Thus, you seem to have two different accessibility failures in this one feature.
  • But — and this is very important — if they click any one of the items in the primary menu, they go to a page where the corresponding secondary menu is displayed. Although the content of this secondary menu changes if people using a mouse hover over any other item in the primary menu, the original content persists when people who don't use a mouse move through the primary menu. So on the corresponding inside page, mouseless navigators can get to each item on a secondary menu. In other words, what seems to have been a barrier actually is not a barrier at all. Everyone has comparable access to the same information.

You noticed this in your analytical results. People are getting to the interior pages, and I would wager that they are getting there just fine from a mobile interface. They have to take a slightly different path, but they can get there.

The long and short of footers

cliff's picture

Just the other day, Frank Suyker reviewed the advantages and disadvantages of fat footers, as he calls them. There are points to consider both ways.

It's worth a read for anyone who finds themselves having that discussion with a designer or client. Or themselves, for that matter.

Good to know

Branjawn's picture

Yeah, I'm at a smaller church of not too technically savvy folks. And the ones who are more inclined towards that are already up to their necks in ministry demands.

Here's my site: http://www.foc4u.org
I themed custom using 960 grid theme.
It's a work in progress!

Be thankful you have a team! If I woulda known what would be demanded of me I would have made a one page html site! (half kidding)

Menu

Branjawn's picture

How did you get the span with class menu_delimiter in the dynamic menu? Did you insert code you'll have to replicate every time you update the module?

Yes, we did add the

boyfly's picture

Yes, we did add the menu_delimiter span to the module code.

I don't expect to have to update the module often, if ever, as it is working as we need it to.

thanks for the reply

Branjawn's picture

cool. I tried using a background image in the <li> and padding it to allow space for the image. It worked, except it shows up for each item and you have for each but the last.

Anyways, if worse comes to worse I'll add the code like you did, but I'd rather use some css. thanks for the information and taking time to respond.

<*)))><

drupal module for quoting the Bible

daustin100's picture

We have created a drupal module for quoting the Bible see http://labs.bible.org the module is called
NetQuote - Drupal NET Bible Quoting Module
we also have a NETBible verse reference tagger that will popup the NETBible for verse references on your site.
see also our online NETBible study enviroment at http://netbible.org
david austin
exec dir bible.org

Paths

WillBrown's picture

That's a great looking site. Congratulations to you and your team!

I did notice that your links in your Audio section had the default "node" and "term" links in their URLs. Not sure if you forgot to change the paths on those.

Besides that. I'm very impressed. I'm still working on creating a Drupal site for my church.

Will

We allow the audio files to

boyfly's picture

We allow the audio files to import automatically so we don't have to spend time editing them, which results in the paths being somewhat cryptic. I believe the Pathauto module would help in this situation, but we have not looked into it. We do plan to add some search/filter capabilities to the audio section in the future and may address the urls at that time.

Thanks for the comment!

Import automatically?

WillBrown's picture

Could you expand on what you mean by "import automatically"? Are the nodes created automatically when someone uploads an audio file?

If so, how are you accomplishing this? A module or some type of CCK/Views configuration?

Is there a way where I can

rpeters's picture

Is there a way where I can get the theme? I like it or you could put it in the repository, so other people can benefit from your teams work.

Unfortunately, we were not

boyfly's picture

Unfortunately, we were not familiar enough with drupal to understand all the ins and outs of creating a custom theme when we built this one. That means we don't have everything in one place and providing the current theme files would result in a broken site.

At some point we may attempt to put everything where it is supposed to be and then we can provide the theme to the community. I will be sure to let you know if we get there.

In the mean time, the base Zen theme will provide 90% of what you see on our site (minus all the images and colors, of course).

Very Nice, boyfly

whizzbang's picture

I like the graphics and the custom theme. I am not familiar with the Dynamic Display Block module, it looks very nice. I like the way you incorporated the intro text on the left with the images. I use the views rotator module on this site that I built for my church's Young Adult Ministry http://tempuschicago.org
I created a content type of Happenings that allows an image upload. Image cache resizes it and Views Rotator block displays this content type. This site is brand new last week and is still kind of rough. I built it using the zen 960 theme. Took me forever to solve the Nice Menus falling below other divs in IE (I finally added z-index: 10; to the #site-menu div and voila. Two weeks, but finally, ptl! I'll have to look at the Dynamic Persistent module for the drop-down / over menus.
Nice Job.

Alan McColl
http://whizzbangcomputerservices.com
Web Design | Computer Repair | Data Recovery - Migration | Virus Removal

Drupal Churches Home

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week