Last year Drupal Association staff—in collaboration with Forum One—analyzed the state of content on Drupal.org. We developed a content strategy aimed at improving its quality and findability. Various recommendations were made for content structure, organization, and governance.

One of the main recommendations was to restructure content around areas of user activity instead of the content type used to create the content. On Drupal.org, content about a topic is often scattered, because some content types are only available in certain areas. But we’d rather have a single place for content on a particular topic, no matter which content types are used to create that content.

User research gave us a number of general areas of user activity or tasks, which we used as a base for top level content grouping. We’ve called those groupings “sections.” Each section is based around a particular set of common user tasks and has a clear purpose and audience. We started implementing these sections a few weeks ago.

Each of them will also have a slightly different governance structure. Some of the sections will have more editorial/curated content, while others will be open to edits by everyone. We wanted the flexibility of having different user roles with different permissions in different sections. We also wanted the flexibility of being able to display a single piece of content in multiple sections if needed, and perhaps even use a different theme per section.

To meet those requirements we decided to use Organic Groups. The work on getting all the modules ready on Drupal.org began in August last year. After a few rounds of performance testing and configuration review, Organic Groups and a few accompanying modules were in place to enable us to work on sections. The first couple of them were launched simultaneously with the Drupal 8 release.

Drupal.org section

At first, we wanted to test out our ideas and assumptions on a less visible area of the site with lower traffic. So, the first section we created was about Drupal.org itself. It consists of various information about the website, aimed at those who follow or take part in Drupal.org development. Its content is mostly produced by our internal team.

About section

The first highly visible section we tackled was About. It is a source of general information about Drupal and promotional materials. The content is curated and aimed primarily at evaluators, and the Newcomer and Learner personas.

To create the section, we audited all the content in the old “About Drupal” area (which was using the old book page content type), rewrote most of it, and re-created it using the new content types. While the initial round of work on the section is complete, there are a few more things we want to do, so expect additions to the section throughout the year.

Because of the curated nature of the content, this section has tight edit permissions, and is managed by the Drupal Association staff. Feedback is always welcome, however, so if you do notice a problem please use the Content issue queue to report it.

A big part of the About section is talking about the features of the Drupal software. And specifically with the Drupal 8 launch, we wanted to do it well, which brings us to...

Drupal 8 section

It is the landing page for Drupal 8 release, and the main source of high level information about Drupal 8 and its features. And it is a section too, created using Organic Groups and located inside of the About section.

This one was created from scratch. All the content was written specifically for it, by the Drupal Association's communications team with a lot of help, review, and feedback from Core committers team.

For this section, we went one step further. Not only does it have unique content, it was also designed to look completely different from the rest of Drupal.org. To make it happen, we created a separate theme, based on Omega, and used og_theme module to make it possible to use the theme on only one particular section of the site. This worked really well.

Again, this section has curated content and edit permissions are locked down. If you do find a problem, please report via the Content issue queue.

What's next?

These new sections don’t only introduce a new governance model and navigation patterns. They also introduce a new way we create dynamic content. I will talk more about this, as well as the sections we are working on right now, in following posts.

Comments

yoroy’s picture

Happy to see this strategy come to life!

Was going to ask where the governance bit is documented but found the issue: https://www.drupal.org/node/2338301. Would be good to document who's in charge of maintaining current sections, maybe even on the Section page itself?

Also curious to learn how new sections can be proposed, what criteria they need to meet. And: how this Section concept could be applied to the long wanted idea to have "Topic" pages.

tvn’s picture

Thanks Roy.

Since governance is slightly different per-section, it is documented per-section. So each 'Plan' issue for specific section implementation has 'Governance' bit in it. E.g. https://www.drupal.org/node/2533684, https://www.drupal.org/node/2516956.

Re: documenting who is in charge. I am curious how relevant that info is to the readers (especially if they are Newcomers/Learners as it is for some sections such as About). I feels like this sort of info is more relevant to a small sub-set of visitors - Experts and Masters who are heavily involved in the community and might even have advanced role on Drupal.org. And so, we don't necessarily want to have that info prominently right on the page.

What could be more useful perhaps is a way to 'report a problem' with a page? E.g. a link to open an issue or w/e.

>> Also curious to learn how new sections can be proposed, what criteria they need to meet.

We still have a long list of sections to implement from our initial plan. So I think this is a good discussion to have, but perhaps a little bit later. Overall I imagine, if we are talking about adding top level sections, there should be a use case different enough from any existing top level section, and enough content / potential users to justify it being separate.

>> how this Section concept could be applied to the long wanted idea to have "Topic" pages.

So Topic pages are different from Sections, but as we work on the latter and as we introduce new content types, we'll be introducing the new 'Topics' taxonomy as well. So at least we could start categorizing the content, even if the actual proper display for Topic pages will come later.

yoroy’s picture

I agree that the information about team members governing a particular section doesn't have to be prominently displayed. Maybe only logged in users can see it. Being able to report a problem could be a good first step. I ask because this indeed introduces a new governance model and I think it would be good to be open about what that model is or what the initial assumptions and starting points are anyways. Organics groups speaks to the technical part, the people side of this is unclear for now.

Re: topics: I know I'm getting ahead of things there :) It's just that we keep running into the problem of not having a good starting place to point to for people interesting in "X". Good to hear at least "Topics" are getting their taxonomy!

jamesoakley’s picture

The menu block in the RH sidebar of the About section remains there for most of the links you click within it. For those which generate a sub-section, it is replaced by the child pages. (For example media kit). But for the Drupal 7 and Drupal 8 pages, the block vanishes altogether.

I then eventually noticed that, for media kit, D7 and D8 I could use the breadcrumb to get back to the "About" top-level page.

Maybe I'm too much of a book-module, Garland-theme, traditional Drupalist, and instinctively look for an expanding menu block that shows the hierarchy of where I am. Maybe a newcomer wouldn't get confused as I did. But it seems to me that the About section needs more consistent navigation indicators, to help people see where they are in the Section, and how to other parts of the Section including where they came from.

All subjective. Only my 2p / 2c. But I leave these thoughts for what they're worth.


This signature is currently blank
tvn’s picture

Thanks for your feedback James. Drupal 7 page will get navigation block as soon as we add more contents to it. See https://www.drupal.org/node/2666250.
Drupal 8 area has a completely different theme, so won't have the same nav block. We can however mark 'About' menu item as active, to make it a little easier to get back.

tvn’s picture

Quick update, the 'About' menu item is now highlighted as active on Drupal 8 pages.

jhodgdon’s picture

At least on the current site, we have information in a sidebar of all the Documentation pages about the copyright/license for the content (it's CC BY-SA 2.0 licensed). The sidebar links to this page:
https://www.drupal.org/node/14307
which explains the copyright. So, that is good.

But this type of copyright information is currently missing from the About pages, such as:
- https://www.drupal.org/about/faq
- https://www.drupal.org/about
Also it's missing from blog pages. This is an oversight -- every page on the web in general, and in Drupal.org in particular, with content that someone might conceivably want to copy or reuse should have a copyright statement somewhere. In my opinion, since Drupal.org is an open-source project, the About and Blog pages should probably be CC BY-SA 2.0 licensed, same as Documentation pages always have been.

Also, you need to be careful about where the content is coming from. It is hard to tell with the About and FAQ pages, but if any of the original content of those pages was copied from previous drupal.org book pages, that content is most likely licensed CC BY-SA, and it is a violation of that license to (a) lose the attributions information that was on the original pages (in the revision history) and (b) not have a statement on the page that the content is CC BY-SA licensed.

So... this needs to be addressed ASAP. Thanks!

tvn’s picture

Thanks for pointing this out Jennifer. All content on D.o is indeed CC BY-SA 2.0 licensed per our ToS. We should display this better on the pages indeed, let's figure out how to do it in https://www.drupal.org/node/2705533.

For the About and FAQ pages specifically, the content was based on the previous book pages, but was rewritten by our content strategist in the process of migration. We'll fix (b) by displaying that better for all pages. We'll be more careful with this going forward.