A place to discuss and collaborate on improvements to Drupal.org. Here you can find and share ideas for improvements, organize and announce IRC sprint or other Drupal.org related event, get regular updates from development team.
This group is for active users of the site, content moderators, site moderators, and anyone contributing to Drupal.org in any way.
IRC channel
#drupalorg on Freenode
Recent
beta.drupal.org is ready to QA!
The redesign of the drupal.org site is nearing completion, and we’re looking for people to help us Quality Assurance (QA) test beta.drupal.org to identify problems with functionality and visual implementation before launch. There should be opportunities for people of all skills to help us identify or fix problems.
Bill O'Connor (csevb10) is leading the QA effort and can be reached on #drupal-redesign on IRC or in the issue queues.
Read moreDashboard general plan
Make a simple, solid default dashboard, with flexible underlying work. See what people use and ask for, use to improve content. Add features after launch.
Issues are tagged drupal.org redesign dashboard
What is on the dashboard?
Pages to round up existing user-specific listing pages:
<
ul>
Project metrics for drupal.org redesign
One of the big goals of the drupal.org redesign is to make it easier for end users to find the right modules for the site they're trying to build. With over 5,000 contributed modules, many of them providing similar functionality, it can be extremely difficult to choose. One method is to try to assess the "health" of the module, by how actively it's maintained, used, supported, etc.
One approach to gauging health is posted at Project ratings and reviews for drupal.org redesign. While that proposal deals with subjective factors, this post addresses objective facts about a module that can be computed and displayed for all projects hosted on drupal.org. While no single metric can tell you what module to use, and some knowledge will be required to make the best use of this data, it's important to make these statistics more readily available on drupal.org to empower users to make better decisions.
The redesign prototype for project pages includes the introduction of a sparkline showing the "Activity" for each project. The details of this activity chart weren't specified at a technical level during the design phase, but the spirit of the design is that they wanted more ways to visualize the health of a project. As we're implementing the redesign, we've been empowered to provide as many charts containing specific data we think will best help end users make sense of what's going on with a project. Read on for our specific proposal, including what metrics to compute, and some ideas on how those are going to be visualized on the new drupal.org
Read moreNeed volunteer for brochure update, and another for some writing/IA for the Drupal.org redesign
Hi,
I have a couple content-related d.o. redesign tasks:
Brochure
We need a one-page brochure that explains the benefits of Drupal. It will be linked from the new About page with the text "Short on time? Decision-maker too busy to look at this site? Download our one-page brochure for a summary of why you should choose Drupal, and information on its features and benefits."
You can see a prototype of his about page here: https://infrastructure.drupal.org/drupal.org-style-guide/prototype/about...
Read moreAbout redesign.drupal.org
redesign.drupal.org is what we will be launching when ready. User/pass: drupal/drupal.
Theme changes are deployed within 2 minutes. Module changes are pulled from CVS by BZR admins. The database is rebuilt from a fresh copy of Drupal.org every day. This is meant to emphasize that changes to code should be committed to CVS modules and the main copy of the theme. And database changes need to be done on Drupal.org, or automated in drupalorg_update_65xx().
Project ratings and reviews for drupal.org redesign
One of the major new features proposed in the redesign site prototype for making it easier to find the right modules for end users is the introduction of Project ratings and reviews. This post is a proposal for how we're planning to implement these features as part of the redesign. If there's sufficient traction for this proposal, we could actually roll this out independently of the redesign theme launch itself.
Read moreEditorial & Webmaster changes
Long-term changes or additions for editorial and webmaster tasks http://drupal.org/node/21923
1. Community spotlight on Get involved
https://infrastructure.drupal.org/drupal.org-style-guide/prototype/getin...
Interviews with community members. Will be a regular node, so no technical restriction on questions.
Related Issue: http://drupal.org/node/873194
2. Community Spotlight for Themes / Projects
Highlighted modules and themes
http://infrastructure.drupal.org/drupal.org-style-guide/prototype/themes...
Read moreHow to build Drupalists
Throughout the site there will be Drupalists
http://infrastructure.drupal.org/drupal.org-style-guide/prototype/docume...
http://infrastructure.drupal.org/drupal.org-style-guide/prototype/dashbo...
http://infrastructure.drupal.org/drupal.org-style-guide/prototype/downlo...
These are user-created lists of pages throughout the site that can be shared with others. At the most basic, a title and list of paths. This will take over the Contributor and Doc team links blocks.
What are good modules to build this?
Read moreBOF and sprint this Wednesday at noon (at Drupalcon)
Hi all.
It's a little last minute but we're going to be having a little Drupal.org Redesign BOF Wednesday. Bring your lunch to room 200.
After that, if folks want to sprint on the redesign we can move to the coders lounge or whatever. We can also sprint on Thursday if people are interested.
It will be great for those of us who are here to meet each other and I'm hoping for a group photo!
Thanks
Lisa
Header Tags
This post will discuss how to write a good header tag. As a general rule, you should have one <"h1"> tag, no more then a couple <"h2"> tags, and a spattering of <"h3"> tags
<
ol>
- Review the <"h1"> tags and determine which can be eliminated
- If you cannot eliminate enough <"h1"> tags, then rewrite them as an <"h2"> tag.
Drupal.org redesign sprint
Hello, we will be having the next Drupal.org redesign on April 9th, 2010 from 8am PST/4pm GMT to 12pm PST, 8PM GMT.
We will be focusing on the helping people their their themes implemented as well as the Solr implementation in first phase of the redesign. If you want to help please contact us about helping with the redesign.
Read moreStaging VM Maintenance Wednesday, March 31
StagingVM will be down for maintenance for approximately 3-4 hours on Wednesday, March 31 while it is migrated to a new and faster cluster.
Read moreWriting a Meta-Description
This post will discuss how to write a good title tag
<
ol>
Writing a Title Tag
This post will discuss how to write a good title tag
- By now you should have the Keyword, Title, and Description spreadsheet. If you don't go here and work on this process first: Keyword Research
- Open the spreadsheet that you have the URL of the page you are working on optimizing and the meta-keywords that you decided upon using the Keyword research process
Keyword Research
To do keyword research follow the following steps:
<
ol>
Drupal.org SEO Checklist
When reviewing a piece of content for the new Drupal redesign, we want to look at the following elements:
<
ul>
3/19 Sprint - Updates to Download and Extend / Search
This is the current status of the d.o redesign as it relates to Download and Extend along with Search.
Bill O'Connor and Keith Jay continue to be the project leads for this section. Keith and I reviewed and attempted to resolve several issues related to the implementation of Solr and the filters on the D&E section. Several advancements were made in the handling of Solr on staging 5, but we are still running into blockers. After hitting a few blocking issues, we shifted our focus to themeing and management of images on the D&E pages.
Blocking Solr issues:
Read moreDrupal.Org Local Install Guide for Redesign Implementers
Requirements
PHP 5.2 or later
Java 1.5 or later
1. Checkout the latest version of Drupal from the redesign SVN branch.
cd to the directory you would like to install the site in.
Create an empty database and update settings.php as you would for any other site.




