Project page redesign

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
Posted by Anonymous on April 25, 2011 at 11:15am
Last updated by tvn on Mon, 2012-02-06 15:45

Current Status - on hold

The current project (module, theme) page could do a better job of supporting both a site builder (someone choosing modules to use when building a Drupal site) and a module maintainer (someone responding to feature and support requests and planning a roadmap for future development hopefully with the assistance of co-maintainers). We'd like to find a way to support both these audiences better.

Reference

Earlier Prairie discussions

Relevant discussions elsewhere

Login or register to post comments ⋅ Categories:

Comments

Code standards compliance status in module page

Posted by rafamd on October 3, 2011 at 4:30pm
rafamd's picture

Wouldn't it be nice to have a coder module output available in the module page ? This could be an extra indicator of the module quality and also encourage contributors to follow the coding standards.

Like it ?

(In a nutshell: coder module analyzes any module's source files and reports minor/normal/critical warnings. It generates a detailed listing of all warnings and this summary: "Coder found 1 projects, 24 files, 3 critical warnings, 1 normal warnings, 0 warnings were flagged to be ignored")

This idea is inspired in this core issue.

I've made this proposal which

Posted by joachim on November 10, 2011 at 10:50am
joachim's picture

I've made this proposal which I think would help site builders discover useful modules:

Many projects on d.org have formed ecosystems around themselves, because they are extensible. Eg: Views, Drupal Commerce, Domain Access, and so on.

Sometimes these projects provide a list of related or helper projects in their project page, or in documentation pages, but these often end up being out of date because the people who maintain the ecosystem projects don't know about them or don't have access.

A partial solution to this has been the inclusion of some ecosystem terms in the 'Modules categories' taxonomy, but this has problems of its own:

- need to add more terms as more projects develop an ecosystem
- terms don't link back to projects

What I propose is that we let projects link to other projects:

- add a flag to project nodes that marks them as an 'ecosystem hub'
- add a noderef to project nodes that lets you select an ecosystem hub for the project.

So for example, Views would be flagged as a hub, and EVA would point to views.

Then on project pages we'd see:

- on a hub page, a block listing all projects that point to this node, ie all those in the ecosystem
- on an ecosystem page, a link or a block (design TBD) that says 'This project is a part of Views'.

(originally posted at http://drupal.org/node/1323826)

Prairie Initiative

Group organizers

Group categories

Prairie tags

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: