In November and December 2011, New Target, Inc. officially launched a suite of websites implemented in Drupal 7.9 for the Legal Services Corporation (LSC) – an independent government agency that is the single largest funder of civil legal aid for low-income Americans in the nation.

Why Drupal was chosen: 

Drupal was chosen because of it's multisite functionality.

Describe the project (goals, requirements and outcome): 

Introduction and Background

LSC envisioned their website to be the comprehensive resource for low-income individuals to find legal assistance – yet their one-stop website was actually a collection of 6 unique websites. The multi-site aspect served not only as a technological hurdle to overcome but also as a stakeholder consensus hurdle because website ownership was spread across multiple program offices. To achieve LSC’s vision, the websites needed to be simple to navigate, easy to update by LSC staff, and integrated closely in navigational flow as well as branding to provide a seamless user experience. Internally, the websites needed to encourage efficiency, communication and collaboration among Board Members and staff by providing a unified content repository from which to manage all websites.

To best understand the needs of each user (external and internal) and properly architect the websites, New Target undertook the facilitation of an in-depth requirements gathering and information architecture process with staff members, stakeholders, and site users, who gave diverse, yet valuable, insight on content priorities, design elements, work flows, user roles, and more.

Design and Functionality

The following sites were architected, designed, developed, tested, and deployed under one Drupal 7 installation, giving each LSC Web administrator the ability to manage the collection of websites from one CMS with one login:

Four external public sites


One password-protected intranet site

  • LSC eWeb (not publically available)

A working group model for select users operating as an internal, password-protected “wiki”

  • LSC Wiki (not publically available)

The sites leverage multi-language support and are compliant with Section 508 of the US Rehabilitation Act. Additionally, they are optimized for search engines.

External SQL Database Integration

