You’ve read about my operational plan and theorems in Part I of this series. Here’s why I chose Drupal to carry out the Asian Pacific Americans for Progress website instead of Wordpress.
Drupal is very good at building complex websites that can vault a nonprofit past brochureware or a blog and into the position of being #1 on your subject matter. I’m sure Joomla can do the same but there are certain Drupal practices and modules that can fundamentally alter the balance of power between your nonprofit and the competition. If your nonprofit is interested in being the biggest and baddest Website on the block and in winning your vertical, I’m pretty convinced that Drupal is the technology that can take you there. Don’t get me wrong, I still love Wordpress for smaller nonprofits but once your nonprofit has started to do multi-user blogging or if your nonprofit is very aggressive in the online space, you can’t really take Wordpress in that direction. However, there are caveats. You WILL need dedicated staff or retain consultants to maintain the Drupal beast. It’s not cheap.
It’s important to note here that I support the use of Acquia Drupal instead of the regular Drupal distribution that you normally find. Acquia is the company that is dedicated full-time to Drupal development in much the same way Automattic supports Wordpress development. They have created a customized distribution of Drupal called Acquia Drupal that bolsters Drupal’s ability to become a community website.
Here is a quick comparison of the feature sets between Wordpress and Drupal that you should be aware of.
Feature Wordpress Drupal Upgrade without techie Yes Hell No Multi-user blog No Yes Automated image formatting No Yes Complex data manipulationOk, here’s some typical information architecture nomenclature that you’ll need to learn in order to discuss these strategies with a Web designer. Note: if your consultancy’s designer doesn’t know what you’re talking about, ask to see an information architect. If they don’t have one, they’re probably not right for your nonprofit redesign.
The river
The river is that stream of posts that you normally see in blogs. You can see this in effect on this blog with the blog entries listed by date from newest to oldest.
The (endless) queue
This is derived from a Drupal module called “nodequeue”. It basically allows you to order articles at will in whatever order your editors so desire. You won’t need a user to go in and manually hack out some HTML to make headlines for all the other blog entries on your site. In other words, it’s a human-powered headline builder for your website.
The teaser
This is the first few lines of the article used by Drupal and by Wordpress to entice users to click on a link to that article.
The teaser thumbnail
This is the picture that accompanies the teaser. I also use teaser thumbnail videos but that’s a much more advanced tactic that I’ll discuss in another article.
Your StrategiesNonprofit strategies mentioned in Part I that fall underneath the purview of a Drupal installation include (listed in the order that it would be encountered by the average reader):
Key modules we will be discussing will be blog, imagecache, nodequeue, Content Construction Kit (CCK) and Views. These modules constitute the core of any good Drupal community site as together they allow for a nearly infinite level of layout customization. CCK and Views are a profoundly powerful aspect of Drupal but they require a high level of technical knowledge to use properly. CCK allows you to create customized blog entries in which certain fields are used to specifically fill in portions of a magazine layout like the teaser thumbnail Views are a way in Drupal to customize the ordering and layout of specific pieces of content on your Web site. Those of you who have used report builders in Raiser’s Edge or Crystal Reports will be surprised that there is now the same capability in a CMS. Learn more about Views here. For those of you in Joomla world, CCK and Views don’t have any equivalents although there is something in beta that is rolling out.
Magazine-style layouts
Magazine-style layouts in Drupal are basically concerned with the layout of content comprised of a teaser, a teaser thumbnail, meta information like the name of the author and date, and the article itself. Let’s take a quick look at a typical “design pattern” for the headlines section of a web newsite.
Typical News Headline Design
It’s almost impossible to build this into a Wordpress design consistently because Wordpress has no built-in facility to automatically resize and crop images to fit into a specific size. Wordpress is wonderful at one-blog-entry-at-a-time posting. However, a magazine style layout will require the ability to reformat and resize content into an existing template. Wordpress doesn’t have that capability. By using CCK, Drupal allows developers to customize blog entries that a user fills out which can then be reformatted to fit an existing template. In essence, you can make a magazine lay-out composed of blog entries. In fact, the APAP web site is a perfect example of this, you’ll notice that an image is repurposed as a teaser thumbnail and as the lead image on many of the articles there. That’s only possible because of the imagecache module which allows for the dynamic resizing of your pictures depending on its position in a page. When you combine this all with Views, you have the groundwork for an automated news magazine website built entirely by your user community.
News aggregation
Your nonprofit will have to create personal blogging environments for its staff. This is where social media is remarkably useful and I wholly endorse THIS kind of use. Basically, you open up a Twitter account and start following other Twitterers who are in the same policy area as your nonprofit. You can also set up RSS feeds to do the same thing. Between Google Reader and Tweetdeck (I use Twhirl), you can have a fairly robust set of news items flowing into your desktop in real-time. Your editors can then pluck the necessary items from their feeds and write about it on the site. APAP has gotten a lot of hits using this process and has eventually gotten good search engine results page (SERP) rankings over time. This is crucial to building up your PageRank. When I started working with APAP, it was at three and now it’s at five. It’s moving up in the world. Also, it’s old Website Grader score was in the low 30s. It’s now at 95.5 indicating that we’re pushing up at the top of what’s available in terms of SEO but I still have a few tricks left up my sleeve to push that up higher.
Editorial filtering function
This strategy requires nonprofits to get their head wrapped around using their expert domain knowledge to filter out news items for their users. Once nonprofit management understands this, you need to implement this in Drupal. Here is the design pattern you should follow for this strategy.
Aggregate Your Headlines With a Nodequeue
What you are doing with an editorial filtering function is two things: your nonprofit is telling your users what it thinks is incredibly important to read with one big headline and your nonprofit is shaping content based on site traffic using your queue. Basically, your editors can see what is getting read by users in real-time and then adjust the queue accordingly. This is how the “Top Five” section gets reordered every day by editors on the Asian Pacific Americans for Progress site. If a post is in the river and starts getting traffic, we push it up to the Top Five to accelerate that process. The three modules you need for this is nodequeue, Views and imagecache. The nodequeue module should be installed so that your editors can reorder the queue to suit their taste but the Views module is how you present the queue to your users. Imagecache is useful to dynamically resize your pics to fit the different layout options you can give yourself.
Can you do this in Wordpress? Oddly, before I even heard about what nodequeue and Views could do, I actually had a crude node queue running at asianamericansforobama.com. With the help of another techie volunteer, we wrote a nodequeue-like piece of code that reordered the Wordpress loop so that it would highlight the ten headlines with different colors and points sizes. This is why you see the large Huffington Post-style headlines over at that site. It wasn’t an easy kludge either and was prone to a problem wherein users would add too many posts to the queue. I very much prefer nodequeue over our Wordpress hack.
Blogging community
Multi-user blogging capabilites are available out of the box with Acquia Drupal and it’s fairly easy to simply turn on the blog module. This blog module is so attuned to a multi-user blog format that it has to be differently configured for single-user blogging. There’s even room to support distinct RSS feeds for every blog generated by every user. While Drupal can be extremely maddening at times, this is one of the things it gets incredibly and totally right.
In the end, your blogging workflow should look something like this:
Information Workflow
Basically, information from the outside world gets sliced and diced by your staff, which in turn, gets turned into user-generated content by your community.
Your Mission Should You Choose to Accept ItI don’t think you should go out and set up a Drupal site tomorrow. In fact, if you already have a Joomla site, there’s a good chance you can do this as well. What I do think is that nonprofit managers and techies should work together to iron out these sorts of information architecture issues. Simply by improving the ability of the user to focus on important headlines, APAP generated a 10.73% increase in time on site while simultaneously seeing a 19.62% increase in absolute unique visitors during the month immediately after these changes were rolled out. To grow in site traffic yet improving the length of each reader’s engagement with a web site is pretty hard to do. Generally speaking, any growth in site traffic tends to mean a decrease in average time on site. However, we were able to forestall that from occurring with the new information architecture redesign.
Effect of Blog Entries on Site Traffic
An alert reader has asked me for a chart on the effect of blog entries on site traffic. I took the time to create a little data table from the Google Analytics reports for APA for Progress. Please be aware that the Jun-09 figures were run on 6/22 so the figures are incomplete for June.
As you can see in the chart above, there’s a high correlation (.945) between the number of blog entries and the level of site traffic. There’s also a high correlation (.820) between the number of blog entries made per month and the number of Google searches that drove users to the site.
Why is there such a strong correlation with blog entries and site traffic? Remember, this data set is selective in that there were very few external news events during this time period driving traffic to the site. If there had been external news events driving users to the site, this correlation would have been a lot lower. The lack of external events makes this data set almost the perfect illustration of a pure SEO play. Properly tagged blog entries with good metainfo will basically cause Google to better index your site. In turn, it will drive more traffic to your site, thus generating more loyal readers. It makes sense that there’s a higher correlation between visits and the number of blog entries than between Google searches and blog entries. This is because visitors do stay after hitting the site through a Google keyword search. They tend to accumulate on the site and get used to visiting it every so often. Think of Google as a way to give your website a shot at presenting itself to new users. In effect, each new blog entry complete with tagged keywords, is a way to hook more visitors into your site. The more attempts you make, the more likely you’ll be able to snag users into your traffic stream. And the more likely you can add these users to your blogging community. This should result in a workflow that looks like this:
Suggested Blog Workflow For Nonprofits
So here’s my thinking: I don’t think it really matters whether a nonprofit blogs to update a site. As long your posts conform somehow to already mentioned guidelines for building out your site, I’m pretty sure that if your nonprofit has the resources to post 2 or 3 times a day with its own people that it could eventually manage a similar growth pattern.
Here’s the kicker: most nonprofits don’t have the resources to post two or three times a day to their website. However, their volunteer base does. And this is why I believe blogs are essential to cash-strapped nonprofits. It allows you to get a chance to do multiple posts to your website with minimal cost. I don’t see how APA for Progress would ever have been able to sustain this torrid pace over six months without a blogging community. They’re set this month to break their monthly records and probably end up with around FOUR posts a day due to the addition of new bloggers in recent months.
Of course, the harried nonprofit manager will probably say that you’ll end up with new headaches as your try to fit your new bloggers into your existing communications strategy. Agreed, but first things first. Which problem would you rather have? The problem of managing of thriving a blogger community for your nonprofit or the silence that accompanies your nonprofit’s web initiatives? I opt for the noise.
I’ve been doing some research lately on building websites for a political advocacy group, Asian Pacific Americans for Progress (APAP). I haven’t been posting lately because I went down a VERY, VERY deep Drupal, information architecture and SEO rabbit hole for the last few months. I would have written this post sooner but I really wanted to confirm a lot of my thoughts first with site traffic measurements. Basically, this is a story of how a very small political advocacy group went from zero to hero in roughly six months. This is going to be a long post so let’s get started.
Chart of APA for Progress site traffic
What we have above is a chart detailing the last six months of traffic for APA for Progress. In return for my volunteer work with them, I asked that I be able to blog freely about the site’s growth and how I did it on basically a very, very tiny budget.
Be aware that the time period in the chart above begins the day before Obama’s inauguration so there is no bump from the political campaigning of last year. Also, the group had a very low number of new blog entries on it and was unable to get a bump from the campaign. Site traffic has grown from 91 visits a week to an all-time high of 2,356 about two weeks ago. The site is probably going to undergo a summer slump as many students will be on vacation but I expect the traffic to grow again during the fall. At the time I found them, APAP had suffered the loss of a previous Drupal site and was temporarily on a Wordpress site as a stopgap measure. In other words, they were simply like many other tiny nonprofits in terms of the transitory nature of their IT assets.
First, let’s list APA for Progress’s online and offline assets:
With little money and no traffic, APAP had to figure out how to maximize their current assets. I ran into them as a way to work off my Obama addiction. I decided that they would make a great lab for many ideas swirling around in my head as to how nonprofits should carry out their advocacy campaigns on the Web.
Over time, I’ve had to seriously rethink the role that nonprofits can play on the Web. Most of the time, nonprofits like to use Web sites to promote their mission and monetize their traffic. It’s basically a 20th century industrial model akin to radio and TV. The nonprofit broadcasts and the donor listens. The problem with this model is that it’s a guaranteed way of falling straight into the black hole of mediocre web design and low site traffic. There’s been a lot of discussion in the last few years given to email marketing and social media but primarily email and social media end up being used in the same way: to broadcast a nonprofit’s news and events. Just because your site has some moderate interactivity given you by an email vendor or your CRM, it’s not going to fundamentally change the nature of your site.
And unfortunately, much is made of social media’s ability to break up this model to the detriment of what I believe should be the cornerstone of a nonprofit’s online strategy: the Web site. Social media (in this case, Facebook and Twitter) simply cannot carry the burden of the work. It cannot generate traffic on a consistent basis and relies all too often on the most mercurial of personal relationships. If your nonprofit has little penetration with the right digital media rockstars, it’s difficult to get your message out there. This is not to say that your nonprofit should NOT have a social media inititative. If your constitutencies include young people, you should definitely have a Facebook fan page or Facebook group for your organization. You CAN use Facebook to drive traffic to your site but mostly for increasing traffic to your already popular blog entries.
What APAP needed was a surefire way of generating site traffic without hoping on hitting a social media jackpot and absent a compelling event that would organically drive interest in a nonprofit like APAP that dealt primarily with Asian American politics. It’s difficult to raise interest in politics regardless of your ethnicity if you’re not in an election cycle.
Because of this, I had to think about the assets that tiny nonprofits have. All small nonprofits are mostly made up of a collection of people interested in working on a particular issue. Their main assets are their fundraising and community relationships. This means that you have to grow and nurture those relationships into an online design. I’ve got a couple of “theorems” about nonprofits as a result:
These two observations have a strong impact on the way I believe nonprofits should create their sites in the future. It suggests that nonprofits can use their staff to create a strong editorial “filter” on news items happening in their geographic catchbasin. It also suggests that they should use their existing community of volunteers to build out content that more closely matches their advocacy positions.
These observations simply hung in the air until I started thinking further about taking these observations and turning them into an operational plan that could be implemented into APAP’s website. After working on this blog for two years, I had learned a lot about SEO and was intrigued by the success of sites like the Huffington Post and Daily Kos. I thought to myself: what can be gleaned from those sites and be applied to nonprofits? Here are my simple recommendations that I think nonprofit websites should adopt from news sites.
So ultimately, my earlier two theorems and these ten tips combined together into the current site design for APA for Progress. I understand that these strategies would create a fairly radical shift in the way nonprofits organize and distribute their communications. It’s a user-centered model built on serving users with content that doesn’t necessarily originate from the nonprofit. Indeed, most of the people creating the content are not staff.
This has tremendous ramifications for the way a nonprofit will organize itself on the web. With the informal and highly opinionated nature of most user-generated content, it’s probably a good idea to include a disclaimer saying that your organization doesn’t necessarily share the opinions of its bloggers. It also means the traditional role of a communications director moves less from creating press releases to more of a “business development” role asking other blogs and nonprofits in the same policy space to syndicate content from the site by either linking to it or republishing. It also means using your contacts to generate good “gets” — getting good guest bloggers or having important individuals participate in conference calls to your membership or in live video conferences. There are many different ways to use traditional PR means to get more traffic for your site.
Don’t get me wrong, this is a remarkably labor-intensive endeavor. Writing content and/or getting people to write for your site is time consuming. However, it IS free. And when you’ve got more time than money, this is a fairly clear way of getting your nonprofit out there. Oh, and how much did this project cost? Less than $600 for the Drupal redesign.
Check out Animoto for a Cause! I’ve been a long time user of Animoto and I’m actually a paid subscriber to Animoto. I’ve had a lot of fun working with their software to make vacation videos out of pictures I’ve taken. The way Animoto works is that you upload a bunch of pictures to their site and perhaps an MP3 for a soundtrack and their software creates a video out of your media. For nonprofits, this is a godsend especially since most nonprofits don’t have dedicated staff for making sophisticated multimedia. The time it takes to upload pics and video is nothing like the time necessary to create and edit a video. I highly recommend this software for nonprofits that hold frequent special events and want to promote them on their site. You can upload the video to YouTube and then embed it on your Web site for an instant promotional video of your work.
Here’s the PR blurb from Animoto itself:
Video creation platform Animoto® (http://animoto.com) today released Animoto for a Cause (http://animoto.com/cause), giving non-profit organizations and community activists free and unlimited access to the full range of Animoto’s services, both standard and premium. Animoto is the web application that lets anyone quickly and easily create dynamic, professional-quality videos from their own photos and music. Now organizations can use the service to promote their cause online in a multitude of ways, from posting and sharing videos on websites, YouTube and social networks, to downloading them to DVD for distribution at events. Animoto for a Cause launches with more than 20 participating charities, ranging from national to regional, and applications are now being accepted from qualified organizations, groups, individuals, non-profits, and activists.