To see what is indexed on each entity, use the Solr Devel module.

To debug the requests that get sent to Solr with the apachesolr module, you can use the devel module to dpm the $params variable in the DrupalApacheSolrService::search() method. As of this writing, that means doing something like this at around line 936 in Drupal_Apache_Solr_Service.php:

Here is how to track events for Google Analytics. There used to be a lot more information here however, now, the best way to learn is to visit the following references:

Note 02 28 2014: This article shows syntax for both the old deprecated way using ga.js and also the new recommended way, using analytics.js. The old way will still work for awhile. This following link shows how to convert old code to new code https://developers.google.com/analytics/devguides/collection/upgrade/reference/gajs

A friend of mine said this: "if you are ever writing scripts and want a native mac notification - this is awesome: https://github.com/alloy/terminal-notifier"

This was taken from Karen Stevenson's blog post here: http://www.lullabot.com/blog/article/sending-drupal-site-retirement

Heres how to hide the administration menu from the admin_menu module when not on a page that is using the admin theme.

Here's a command that was used on a project I worked on that shows the number of lines of custom code and total lines of code in a project:

If the default behavior of the apachesolr module doesn't cut it for you, you might want to perform some custom queries or add some custom fields to the index.

There are contributed modules that will help with this that are listed below. You can also use Form API's #attributes to add in an HTML5 placeholder. Here's an example using Drupal Form API:

Thanks to Dan Shumaker for this: