In early 2009, the Archdiocese of Saint Louis determined that it needed to upgrade its website, mostly for security concerns. After investigating a move from Joomla! 1.0.x to Joomla! 1.5.x, the Archdiocese determined it would be more cost effective and a more future-proof decision to migrate the over 49 individual Joomla! sites that comprised www.archstl.org into a single Drupal installation.
This upgrade/migration provides many benefits, not the least of which are a better end-user experience, a better administrative experience, and much improved page load and search indexing performance. In addition, Drupal's structure and content presentation provide much greater flexibility in design and information structure, as well as SEO (search engine optimization) than other popular CMS frameworks that were investigated.

The decision was made early on to partner with a development company that would help with the content migration and initial site buildout. Theming would be done in-house. We chose to partner with Palantir.net, a web development company located in Chicago, IL. After Palantir completed initial site work, I went up to meet them, and also attended my first DrupalCamp (Chicago); Chicago has a much more vibrant Drupal community than St. Louis... but perhaps that will change at some point!

After nearly a year's worth of planning and development, the Archdiocese launched its upgraded website on February 22, 2010.

Server Configuration

The Archdiocesan website was formerly running on a server managed through RackSpace, but costs and configuration restraints prevented us from continuing on a managed server through RackSpace. We migrated all of the Joomla sites to a new dedicated server from SoftLayer, and also migrated a few of our other sites (including the Saint Louis Review - case study on Drupal.org here). Due to caching and optimizations, the server is typically not burdened much, even with a few relatively high-traffic sites running on it.

The server is running the CentOS distribution of Linux, along with Apache, PHP and MySQL. Apache's configuration is set to survive a slashdotting, PHP is configured with APC caching for performance, and the MySQL configuration has been thoroughly tweaked to provide the best performance with the amount of RAM we have in the server.

Modules Used

Like any large website, this Drupal installation used a plethora of modules to enable certain functions and features. Here are some of the more relevant/prominent modules we used:

• Joomla to Drupal: This module saved quite a bit of time and frustration when we were transferring all the content from the 40+ Joomla websites that made up the old archstl.org, and allowed us to easily add content from live site. The module was highly customized by Palantir to help import content directly into Organic Groups. (agentrickard did the lion's share of the work in moving all the databases - he should at least get a cookie for all that work!)
• Table Wizard + Migrate: Palantir helped immensely with regard to a ton of legacy data we use on our website to populate the Parish, Schools, and Organizations directories. Using Table Wizard and Migrate, plus a custom shell script (which runs every morning), we pull in data from various csv files, import them into Views-accessible tables, and then use Migrate to build a node for each organizational entity. (Special thanks to agentrickard and sdboyer for setting this up).
• Custom Formatters: Key to formatting a ton of content pulled from an Archdiocesan database. We used this module to set up formatters for phone numbers, Mass Times, and other miscellaneous data pulled into CCK fields.
• Views + CCK: These two modules were used to build out almost the entire website. All content types use a "body" field provided by CCK (in Drupal 7, this is how nodes are built - there is no more "Body" attached to a node). The Request a Prayer and Bulletin Gateway system are both built on Views and CCK.
• Mapstraction: This module allowed for gratuitous use of Google Maps on nodes (using the Views attach module and node content displays), and in views (using a Mapstraction view attachment). (agentrickard gets another cookie for this).
• Date + Calendar: The Calendar provides a very pleasing-to-the-eye listing of all the events posted to the website, and users can easily filter by group or event type using a Views exposed filter. The Date module supplies time/date functions for Event nodes and other features.
• Organic Groups: Each office and agency is set up as an organic group, with permissions for posting new news/blog posts, pages, forms (using Webform), and events. Additionally, each group gets its own menu, provided through the OG Menu module.
• ApacheSolr: After having many troubles with the large database (over 20,000 nodes, with about 800 words per node on average) with search indexing and cron runs, I decided to install ApacheSolr and the Lucene search server, then set up cron using the Elysia Cron module (to help ensure cron was running efficiently).
• Übercart: Online giving pages and the shopping cart system (with PayPal integration) are provided by Übercart, along with a healthy dose of hook_form_alter()s and Rules. (JohnAlbin setup most of our donation system, and joelstein helped with a lot of cleanup issues, including notification emails, some rules actions, etc.).

SVN Version Control

Working together with Palantir.net, I was finally forced to jump in headfirst into using a version control system. We decided to use SVN, and after I set it up on our Archdiocesan web server (running CentOS), we synchronized repositories with Palantir, then worked together (I did most of the theming, while Palantir did most of the back-end development and content migration), checking in and out quite frequently.

I tried to use Coda's built in SVN functionality, but ultimately had so many problems (it's in its early stages) that I decided to stick to using the Terminal to interact with the repository.

