Right now if you do a google search for "drupal annotate.js" the first result is a packging whitelist node:

https://drupal.org/node/1904824

This is silly and totally confusing. Heck, it took me ten minutes to figure out what it was. Is there any reason these can't just all be unpublished? They're for internal use only.

Comments

drumm’s picture

Title: Unpublish packaging whitelist nodes » Hide/explain packaging whitelist nodes

This View, https://drupal.org/packaging-whitelist, only shows published nodes. I think we'll want to keep that, since it is a relatively-normal setup. And we won't have to worry about potential permissions-related problems.

For search results, we recently installed metatag for #2233753: Add ability for webmasters to flag posts no-index, no follow . We can configure the whitelist content type to "Prevent search engines from indexing this page."

If someone does land on the page, drupalorg could insert an explanation, and link to https://drupal.org/packaging-whitelist.

gdd’s picture

Ah I hadn't realized about the public view of whitelisted libraries. The proposed solution makes good sense. Thanks!

damienmckenna’s picture

drumm’s picture

Status: Active » Closed (outdated)
Related issues: +#3388668: Dismantle code which supported drush make distribution packaging