Wagtail (Django) Installation and Production Setup

Wagtail (Django) Installation and Production Setup

You chose Django, but content managers want an admin panel like WordPress, and developers want full control over the data model. Wagtail fits this scenario perfectly: Python, Django, StreamField for flexible templates, and a built-in workflow for publishing. However, the real power unfolds only with proper production configuration. We are a team with deep Django/Wagtail expertise—here’s how to avoid typical pitfalls and ship a stable system.

Why Choose Wagtail for a Django Project?

Wagtail transforms Django from a developer framework into a full-fledged CMS for editors. Unlike other Django CMS solutions, Wagtail offers a built-in WYSIWYG editor, image management, A/B testing, and a page editor for design without code. For developers, it provides a clear page inheritance model, hooks, and signals. Paired with Redis and Cloudflare, it handles traffic up to 1 million visitors per month.

Typical Problems When Configuring Wagtail for Production

Even experienced Django developers make mistakes at the intersection of media storage and caching. Here are three common scenarios:

Problem 1: Conflict between WhiteNoise and S3 for media. If static files are served via WhiteNoise and media via S3, you must set WHITENOISE_USE_FINDERS = False, otherwise 404 errors on files occur. The solution is a clear STORAGES configuration with separated backends.

Problem 2: Redis serialization errors with StreamField. Wagtail stores StreamField as JSON in the database, but when caching, it goes into Redis. Without a custom JSON encoder, stacktraces appear in logs. We always add 'SERIALIZER': 'django_redis.serializers.json.JSONSerializer'.

Problem 3: Slow StreamField migrations. When adding a new block to StreamField, migrations can fail with a TypeError. We use null=True, blank=True by default and manually dump data before makemigrations.

How We Configure Wagtail Turnkey

Our typical stack: Python, Django, Wagtail, PostgreSQL, Redis, Docker + Gunicorn + Nginx. For media, we use S3 (DigitalOcean Spaces) with a CDN via Cloudflare. Real-world case: we deployed Wagtail for a media portal with 50,000+ pages. The initial LCP was 4.2 seconds due to lack of caching and unoptimized images. We implemented:

• Page caching via WAGTAIL_CACHE_BACKEND = 'default' with Redis.
• ISR (Incremental Static Regeneration) using a combo of Wagtail + Cloudflare Workers.
• Image optimization via wagtailimages with WebP and srcset.

The result: LCP dropped to 1.1 seconds, and page build time fell from 600 ms to 50 ms.

Comparison: Wagtail vs Django CMS

Work Phases

How to Boost Wagtail Performance?

After basic installation, optimize caching and media. We set WAGTAIL_CACHE_BACKEND = 'default' with Redis. For images, we enable WebP and srcset via wagtailimages. In production, configure a CDN for static and media—this reduces server load by 3–5 times.

Timelines and Cost

Basic setup with PostgreSQL, Redis, S3, and Docker takes from 4 to 8 hours. If you need content model customization, CRM integration, or data migration, the timeline extends to 2–5 days. Cost is calculated individually after audit—we value transparency and don’t inflate hours.

What You Get After Setup?

• Fully functional project with ready-to-use Docker Compose and Dockerfile.
• Admin panel credentials with superuser.
• Deployment and operation documentation (including core commands).
• Team training (1 hour – Wagtail admin basics).
• Warranty on all work – one month of free support after deployment.

We are certified Django specialists with 20+ Wagtail projects. Contact us to discuss your project—we’ll help with hosting choice, scaling, and optimization. Order a turnkey Wagtail installation today.

For more details, see the official Wagtail documentation.

Management commands:

python manage.py migrate
python manage.py collectstatic
python manage.py rebuild_references_index    # reference index
python manage.py wagtail_update_image_renditions  # recreate renditions
python manage.py search_garbage_collect      # clean search

Wagtail installation with PostgreSQL and S3 for production – 4–8 hours.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.