Voting starts in March for the Drupal Association Board election.
This is a terrible, terrible problem.
Across the board, the usability testing participants we tested at UMN did NOT understand that you could extend Drupal. There were a few reasons for this:
1. The word "Modules" means nothing to them. Some thought it means blocks, some thought it meant the site outline (sitemap), some thought it meant a part of the front page.
2. Once they got to that page and kind of got the jist of it, they thought that the options presented there were the extent of Drupal's functionality. The option to add additional modules wasn't discoverable.
3. Once they got to Drupal.org, it was incredibly jarring and people didn't realize they were still within the context of their site. The lack of integration was very challenging for people getting around.
Here were some possible solutions we brainstormed, but this really needs a larger community discussion:
"Develop tabbed interface to module list, to indicate there is more than what is included. Example:
1) Enabled modules
2) Disabled modules
- Enable (taken immediately to configure)
3) Add module
- Discover/Browse [drupal.org]
- Install to your site"
PASSED: [[SimpleTest]]: [MySQL] 41,240 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 41,242 pass(es). View
|#143||Tips for extending Drupal 1.png||39.19 KB||yoroy|