Wagtail

To add custom fields, open your models.py file and import specific field types from django.db.models such as CharField, TextField, or RichTextField. Inside your inherited Page class, define these fields as class attributes just like in standard Django development. After adding your fields, run python manage.py makemigrations in your terminal to generate the database instructions. Next, execute python manage.py migrate to apply those schema changes to your active database. Finally, include these fields in your page's content_panels definition so they appear in the administrative editing interface for content creators.

The routing mechanism operates via a tree-traversal algorithm that matches URL path components against the nested node paths stored in the database. When an incoming request hits the WSGI application, Wagtail's Site middleware identifies the correct root page based on the incoming HTTP Host header. The request path is then split into segments and evaluated recursively down the tree nodes using modified pre-order tree traversal patterns. Once the deepest matching page node is identified, the system instantiates the corresponding Python model class and invokes its custom route method to handle remaining URL sub-paths.

To configure headless endpoints, you need to enable the built-in wagtail.api.v2 module within your Django installed applications settings. Next, create an api.py file in your app directory and register your custom page models by subclassing Wagtail's PageViewSet or PagesAPIEndpoint. Include the API router URLs inside your project's main urls.py file under a designated path like api/v2/. You can then send GET requests to endpoint URLs such as /api/v2/pages/ to retrieve fully serialized JSON representations of your content tree, including all StreamField blocks and custom metadata.

While WordPress relies on a flat post-type structure supplemented by plugin-heavy page builders like Elementor, Wagtail is built on Django and enforces strict, code-defined data models. This structural difference means Wagtail websites are significantly more secure, performant, and resistant to malicious plugin vulnerabilities. Additionally, Wagtail's StreamField gives editors modular layout control without letting them break underlying HTML templates, whereas WordPress builders frequently output bloated, difficult-to-maintain markup. Wagtail is fundamentally designed for Python engineers and professional editorial teams, whereas WordPress targets general consumers.

This error occurs when the database lacks a default Site record matching the incoming domain name or port number of your request. To fix this, log into your Django administrative dashboard at /admin/, navigate to the Settings section, and click on Sites. Ensure that you have created a Site object whose hostname matches your current local address, such as localhost or 127.0.0.1, and that the port number aligns with your development server setting. Alternatively, you can seed this default site programmatically by writing a custom data migration or management command using Wagtail's Site.objects.get_or_create() API.