app/django/contrib/admindocs/templates/admin_doc/index.html
author Sverre Rabbelier <srabbelier@gmail.com>
Fri, 23 Jan 2009 21:20:33 +0000
changeset 935 09f47e08f805
parent 323 ff1a9aa48cfd
permissions -rw-r--r--
Adust the as_table tag to render a pick link if appropriate The templates are adjusted to pass on a 'reference' value, which is the url_name of the view from which the entity should be picked. The as_table (and related) function(s) construct and then pass on this argument and enable takes_contex so that we have access to the context of the enclosing template. We only extract ReferenceProperties that end with '_link_id' since that is how all RP's are currently named. It is not possible to create a field with the same name as the RP, as GAE will try to interpret it's contents as the key of an entity before even calling any function we can override. Patch by: Sverre Rabbelier

{% extends "admin/base_site.html" %}
{% load i18n %}
{% block breadcrumbs %}<div class="breadcrumbs"><a href="../">Home</a> &rsaquo; Documentation</div>{% endblock %}
{% block title %}Documentation{% endblock %}

{% block content %}

<h1>Documentation</h1>

<div id="content-main">
  <h3><a href="tags/">Tags</a></h3>
  <p>List of all the template tags and their functions.</p>

  <h3><a href="filters/">Filters</a></h3>
  <p>Filters are actions which can be applied to variables in a template to alter the output.</p>

  <h3><a href="models/">Models</a></h3>
  <p>Models are descriptions of all the objects in the system and their associated fields. Each model has a list of fields which can be accessed as template variables.</p>

  <h3><a href="views/">Views</a></h3>
  <p>Each page on the public site is generated by a view. The view defines which template is used to generate the page and which objects are available to that template.</p>

    <h3><a href="bookmarklets/">Bookmarklets</a></h3>
    <p>Tools for your browser to quickly access admin functionality.</p>
</div>

{% endblock %}