New Target utilized the standard internal MySQL databases as well as integrated a Custom SQL Server database to render information dynamically. This legacy 3rd party SQL database maintained the statistics and other data relevant to their programs and is a critical part of providing a comprehensive experience to users seeking legal aid. New Target was tasked to implement a search-able widget that queries the SQL database and retrieves data. Both the ‘Find Legal Aid’ block on the Home page and Find Legal Aid page are integrated and populate from the SQL database ( Additionally, the Program Profiles page uses views to query SQL database and retrieve state specific data ( This SQL integration is yet another example of Drupal 7’s evolution as a platform for web development and the interoperability efforts well underway at Microsoft (


New Target organized the entire LSC Resource Information website using a controlled taxonomy module. LSC administrators of the site have the flexibility to add to the vocabulary list and tag content as needed. The menu structure is based on Taxonomy vocabularies and it is auto generated each time new vocabulary terms are added with projects. This module gave LSC a simple way to organize the content and allow for accurate searching by site users who need a comprehensive, intuitive legal resource.


The website is installed on a VMWare ESX 4.0 quest running Centos 5.6. LSC has allocated 2 CPU cores, 12 GB RAM, and 60 GB disk space. Originally, New Target provided LSC with a VMWare image, which they simply converted and loaded onto the LSC VMWare system allowing them to point the DNS to the new IP addresses. During the launch New Target assisted LSC in trouble shooting common issues in their network that were impeding site functionality.

Lessons Learned & Conclusion

Building this site required a significant level of effort on the technological and project management fronts. We learned new things and were reminded of timeless aspects of all web projects. Those we’ll keep in mind on future projects include:

  • We chose Drupal 7 to have the most recent, stable version of core Drupal features; however several of the modules functioned best on Drupal 6. This didn’t prevent us from using the modules; it simply added a layer of complication and additional time to configure the modules correctly. We watched Drupal 7 mature rapidly during the course of the project but were reminded that software matures as well.
  • The level of information architecture strategy needed for coordinating URL paths and breadcrumbs on deep level navigation can’t be underestimated. This small technological quirk of Drupal 7 and the infrastructure needs reminds us that hurdles always arise that no one could have anticipated and, after a check of all forums and groups, no one at the time had experienced either!
  • Migration, migration, migration or content, content, content. When evaluating a website the content that is present is not just an entry in a database. It may have been stylized and created just for the “wrapper” of the old web templates or the overall messaging strategy manifested in the Information Architecture. Trying to fit a square peg in a round hold never quite works and sometimes a client’s content needs to be rewritten and reformatted extensively.
  • No matter how far we think web technology has progressed there is always a creative friction present between form and function. A great deal of ink and pixels has been dedicated to this issue over the years in web industry magazines and we’re sure it will continue, but there will always be tough choices to be made in web projects that should always give the client the best possible solution for their needs.

The websites are a strong voice for equal justice in our country and play an integral part in supporting LSC’s mission “to promote equal access to justice in our Nation and provide high quality civil legal assistance to low-income persons.” New Target is proud to have been a part of this important government web project and looks forward to supporting many more government agencies with Drupal powered web properties for years to come.

Organizations involved: 
Why these modules/theme/distribution were chosen: 

Mobile Tools: Through the use of this module, New Target was able to feed select pages of the sites for customized display on iOS and Android mobile devices. This module allows the mobile version of the site to be manageable from the administrative panel of LSC’s Drupal 7 CMS. Additionally, given LSC’s and the federal government’s utilization of Blackberry mobile devices, New Target created custom style sheets for Blackberry devices.

Books: New Target faced a business requirement to create a collection of working groups, each of which allowed only a select set of individuals to access and contribute to the group’s content. Although originally conceived as a Wiki module implementation, once requirements gathering was complete and the business needs defined, the Wiki was deemed unsuitable to meet LSC’s unique needs in this area. New Target researched several solutions and chose the Books module as the best fit to accomplish the necessary functions for LSC. With the Books module, New Target was able to provide an outline-style content organization that satisfied LSC’s expectations. More importantly, New Target was able to seamlessly extend user access settings managed at the book level to its various content pages or “chapters”.

Project team: 

One Project Manager
One Technical Lead
One Usability Specialist
Two Designers, one of which was the Creative Lead and directed the strategy of all themes
Two Drupal Developers
One Quality Assurance Specialist
One Systems Engineer


Stomper’s picture

Did you guys use Drupal for the intranet as well? If so, could you enlighten me on any obstacles you encountered and how well Drupal met the intranet requirements. Did you have to integrate Drupal with any Microsoft products (like SharePoint, Office)?

Pedja Grujić’s picture

Drupal works for intranets.

We have since LSC Intranet built quite a few intranets with varying features and have not run into any obstacles yet or anything that could not be built with an already existing module or custom module.

LSC Intranet was simple and it did not require any integration with Microsoft products, their intranet is more of employee portal for news, events, weather, traffic and other company related items.

Some of the modules we could recommend are:

and there are tons more that you can utilize based on your needs.

Only additional thing is that we had to setup is to pull data from an old MS SQL database, we have outlined steps for that in our blog post here:

Drupal Geek at New Target Inc.

Stomper’s picture

Thanks for the response. I was wondering whether you have any experience with using Drupal in an intranet application, but dealing with document management, work flow, and multiple editors.

I ask because I'd appreciate any feedback regarding the best approach or modules to allow content editors to a) be able to check out content, b) view which content is currently checked out, c) supports 10+ simultaneous unique editors, and d) support versioning/roll-backs of changes etc.

Thanks again

Pedja Grujić’s picture

Have not done anything to that extent yet. However few things that do come to mind is using Workbench modules ( )with rules, and bundling it up with FileDepot ( ) and Content Locking ( )

My suggestion would be that you give those modules a try and they should get you close. Let me know how it goes seems like an interesting project.

Drupal Geek at New Target Inc.

Stomper’s picture

Thanks for the recommendations. I did not know about Workbench previously.

In the process of developing the information architecture, I've encountered an issue in how best to determine which content fields should be included in a given content type. Ideally I'd be able to get feedback from the end-user but am having trouble trying to figure out the best means to do so. I've considered using card sorting, but the card sorting software I have available does not allow the reuse of cards. Reusing cards would have allowed participants to put the same content field under different content types. My plan is to have the content fields on "cards" and the content types as "categories."

Did you have to do something similar when creating the create content forms for your clients? What was your approach and do you have any suggestions? A free approach would be ideal.