From ed2b8ca14dad2c70fb2fb892143d250c49c9bd38 Mon Sep 17 00:00:00 2001 From: Matt Westcott Date: Wed, 30 Nov 2016 13:27:29 +0000 Subject: [PATCH] Add note that wagtailforms is not a replacement for Django forms --- docs/reference/contrib/forms.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/reference/contrib/forms.rst b/docs/reference/contrib/forms.rst index 50ec655389d..e56d6a4279a 100644 --- a/docs/reference/contrib/forms.rst +++ b/docs/reference/contrib/forms.rst @@ -6,6 +6,8 @@ Form builder The ``wagtailforms`` module allows you to set up single-page forms, such as a 'Contact us' form, as pages of a Wagtail site. It provides a set of base models that site implementers can extend to create their own ``FormPage`` type with their own site-specific templates. Once a page type has been set up in this way, editors can build forms within the usual page editor, consisting of any number of fields. Form submissions are stored for later retrieval through a new 'Forms' section within the Wagtail admin interface; in addition, they can be optionally e-mailed to an address specified by the editor. +.. note:: + **wagtailforms is not a replacement for** `Django's form support `_. It is designed as a way for page authors to build general-purpose data collection forms without having to write code. If you intend to build a form that assigns specific behaviour to individual fields (such as creating user accounts), or needs a custom HTML layout, you will almost certainly be better served by a standard Django form, where the fields are fixed in code rather than defined on-the-fly by a page author. See the `wagtail-form-example project `_ for an example of integrating a Django form into a Wagtail page. Usage ~~~~~