Contributed Module Ideas

A way for OG group administrators / members to "feature" (in the real meaning of the word) some general content from other areas of the site, making it appear in group views with the content from that group. New table would be nid, gid, and timestamp when node was featured; the last field would be the one accessible to views.

I want, in a site, to add relationships between nodes with a taxonomy vocabulary.

For exemple i add a vocabulary "branches" with 1.x, 2.x, 3.x term. Then i create some page for documentation : introduction, usage, etc.

I want to display a block in my page with the related pages, for exemple when i'm on introduction for the 1.X branches, i would like to add a link to introduction of the 2.x and 3.x branches. Maybe node relationships can do that.

Would some one be available to become co-maintainer of comment_subject?
he/she will only need to commit RTBC patches to a new 2.x branch
since I will attend the issue queue and provide patches against 2.x-dev to support integration with token

I'm maintaining a patch for comment_subject module to support integration with token
it seems to be a "must have" feature
which allow each site to choose how to solve http://www.lullabot.com/articles/drupal_usability_comment_configuration

I'd like to build a "permalink" module that gives consistent links to comments. Here are a couple of the requirements:

• The permalink should be available on the comment itself
• The permalink should stay the same regardless of where the comment is - that's particularly a problem on nodes with hundreds of active commenters and with a page limit (like 20 comments per page)
• The permalink should go directly to the comment, through use of anchors in the url like #comment-CID

Create a module that can be leveraged by other modules (via hook) that uses the output buffer; pass by reference; print at end, write to core page cache if enabled. Make http://sourceforge.net/projects/simplehtmldom/ or another package a required download in the libraries dir, allowing other modules to leverage this inside their hook.

Modules that could benefit:
Boost, Beautify, Parallel, CSS Gzip

We are currently seeking an experienced Drupal developer to start immediately. The project involves moving an existing site to Drupal plus optimizing for SEO, adding new features, and customizing modules. The website already has several thousand pages but requires a complete revamp.

This is a short term contract with the potential for longer term commitments on several ongoing projects.

Location: Los Angeles, California

Type: Contract Job

Requirements:
-Proven experience building and supporting Drupal 6 sites that are feature-rich, optimized for SEO, and with high traffic.
-Solid skills in developing, customizing, and integrating modules.

(Wow, this turned out longer than I anticipated. tl;dr version: This module would create ancillary short paths for your nodes which will make life easier when linking to them with Twitter and the like, without the hassle of external services.)

Create a module that automatically rewrites various tags with a src attribute to use a subdomain. This /sites/all/files/css/mystyle.css to //data1.example.com/sites/all/files/css/mystyle.css. Have it handle the following html tags

• link
• style
• script
• img
• iframe
• embed
• ???

For sites that like to use a cache to serve the full page (boost, drupal core cache, ect...), but still would like to have more dynamic content in a block; loading of blocks via ajax seems like a good way to accomplish this. I've already accomplished this with the boost module and I'm wondering if/how I should abstract this out to be a generalized solution.

Simple way

Below is the simple way to do it, for one or 2 blocks it works. For anything more then that it would probably have a negative impact since it's doing a full bootstrap for each block.

blocka.php