0
0
mirror of https://github.com/wagtail/wagtail.git synced 2024-12-01 11:41:20 +01:00

documentation - fix a few internal references

This commit is contained in:
LB Johnston 2022-07-20 17:09:59 +10:00 committed by LB (Ben Johnston)
parent 8cdb3f3a60
commit c8d1a6b00a
2 changed files with 5 additions and 3 deletions

View File

@ -16,7 +16,7 @@ Multi-site configuration is a single code base, on a single server, connecting t
Wagtail supports multi-site out of the box: Wagtail comes with a [site model](wagtail.models.Site). The site model contains a hostname, port, and root page field. When a URL is requested, the request comes in, the domain name and port are taken from the request object to look up the correct site object. The root page is used as starting point to resolve the URL and serve the correct page. Wagtail supports multi-site out of the box: Wagtail comes with a [site model](wagtail.models.Site). The site model contains a hostname, port, and root page field. When a URL is requested, the request comes in, the domain name and port are taken from the request object to look up the correct site object. The root page is used as starting point to resolve the URL and serve the correct page.
Wagtail also comes with [site settings](settings). _Site settings_ are 'singletons' that let you store additional information on a site. For example, social media settings, a field to upload a logo, or a choice field to select a theme. Wagtail also comes with [site settings](site_settings). _Site settings_ are 'singletons' that let you store additional information on a site. For example, social media settings, a field to upload a logo, or a choice field to select a theme.
Model objects can be linked to a site by placing a foreign key field on the model pointing to the site object. A request object can be used to look up the current site. This way, content belonging to a specific site can be served. Model objects can be linked to a site by placing a foreign key field on the model pointing to the site object. A request object can be used to look up the current site. This way, content belonging to a specific site can be served.

View File

@ -1,3 +1,5 @@
(site_settings)=
# Settings # Settings
The `wagtail.contrib.settings` module allows you to define models that hold The `wagtail.contrib.settings` module allows you to define models that hold
@ -83,7 +85,7 @@ class SiteSpecificImportantPages(BaseSiteSetting):
] ]
``` ```
You can also customise the edit handlers [like you would do for `Page` model](/advanced_topics/customisation/page_editing_interface.html#customising-the-tabbed-interface) with a custom `edit_handler` attribute: You can also customise the edit handlers [like you would do for `Page` model](customising_the_tabbed_interface) with a custom `edit_handler` attribute:
```python ```python
from wagtail.admin.panels import TabbedInterface, ObjectList from wagtail.admin.panels import TabbedInterface, ObjectList
@ -126,7 +128,7 @@ class SiteSpecificSocialMediaSettings(BaseSiteSetting):
verbose_name = "Site-specific social media settings" verbose_name = "Site-specific social media settings"
``` ```
For a list of all available icons, please see the [styleguide](/contributing//styleguide.html). For a list of all available icons, please see the [styleguide](styleguide).
## Using the settings ## Using the settings