I don't know if it is possible or practical, but I learned long ago that the way to get relevant search results on Drupal is to use Google site search.

If handbook paged were aliased to /handbooks/* then you could search using google site:drupal.org/handbooks/ and get only matching handbook pages and skip old forum topics referring to version 4.1 techniques, etc.

Here is a sample glossary page. Where would be a good place to put this? This is related to the thread I started about documenting comments. Please see
http://drupal.org/node/43452. While these terms are not frequently asked questions, they do cause confusion for the newcomer.

Here are some terms and acronyms that are not Drupal terms that are used on this site that a newcomer might not know.

GLOSSARY

IDE
Intergrated Development Environment. Used here in relationship to debuggers.

I have a to-do idea which I might volunteer for. As a newcomer to Drupal, I spend hours if not days browsing this site every time I have a question. I find that many times the same questions are asked over and over. And some very kind people take the time answer them. The quality of the answers are uneven. Sometimes the question gets an answer that is perfect, complete and clear. Sometimes the question gets an answer that's confusing. This may relate to how much hurry someone was in, how much experience the answerer has, a version change, etc. Sometimes you'll see a little debate in the trail of comments about whether a solution will work or not.

Two examples of commonly asked questions are:
1) how to use taxonomy and the various add-on modules to create breadcrumbs a certain way
2) how to replace the default logo.

I would guess there are over 100 comments on each question. I am planning to put together a list of bookmarked comments that I think best answers each question. (As a newcomer, my judgment could be wrong.) I am thinking about contributing that back to the Drupal community. I browsed through the instructions about documentation. I don't want to step on anyone's toes, but I don't think I'm familiar enough yet with the Drupal site to figure out the best way to implement something like this in a way that would not be too time-consuming for me.

I thought I knew how Drupal's "clean" URLs interacted with Apache's mod_rewrite and the file system. The logical flow seems obvious after observing the following code in .htaccess:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

The Apache 1.3 documentation for RewriteCond says:

'-d' (is directory) Treats the TestString as a pathname and tests if it exists and is a directory.
'-f' (is regular file) Treats the TestString as a pathname and tests if it exists and is a regular file.

The code checks for a file or directory that matches the request and, if neither is found, rewrites the clean URL such that Drupal can handle it. But all is not as it seems. I expected RewriteCond %{REQUEST_FILENAME} !-f to require a complete match between the file system and the URL before failing.

Here is the caveat:
Apache will not rewrite a clean URL if Apache finds a file at the base of the Drupal installation whose name matches everything up to the first slash (/) in the request. As an added twist, Apache does the same if the file ends with .txt, .diff, and perhaps some other common extensions.

Here is how to demonstrate the quirk:

Why do:

http://drupaldocs.org/api/head/function/filter_xss_bad_protocol

and

http://drupaldocs.org/api/4.6/function/filter_xss_bad_protocol

return the same lines of code even though my actual Drupal install (4.6.5) has different code altogether for this function?

Hi,

is there any offline documentation available for drupal? Like the handbooks and the API documentation?

tnx!