Added links and more info to documentation (#9517)

* Docs: Mention Wagtail’s usage of Django’s default user model by default (Temidayo Azeez)
 * Docs: Add links to treebeard documentation for relevant methods (Temidayo Azeez)

Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>

CHANGELOG.txt

@@ -35,6 +35,8 @@ Changelog
  * Docs: Mention the importance of passing `request` and `current_site` to `get_url` on the performance documentation page (Jake Howard)
  * Docs: Add documentation for `register_user_listing_buttons` hook (LB (Ben Johnston))
  * Docs: Add development (contributing to Wagtail) documentation notes for development on Windows (Akua Dokua Asiedu)
+ * Docs: Mention Wagtail’s usage of Django’s default user model by default (Temidayo Azeez)
+ * Docs: Add links to treebeard documentation for relevant methods (Temidayo Azeez)
  * Maintenance: Remove unsquashed `testapp` migrations (Matt Westcott)
  * Maintenance: Upgrade to Node 18 for frontend build tooling (LB (Ben) Johnston)
  * Maintenance: Run Python tests with coverage and upload coverage data to codecov (Sage Abdullah)

CONTRIBUTORS.rst

@@ -667,6 +667,7 @@ Contributors
 * Fatuma Abdullahi
 * Elizabeth Bassey
 * Suyash Singh
+* Temidayo Azeez
 
 Translators
 ===========

docs/getting_started/integrating_into_django.md

@@ -109,7 +109,7 @@ With this configuration in place, you are ready to run `python manage.py migrate
 
 ## User accounts
 
-Superuser accounts receive automatic access to the Wagtail admin interface; use `python manage.py createsuperuser` if you don't already have one. Custom user models are supported, with some restrictions; Wagtail uses an extension of Django's permissions framework, so your user model must at minimum inherit from `AbstractBaseUser` and `PermissionsMixin`.
+Wagtail uses Django’s default user model by default. Superuser accounts receive automatic access to the Wagtail admin interface; use `python manage.py createsuperuser` if you don't already have one. Custom user models are supported, with some restrictions; Wagtail uses an extension of Django's permissions framework, so your user model must at minimum inherit from `AbstractBaseUser` and `PermissionsMixin`.
 
 ## Start developing
 

docs/releases/4.2.md

@@ -51,6 +51,8 @@ depth: 1
  * Mention the importance of passing `request` and `current_site` to `get_url` on the [performance](performance) documentation page (Jake Howard)
  * Add documentation for [`register_user_listing_buttons`](register_user_listing_buttons) hook (LB (Ben Johnston))
  * Add development (contributing to Wagtail) documentation notes for [development on Windows](development_on_windows) (Akua Dokua Asiedu)
+ * Docs: Mention Wagtail’s usage of Django’s default user model by default (Temidayo Azeez)
+ * Docs: Add links to treebeard documentation for relevant methods (Temidayo Azeez)
 
 ### Maintenance
 

wagtail/models/__init__.py

@@ -1124,7 +1124,7 @@ class Page(AbstractPage, index.Indexed, ClusterableModel, metaclass=PageBase):
         such as updating the ``url_path`` value of descendant page to reflect changes
         to this page's slug.
 
-        New pages should generally be saved via the ``add_child()`` or ``add_sibling()``
+        New pages should generally be saved via the `add_child() <https://django-treebeard.readthedocs.io/en/latest/mp_tree.html#treebeard.mp_tree.MP_Node.add_child>`_ or `add_sibling() <https://django-treebeard.readthedocs.io/en/latest/mp_tree.html#treebeard.mp_tree.MP_Node.add_sibling>`_
         method of an existing page, which will correctly set the ``path`` and ``depth``
         fields on the new page before saving it.