mirror of
https://github.com/Hopiu/wagtail.git
synced 2026-04-26 17:44:48 +00:00
Removed a couple of under construction messages
This commit is contained in:
parent
8ea5054a1b
commit
05e55a3abb
2 changed files with 0 additions and 6 deletions
|
|
@ -3,9 +3,6 @@
|
|||
Displaying fields with the Editing API
|
||||
======================================
|
||||
|
||||
.. note::
|
||||
This documentation is currently being written.
|
||||
|
||||
Wagtail provides a highly-customizable editing interface consisting of several components:
|
||||
|
||||
* **Fields** — built-in content types to augment the basic types provided by Django
|
||||
|
|
|
|||
|
|
@ -1,9 +1,6 @@
|
|||
Pages
|
||||
=====
|
||||
|
||||
.. note::
|
||||
This documentation is currently being written.
|
||||
|
||||
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 ``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.
|
||||
|
|
|
|||
Loading…
Reference in a new issue