Commits

Bruno Renié committed ee2b8c7

Using html+django code blocks instead of jinja ones

Comments (0)

Files changed (1)

docs/source/templates.rst

 * **On a per-template basis**: simply add this line on the top of the template
   where you need geoportal's template tags:
 
-  .. code-block:: jinja
+  .. code-block:: html+django
 
       {% load geoportal_tags %}
 
 javascript library on each page that displays a map. This is achieved by
 adding the following in the ``head`` section of your template:
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_js %}
 
 
 Syntax:
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_map field [option1=value, option2=other_value] [as var_name] %}
 
 simplest way to display a geographic field is (assuming you have a
 ``model_instance`` variable in your template context):
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_map model_instance.geo_field %}
 
 some further customization, you can get this variable in your template
 context:
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_map geo_field as var_name %}
 
 Here is an example of rendering a map with ``option1`` set to ``1`` and
 ``option2`` set to ``ff0000``:
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_map model_instance.geo_field option1=1, option2=ff0000 %}
 
 Option values can be static strings or template variables. If ``some_value``
 is available in the template context, calling
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_map model_instance.geo_field option1=some_value %}
 
 
 Let's finish with an example:
 
-.. code-block:: jinja
+.. code-block:: html+django
 
     {% geoportal_map model_instance.point color=ff0000, opacity=0.7, zoom=14, width=300, height=300 %}