admindocs.txt 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146
  1. ========================================
  2. The Django admin documentation generator
  3. ========================================
  4. .. module:: django.contrib.admindocs
  5. :synopsis: Django's admin documentation generator.
  6. .. currentmodule:: django.contrib.admindocs
  7. Django's :mod:`~django.contrib.admindocs` app pulls documentation from the
  8. docstrings of models, views, template tags, and template filters for any app in
  9. :setting:`INSTALLED_APPS` and makes that documentation available from the
  10. :mod:`Django admin <django.contrib.admin>`.
  11. Overview
  12. ========
  13. To activate the :mod:`~django.contrib.admindocs`, you will need to do
  14. the following:
  15. * Add :mod:`django.contrib.admindocs` to your :setting:`INSTALLED_APPS`.
  16. * Add ``path('admin/doc/', include('django.contrib.admindocs.urls'))`` to
  17. your ``urlpatterns``. Make sure it's included *before* the
  18. ``'admin/'`` entry, so that requests to ``/admin/doc/`` don't get
  19. handled by the latter entry.
  20. * Install the docutils Python module (https://docutils.sourceforge.io/).
  21. * **Optional:** Using the admindocs bookmarklets requires
  22. ``django.contrib.admindocs.middleware.XViewMiddleware`` to be installed.
  23. Once those steps are complete, you can start browsing the documentation by
  24. going to your admin interface and clicking the "Documentation" link in the
  25. upper right of the page.
  26. Documentation helpers
  27. =====================
  28. The following special markup can be used in your docstrings to easily create
  29. hyperlinks to other components:
  30. ================= =======================
  31. Django Component reStructuredText roles
  32. ================= =======================
  33. Models ``:model:`app_label.ModelName```
  34. Views ``:view:`app_label.view_name```
  35. Template tags ``:tag:`tagname```
  36. Template filters ``:filter:`filtername```
  37. Templates ``:template:`path/to/template.html```
  38. ================= =======================
  39. Model reference
  40. ===============
  41. The **models** section of the ``admindocs`` page describes each model in the
  42. system along with all the fields, properties, and methods available on it.
  43. Relationships to other models appear as hyperlinks. Descriptions are pulled
  44. from ``help_text`` attributes on fields or from docstrings on model methods.
  45. A model with useful documentation might look like this::
  46. class BlogEntry(models.Model):
  47. """
  48. Stores a single blog entry, related to :model:`blog.Blog` and
  49. :model:`auth.User`.
  50. """
  51. slug = models.SlugField(help_text="A short label, generally used in URLs.")
  52. author = models.ForeignKey(
  53. User,
  54. models.SET_NULL,
  55. blank=True, null=True,
  56. )
  57. blog = models.ForeignKey(Blog, models.CASCADE)
  58. ...
  59. def publish(self):
  60. """Makes the blog entry live on the site."""
  61. ...
  62. View reference
  63. ==============
  64. Each URL in your site has a separate entry in the ``admindocs`` page, and
  65. clicking on a given URL will show you the corresponding view. Helpful things
  66. you can document in your view function docstrings include:
  67. * A short description of what the view does.
  68. * The **context**, or a list of variables available in the view's template.
  69. * The name of the template or templates that are used for that view.
  70. For example::
  71. from django.shortcuts import render
  72. from myapp.models import MyModel
  73. def my_view(request, slug):
  74. """
  75. Display an individual :model:`myapp.MyModel`.
  76. **Context**
  77. ``mymodel``
  78. An instance of :model:`myapp.MyModel`.
  79. **Template:**
  80. :template:`myapp/my_template.html`
  81. """
  82. context = {'mymodel': MyModel.objects.get(slug=slug)}
  83. return render(request, 'myapp/my_template.html', context)
  84. Template tags and filters reference
  85. ===================================
  86. The **tags** and **filters** ``admindocs`` sections describe all the tags and
  87. filters that come with Django (in fact, the :ref:`built-in tag reference
  88. <ref-templates-builtins-tags>` and :ref:`built-in filter reference
  89. <ref-templates-builtins-filters>` documentation come directly from those
  90. pages). Any tags or filters that you create or are added by a third-party app
  91. will show up in these sections as well.
  92. Template reference
  93. ==================
  94. While ``admindocs`` does not include a place to document templates by
  95. themselves, if you use the ``:template:`path/to/template.html``` syntax in a
  96. docstring the resulting page will verify the path of that template with
  97. Django's :ref:`template loaders <template-loaders>`. This can be a handy way to
  98. check if the specified template exists and to show where on the filesystem that
  99. template is stored.
  100. .. _admindocs-bookmarklets:
  101. Included Bookmarklets
  102. =====================
  103. One bookmarklet is available from the ``admindocs`` page:
  104. Documentation for this page
  105. Jumps you from any page to the documentation for the view that generates
  106. that page.
  107. Using this bookmarklet requires that ``XViewMiddleware`` is installed and that
  108. you are logged into the :mod:`Django admin <django.contrib.admin>` as a
  109. :class:`~django.contrib.auth.models.User` with
  110. :attr:`~django.contrib.auth.models.User.is_staff` set to ``True``.