As I have said at Amazon and in the discussion that I unsuccessfully tried to kick-start in the theming chapters discussion board page, I think this book does a great job of explaining the "how" of template overrides, theme functions, theme hook suggestions, pre/process functions, and the render api's alter hooks in building and customizing a site from scratch.
Via Moshe Weitzman: the long story is at http://drupal.org/node/231298. or you could just read the docs in the file.
sites/default.sites.php
[Searched words]
filter a git log
filter log output command line
grep git history
git view commit
git re-apply commit
To do a simple search through Git's commit messages (another reason to write useful information when committing!) *and* the accompanying diffs, you can use to search for dgd7.org:
git log -Sdgd7.org
Shows us, as one of a few matches:
commit 89bec60d085839fff22fdd4e387063717282edc6
Author: Benjamin
Date: Tue Jun 15 19:47:23 2010 -0400
How to set up API module locally.
What's the best online use of API module for third-party modules to link to?
(or the earlier http://api.lullabot.com ?)
Would there be any reason to host our own?
The Drupal community likes to brag about the thousands of contributed modules, but there's a little secret that should be publicly and widely stated: If you install 1,000 modules on your site, your doing it so wrong you'll probably need a complete Drupalectomy.
Look at the code.
Read the tests.
The community wrote the code because they love you. They wrote the documentation to prove it.
It's all right to google first. It may be a good idea to pick a standard practice, code first or web search first.
This module is useful when we have more than one content type.
We might not want to use this module if we have content type
drush dl content_type_overview
Greg Dunlap (heyrocker)
http://drupal.org/project/examples
Heather James sings the project's praises:
