As one of the largest and longest running open source projects of all, Drupal has an incredible community.

To help new visitors, and returning visitors looking for a new challenge, we are making some changes to the /community section of Drupal.org. This will happen in a number of phases, the first of which is already at a “beta” stage.

Phase 1

We are rebuilding the Community home page to reflect the activities and groups that visitors might be looking to find out about. It’s not enough to say “Yeah, there’s a group of people out there and you might find them on Groups.drupal.org, Slack, IRC, Drupalchat.me, etc.” - we need instead to find out what somebody is trying to achieve and then direct them to the actual places on these systems, whilst also giving some context of the overall governance of the activities.

At DrupalEurope, the Splash Awards handed out a prize to a website project that caught my attention, boip.int. It provided a great model for directing visitors based on activity, as you can see:

screenshot of biop.int

So we are working, in conjunction with many in the community, to recreate this experience in Drupal.org. You can see that drupal.org/community/beta had the first iteration of this already and will very soon become the default /community homepage:

screenshot of beta homepage

You’ll also notice that each of the sections has a link to an issue in the community project, https://www.drupal.org/project/drupal_org_community - you are actively encouraged to help us improve the content, propose new sections, etc.

You’ll also notice one other thing I have been repeatedly asked about…

The slogan, “Come for the Software, Stay for the Community” is back! 🎉

Phase 2

One of the most significant challenges I and others creating the page above have noticed is finding the canonical locations to find all the various people involved in each activity. Some people hang out almost entirely in Slack and have their own external website, some have a presence on Groups.drupal.org and other groups have fixed locations, such as the Core Initiatives section.

I would very much like to see a place where groups, both chartered/official ones like the Community Working Group or the Promote Drupal Initiative, and less formal but long-term groups, like Core Mentoring, can have a canonical place to say who they are and provide updates of what they are up to.

So, under /community, we will also be offering groups the ability to create their own section, which they will maintain. That section will, at a minimum require:

  • An introduction to what the purpose of the group is
  • An explanation of how the group organises itself
  • An introduction to the people who organise the group
  • An explanation of how to get involved
  • A blog so that the group can update the community on their activities.

I am listening out for which groups would like such a place. Please create an issue in the project with the details. If you wish to discuss first, please contact me.

Comments

hestenet’s picture

We are still working on the accessibility of the new design, and will be making sure that's in place before the new /community page comes out of beta.

If you would like to provide specific comments about any element of the beta, please post in the Drupal.org /community section issue queue.

--
Tim L
Drupal Association - CTO

andrewmacpherson’s picture

I can't see anything about accessibility in that issue queue. Is it somewhere else?

rachel_norfolk’s picture

Hi! We spoke about accessibility of the accordion a couple of weeks ago and we do intend to run things by you, as I said at the time. The blog post was published before the work came up in the internal sprints, though. I believe they will want to talk through possible solutions. I expect an issue would be created in one of the infrastructure projects for that infrastructure item, rather than in this project, though.

drumm’s picture

#3010343: Add styles & JS for accordion display is the issue for my initial implementation, which should solve most or all of the accessibility problems with the draft page. https://www.drupal.org/community/beta has been updated to use the new markup. Any followups to this work can be comments on that issue, or separate issues in the bluecheese issue queue.

andrewmacpherson’s picture

Thanks @drumm for the latest update. The accessibility of these expandable groups is moving in a good direction; they're much improved already! I'll post more feedback on the Bluecheese issue you linked to, and file some follow-ip issues too.