#9500: Put the Google search that is in the main documentation page on *each*
documentation page.
--------------------------------------+-------------------------------------
Reporter: Beetle_B | Owner: nobody
Status: closed | Milestone:
Component: Django Web site | Version: 1.0
Resolution: fixed | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by kmtracey):
For things that are valid requests but happen to be already implemented
it's a tossup whether I call them invalid or fixed. I really want an
"already fixed" but we don't have that. I don't think it matters all that
much since so far as I know nobody tracks stats on tickets closed by
resolution or anything like that.
As for the placement of the Search yes I think it's debatable where is
best. I too did not realize at first it was on every page, which argues
always at the top might be better. On the other hand that seems to put
undue emphasis on getting away from the current page vs. showing you
what's available on the current page via the Contents, so I can see why
Contents come first.
--
Ticket URL: <http://code.djangoproject.com/ticket/9500#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
