Context Navigation

Changes between Initial Version and Version 1 of Ticket #25702

-              initial
+              v1
 While not going to all the extend of what django-cripsy-forms or another project is doing, //fieldset// is an already known and used convention accross the django project and allowing it in standard forms seems like a natural and intuitive choice.
+Regarding the API, I'm wondering if puting the //fieldset// attribute in the //Meta// class doesn't make more sens since it is already used (only for the //ModelForm//?) to specify options and this will avoid a conflict with currently existing fields named //fieldset//.
+This would look like this:
+{{{#!python
+from django import forms
+class ContactForm(forms.Form):
+    subject = forms.CharField(max_length=100)
+    message = forms.CharField(widget=forms.Textarea)
+    sender = forms.EmailField()
+    cc_myself = forms.BooleanField(required=False)
+    class Meta:
+        fieldset = (
+            (None, {
+                "fields": (('sender', 'cc_myself'),),
+            }),
+            ("Content", {
+                "fields": ("subject", "message"),
+            }),
+        )
+}}}
 [=#point1 (1)] http://django-crispy-forms.readthedocs.org/en/latest/layouts.html