Further, its difficult to locate information about generic relations on any
of the following pages:

   - http://docs.djangoproject.com/en/dev/
   - http://docs.djangoproject.com/en/dev/topics/db/models/#topics-db-models
   -
   http://docs.djangoproject.com/en/dev/ref/models/fields/#ref-models-fields

Doing search on google leads to
http://www.djangoproject.com/documentation/models/generic_relations/, which
is not really the right place to learn about them, only some example usage.

The actual information is available on "Content Types" page [
http://docs.djangoproject.com/en/dev/ref/contrib/contenttypes/], which is
very non intuitive.

Recommendations:

   - Make model fields reference page [
   http://docs.djangoproject.com/en/dev/ref/models/fields/#ref-models-fields]
   either include these fields, or link to the content type page where they
   are, currently searching on that page for GenericForeignKey gives no
   results.
   - Make generic relations a top level item on documents page [
   http://docs.djangoproject.com/en/dev/]

I generally get the feeling that there are bit too many pages, we can make
the entire thing better by clubbing related things together. Documentation
should be organized from consumption point of view, and we can identify the
following main class of consumptions:

   - somebody learning django -- devote a page for them
   - somebody writing models, containing db, queries, models, fields, custom
   fields etc
   - somebody writing views, contain request/response details, cookies,
   meta, urls, shortcut functions etc
   - somebody working with templates, standard tags and filters, writing
   own, shortcuts
   - deployment
   - installations: one page for windows, another for mac etc.

I am suggesting we include some "power pages" for the above use cases, which
just links to everything you need to know when doing this task, which is
already available in our documentation section [may be even including
offisite info].

On Sun, Jul 5, 2009 at 1:05 PM, Amit Upadhyay <[email protected]> wrote:

> Hi,
>
> I find http://docs.djangoproject.com/en/dev/topics/db/ page quite
> inadequate. If I was doing that page I would include links to the following
> pages, along with the ones that are there:
>
>    - (Model Field Rerence, where all standard fields are listed)
>    http://docs.djangoproject.com/en/dev/ref/models/fields/
>    - (Writing Custom Model Fields)
>    http://docs.djangoproject.com/en/dev/howto/custom-model-fields/
>
> The content of these pages used to be clubbed with
> http://docs.djangoproject.com/en/dev/topics/db/models/, which was very
> handy, I have to open just one page, and all relevant information for
> writing models is there, now I have to keep on searching. So I would at the
> least add the links to the above to pages prominently on the top or on the
> sidebar, as of now they are quite difficult to find.
>
> Please merge the three pages together, or at least put the cross links
> prominently.
>
> Will create a patches if given a go ahead.
>
> --
> Amit Upadhyay
> www.amitu.com
> +91-9820-295-512
>



-- 
Amit Upadhyay
www.amitu.com
+91-9820-295-512

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to