anchor.diff:  
   == Builtin contrib modules
   
  -*django-jinja* comes with some additional contrib modules that adapts limited set of external
  -django apps for use it easy from jinja templates. Please note that in order to use any of these
  -contrib modules, you'll need to install the relevant dependent package yourself first.
  +*django-jinja* comes with some additional contrib modules that adapt a limited set of external
  +django apps for easy use from jinja templates. Please note that in order to use any of these
  +contrib modules, you'll need to install the relevant dependent packages yourself first.
   
   
   [NOTE]
  
positive.code: explicit calls to callable from templates, has better performance and has a plugin
  system, etc ...
  
  Django comes with jinja backend, why should I use *django-jinja*?
  
  The Django builtin backend has very limited set of features if we compare it with
  the django template engine and in my opion is not very usable because it does not
  integrates well with the rest of django such as its filters, template tags and
  and preloading of templatetags among others.
  
  *django-jinja* comes to the rescue and add everything missing. This is a brief
  list of differences with django's built-in backend:
  
  - Auto-load templatetags compatible with Jinja2 on same way as Django.
  - Find the templates as usual in `"<appname>/templates"` directory instead
    of `"<appname>/jinja2"`  directory (you can overwrite this behavior, see below).
  - Django templates can coexist with Jinja2 templates without any problems.
  
negative.code: === Regex based template matching
  
  By default, *django-jinja* uses the extension as method to match templates, but if
  it is not enough, you can extend it using regular experessions:
  
  [source, python]
  ----
  