Case Studies
The case studies on Drupal.org highlight impressive websites and applications built using Drupal. Case studies should be stories that highlight the value of Drupal to a company, organization, industry, a group of people, or the public-at-large. The target audience for this content is is non-technical evaluators who want to see what's possible using Drupal.
Case studies should do at least one of the following:
- Mention the benefits that Drupal brings and how it helps the organization overcome previous challenges
- Highlight features of Drupal
- Highlights how the project is innovative
- Illustrates the impact of the project to the wider world and/or improves people’s lives
- How Drupal empowers content editors or site owners
- Illustrates the value of open web and community
Site visitors are able to filter case studies by Drupal version, industry or feature. Sponsored and outstanding case studies rotate through the homepage carousel. To have a case study featured prominently in the case study overview, see promotional information at the bottom of this post regarding Supporting Partners.
Style guide for case studies
In addition to following the Drupal.org content style guide, all case study content submitted should:
- Highlight the value Drupal brings as opposed to just the agency that worked on the project
- Speak to the benefits in specific terms (not just “improve the design or UX” but what experience it makes better)
- Include a point-form list of benefits or features instead of long paragraphs of text
- Avoid emphasizing version numbers so that case studies stay fresh longer (e.g. use “latest version of Drupal” instead of “Drupal 10”)
- Avoid jargon, Drupalisms, and module names
- Spell out abbreviations and acronyms
- Use gender-neutral pronouns
- Adhere to the Drupal Code of Conduct
Accompanying images:
- Must be high-resolution and accessible
- Should show pages, features, and workflows
- Need alt text and titles
- Are optimized for web use (remove unnecessary image metadata and upload pre-scaled images)
Guidelines for format
- Summarize the business value that Drupal brought in the opening sentences
- Add a Results or Outcome section of the project at the beginning of the case study
- Follow a general goal/challenge/solution structure
- Include information about why Drupal was chosen if it’s positive, compelling, and relevant
- Maximum 750 words
Rules for promotional material
Per our advertising guidelines, we ask that you do not include promotional material, calls-to-action, or lead capture forms in your submitted case studies. Such materials are reserved for organizations who participate in the Drupal Association Supporting Partner Program, at the Premium level and above. Implementation of any lead capture CTA will be done by Drupal Association staff, as will premium placement on the Case Study page. If you are a Premium Supporter and above and are interested in learning more, please contact your account manager.
Get inspired by other case studies
By Industry |
By Feature |
Case Study Template Features
The Drupal.org case study template has a number of features you can use to make your case study stand out from the rest.
Cover photo
The cover photo field defines the main hero image that appears behind the title of your case study. This image should be high resolution and low contrast so that the text of the case study title stands out against it. If no cover photo is specified, it will simply be omitted.
Big Quote
The 'Big Quote' feature is found in the 'Template' section of the WYSIWYG editor. This will automatically insert a prominent, full-width block quote where you can call out important information to your reader.
Big Statistics
The 'Big Statistics' feature, also found in the 'Template' section of the WYSIWYG, let's you highlight they key facts and figures that tell the full story of the impact your project made.
Call-outs
The template section of the WYSIWYG editor also offers a number of other 'call-out' templates for adding notes or highlighting important information in your case study. Give them a try!
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion