This came up in discussion of the LDAP Backend patch (#2507). We need to document the backend, but there isn't a clear place to put the documentation. The authentication doc is already pretty long and, in my opinion, would feel rather cluttered adding documentation for using an LDAP backend (which will take a decent sum of space).
I'll quote from the ticket: "The documentation issue is that djangoproject.com has no way to provide subdirectories (in this case /authentication/contributed/) which would place docs for this in an ugly url (/contributed_authenticators/ and /ldap_autenticator/), my idea was to create a new doc (/authentication/contributed/ or /contributed_authenticators/) to explain small contribued authenticators and link bigger ones like (/authentication/contributed/ldap/ or /ldap_authenticator/) just to be ready in case more authenticators get contributed. As you see URLs are far more clean with some directory depth support so I've left the docs where they are until we get this discussed ;)" So what's the best place to put docs for things like bundled auth backends? I imagine that there are a lot of un-documented parts of Django that would make sense to have their own page that is a child to another primary page. Thanks, Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601
pgpggYe5mCach.pgp
Description: PGP signature
