Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Overview
‘Why Drupal’ is a top level Section of Drupal.org, a source of general information about Drupal and marketing materials. It contains unique content that answers the question, “Why should I choose Drupal?”. It also makes learning Drupal a cohesive user journey by also providing clear paths to content in other Sections in useful context.
Personas
Personas: Newcomer, Learner
The Section is primarily focused on Newcomers and Learners, specifically on Technical Evaluators and decision makers that can chose to use Drupal in their organization.
Scenarios
A Newcomer or Learner, who wants to know what Drupal is, will get an overview of Drupal project, its history, mission & principles.
A Newcomer or Learner, who wants to know what Drupal is capable of and decide if it is a right tool for them, will discover main Drupal features and some guidance re: choosing which version is right for them. They will also see industry use cases, technical marketing materials, and high profile case studies, and get a sense of how active the community/project is.
Metrics of success
| Indicator | Target | Time Period |
| Traffic to Why Drupal Section and individual pages | +20% | 8wks post Why Drupal? launch |
| Drupal Downloads | +10% | 8wks post Why Drupal? launch |
| Traffic from the Section to events.drupal.org | +10% | 8wks post Why Drupal? launch |
| Traffic from the Section to Marketplace | +10% | 8wks post Why Drupal? launch |
| Traffic from the Section to Try Drupal | +15% | 8wks post Why Drupal? launch |
| Traffic to Drupal Newsletter signup | +5% | 8wks post Why Drupal? launch |
Governance
Because of the role 'Why Drupal' content will fill, its importance and quality requirements, this section will be managed by the Drupal Association staff and a limited sub-set of community members.
Editorial Calendar for 'Why Drupal' will be managed by the Drupal Association staff. Community input on content in Why Drupal Section is welcome. Community members can use Drupal.org Content issue queue, ‘Why Drupal’ component to report problems or suggest improvements.
Implementation details
Section map:
- ‘Why Drupal’ is a top level Section of the site.
- Present in top navigation.
- It is an organic group.
- Includes a few sub-groups (features per Drupal version)
- Contains ‘official’ Drupal blog.
- Types of content created in this Section: page, post, video.
- Types of content displayed in this Section from elsewhere: case study (featured only).
- URL: drupal.org/why-drupal
- Most pages are static pages, with 2 views: for blog posts and featured case studies.
- This Section will effectively replace current 'About' book, with most of content migrated from there
Todos:
#2666250: Merge D7 landing page into About section
#2666254: Display featured case studies in About section
#2666256: Create Drupal blog in About section
| Comment | File | Size | Author |
|---|
Comments
Comment #1
tvn CreditAttribution: tvn at Drupal Association commentedComment #2
tvn CreditAttribution: tvn at Drupal Association commentedComment #3
tvn CreditAttribution: tvn at Drupal Association commentedComment #4
Bojhan CreditAttribution: Bojhan as a volunteer commentedI am wondering what is our content strategy to convince the different audiences. What are they key messages we assume will drive this traffic, the existence of pages is the step in between.
Comment #5
bradleyfields CreditAttribution: bradleyfields at Drupal Association commented@Bojhan
There is a lot of context this step assumes, yes. Much of that has been articulated elsewhere, like this February update about the strategy’s messages and objectives, and this research-driven description of the personas and what we want them to achieve, for example. We then started on an adoption cycle narrative (honestly, not terribly unlike a guided Choose Your Own Adventure story line), inventoried existing content, and then audited that content to see how well, if at all, it supports and/or serves that narrative (and if not, what we need to change).
The paths we’re working on, as the site map suggests, include answering questions like, “What is Drupal?” and “What are other people like me doing with Drupal?”, as well as giving a foundation to people who want to get started right away or need help to do so. This is all because research revealed that people who are new to Drupal have a difficult time getting familiar with who and what we are before they're asked to download and install.
Messaging will be aligned with where content falls in the story line. So, for example, “What is Drupal?” will grow to feature stats on its use (e.g., X translations, Y camp attendees) as well as an explanation of what "open source" even means. "Features" will grow to offer help deciding which version someone should choose. And “Who uses Drupal?” will grow to feature scenarios from different personas’ perspectives. One of the key messages is inclusion, and to demonstrate that, we're highlighting how others have found a home in the community and illustrating how newcomers can follow similar paths.
Comment #6
tvn CreditAttribution: tvn at Drupal Association commentedAs an 'MVP' for Drupal 8 release, we scaled this down to 'About' section, less marketing/promotion, mostly information about Drupal.
'About' book has been audited and content migrated into the new section and page content type: http://drupal.org/about. Still work in progress, especially copy will be updated on a lot of the pages to be up-to-date and relevant. bradleyfields is working on updating the copy in the coming days.
Comment #7
tvn CreditAttribution: tvn at Drupal Association commentedUpdate: this is mostly done. The new Section got launched at the time of Drupal 8 release. This is now an area with curated editorial content about Drupal, aimed primarily at Newcomers and Learners, with the goal to promote Drupal.
Since 'About' Section is a curated area, any content inside of it can be created, edited or deleted only by Section Maintainers. At the moment they are: bradleyfields and tvn. Users with advanced roles, who have 'bypass access control' permission, will have access to create or edit content as well, but they are expected not to do it without consulting with Section Maintainers first.
At the moment 'About' Section only includes static content. We'll be introducing dynamic content for this Section using 'post' content type in a form of 'official' Drupal blog.
Comment #8
tvn CreditAttribution: tvn at Drupal Association commentedAdded 3 issues which are last steps we need to do to finish this Section.
Comment #9
tvn CreditAttribution: tvn at Drupal Association commentedAm going to close this as fixed. The two child issues are still valid follow up tasks, but the section already exists and is used.