Theming

Since I am very familiar with the internals of Zen 2.x (which was in an alpha release at the time I started site theming), I decided to build a Zen subtheme for this site. The archstl theme has a total of over 15 .tpl.php templates (I tried doing as much preprocessing as I could, but there are some structural XHTML changes that needed to be made directly in the templates), as well as 12 CSS files and a handful of javascript files.

The theme has a few main features:

Mega Drop-Down Menu Navigation

A trend that has become relatively popular of late, mega drop-down menus provide the main navigation for the site. These drop downs are basically divs inside of a list of five main-level navigation links. The divs appear after hovering over a main link, and disappear a short bit after the mouse stops hovering. This functionality is provided via JavaScript.

Using mega menus has even allowed us to insert a parish search form directly into one of the menus. As this is one of the most frequently used features on the site, it should help save a little time for many users.

Due to restrictions in Drupal's menu system, I decided early on to simply create a custom php file with all the navigation markup, and then include that (using a php include) in the site's page.tpl.php templates. At some point, I might move this menu system into some sort of module, for easier management, but our main navigation doesn't change all that much, so it should be safe as-is for now.

CSS3 / Progressive Enhancement

Depending on what browser you use to view the new site, you'll either see rounded corners all over the place, of straight corners on edges of navigation links, sidebar blocks, and content items. Also, blocks should have beautiful box-shadows applied in any Webkit-enabled browser (newer versions of FireFox should also show the shadows).

The site was thoroughly tested in Internet Explorer 6, 7 and 8, as well as FireFox 3+, Safari 4+, Opera 10, and Chrome 4+. Almost all of the main template is coded to meet CSS2 validation standards, and a glance at the W3C Validator (for the XHTML markup) provides an almost error-free review (the main pages seem to work well, but some legacy content has a ton of invalid cruft).

Better Text Layout / Spacing

The old site didn't give much thought to line-height, heading formatting, and text styling. The new theme contains styles for everything from blockquotes to list styles and every level of heading. It is much more pleasant to read a long page or article on the upgrade site.

Check out the Typography Test Page (a great way to quickly make sure you've styled the main elements).

Other Features

Parish and School Search

The parish search pages (along with school search pages) are set up using Views and the excellent Mapstraction module (which allows us to use a view attachment to link a map to all the nodes listed in a view). (Read more about our custom views exposed filter handler).

We set up a custom view with some exposed filters to sort Press Releases and give an RSS feed for those who wish to follow the Archdiocesan news releases.

Prayer Requests

The Archdiocese of Saint Louis is privileged to have a wide variety of religious communities, and one of the beautiful things many of these communities have done is pray for thousands of online prayer requests since the beginning of the third millennium. Our online prayer request form has evolved from an email form, to Joomla's PrayerCenter, and finally to a fully-customized and highly-optimized feature on our new site. You can read more about how we basically rebuilt PrayerCenter, with tons of great improvements.

Calendar System

Using the power of CCK + Date + Calendar, you can make a calendar system that is infinitely extensible. Throw in Views and Organic Groups, and you have a magic combination.

On the old site, it was very hard to (a) manage calendar events (we used JCal Pro), and (b) integrate calendars into other content, and into each other. On the new site, since all events are simple event nodes with metadata attached, we can aggregate the nodes in so many different ways (besides the simple universal Calendar of Events) to build a ton of different listings of calendar events—lists by taxonomy terms, month, year and day views, simple lists, and sortable and searchable event lists.

Another nice feature of the Calendar module is the ease of creating iCal-compatible calendar feeds. You can simply click the icon, and subscribe to the Archdiocesan calendars.

Conclusion

After almost a year of development, it is a wonderful feeling having a project like this out the door. There remain a lot of small tweaks, especially to content manager interaction, but things are much easier now that everything is unified into one codebase and database.

Moving forward, there are a ton of useful new features under development, and many of the current features will be further streamlined based on user feedback. I'll be posting more as the time comes!

What do you think of the site? Follow the Archdiocese of Saint Louis on Twitter, or visit the Archdiocese of St. Louis Facebook Page to provide feedback!

Drupal version: Drupal 6.x