f588fcf249
- Move model reference to directly under the references section, not the reference/pages section - Move panel reference to directly under the references section, not the reference/pages section - Merge panel API with panels reference pages - Fix confusing heading levels in the page model recipes page - Fix title in model reference to align with docs style guide - Adopt US spelling for customize (panels) reference key
987 B
Pages
Wagtail requires a little careful setup to define the types of content that you want to present through your website. The basic unit of content in Wagtail is the {class}~wagtail.models.Page, and all of your page-level content will inherit basic webpage-related properties from it. But for the most part, you will be defining content yourself, through the construction of Django models using Wagtail's Page as a base.
Wagtail organizes content created from your models in a tree, which can have any structure and combination of model objects in it. Wagtail doesn't prescribe ways to organize and interrelate your content, but here we've sketched out some strategies for organizing your models.
The presentation of your content, the actual webpages, includes the normal use of the Django template system. We'll cover additional functionality that Wagtail provides at the template level later on.
---
maxdepth: 2
---
theory
model_recipes
queryset_reference