Django’s form widgets are rendered using Django’s template engines\nsystem.
\nThe form rendering process can be customized at several levels:
\nWidgets can specify custom template names.
Forms and widgets can specify custom renderer classes.
A widget’s template can be overridden by a project. (Reusable applications\ntypically shouldn’t override built-in templates because they might conflict\nwith a project’s custom templates.)
The rendering of form templates is controlled by a customizable renderer class.\nA custom renderer can be specified by updating the FORM_RENDERER\nsetting. It defaults to\n'django.forms.renderers.DjangoTemplates'.
You can also provide a custom renderer by setting the\nForm.default_renderer attribute or by using the renderer argument\nof Widget.render().
Use one of the built-in template form renderers or implement your own. Custom renderers\nmust implement a render(template_name, context, request=None) method. It\nshould return a rendered templates (as a string) or raise\nTemplateDoesNotExist.
DjangoTemplatesLink to this heading#This renderer uses a standalone\nDjangoTemplates\nengine (unconnected to what you might have configured in the\nTEMPLATES setting). It loads templates first from the built-in form\ntemplates directory in django/forms/templates and then from the installed\napps” templates directories using the app_directories loader.
If you want to render templates with customizations from your\nTEMPLATES setting, such as context processors for example, use the\nTemplatesSetting renderer.
Jinja2Link to this heading#This renderer is the same as the DjangoTemplates renderer except that\nit uses a Jinja2 backend. Templates\nfor the built-in widgets are located in django/forms/jinja2 and installed\napps can provide templates in a jinja2 directory.
To use this backend, all the widgets in your project and its third-party apps\nmust have Jinja2 templates. Unless you provide your own Jinja2 templates for\nwidgets that don’t have any, you can’t use this renderer. For example,\ndjango.contrib.admin doesn’t include Jinja2 templates for its widgets\ndue to their usage of Django template tags.
TemplatesSettingLink to this heading#This renderer gives you complete control of how widget templates are sourced.\nIt uses get_template() to find widget\ntemplates based on what’s configured in the TEMPLATES setting.
Using this renderer along with the built-in widget templates requires either:
\n'django.forms' in INSTALLED_APPS and at least one engine\nwith APP_DIRS=True.
Adding the built-in widgets templates directory in DIRS of one of your template engines. To generate that path:
import django\ndjango.__path__[0] + '/forms/templates' # or '/forms/jinja2'\nUsing this renderer requires you to make sure the form templates your project\nneeds can be located.
\nWidget templates receive a context from Widget.get_context(). By\ndefault, widgets receive a single value in the context, widget. This is a\ndictionary that contains values like:
name
value
attrs
is_hidden
template_name
Some widgets add further information to the context. For instance, all widgets\nthat subclass Input defines widget['type'] and MultiWidget\ndefines widget['subwidgets'] for looping purposes.
Each widget has a template_name attribute with a value such as\ninput.html. Built-in widget templates are stored in the\ndjango/forms/widgets path. You can provide a custom template for\ninput.html by defining django/forms/widgets/input.html, for example.\nSee Built-in widgets for the name of each widget’s template.
To override widget templates, you must use the TemplatesSetting\nrenderer. Then overriding widget templates works the same as overriding any other template in your project.