- Easy to use for both developers and non-technical users alike

- Lots of built-in features making it relatively simple to build complex sites

- Highly customisable, so if any features you'd like aren't already included they can generally be added without too much difficulty

- Very detailed documentation Review collected by and hosted on G2.com.

- Limited frontend features compared to some other CMSs, although this is perhaps to be expected as Wagtail is a Django-based CMS Review collected by and hosted on G2.com.

Easy to set up and easy to manage. Speedy development time. Review collected by and hosted on G2.com.

I really can't think of anything! The easiest to use and best-maintained Python-based CMS out there. Review collected by and hosted on G2.com.

Simplicity and speed. Great community for support. Review collected by and hosted on G2.com.

The UI is a bit dated, but they're working on that Review collected by and hosted on G2.com.

Ability to house information and documentation Review collected by and hosted on G2.com.

There are soo many bugs in this "solution." Review collected by and hosted on G2.com.

Easy to setup

Great community

Support is really good with Slack Groups Review collected by and hosted on G2.com.

Not that many developers know Wagtail but improving.

Needs more pre-build plugins Review collected by and hosted on G2.com.

It contains lots of functionality and feels comprehensive overall Review collected by and hosted on G2.com.

It can sometimes be complicated to use/steep learning curve Review collected by and hosted on G2.com.

Easy to use, setup and enhance or combine with regular Django. Review collected by and hosted on G2.com.

A little slow at times. The text and formatting options are disciplined, sometimes over restrictive. Review collected by and hosted on G2.com.

- clear concept

- friendly UI

- speed fast

- on-the-fly form

- nice built-in model (page, image, document)

- SEO support

- streamfield

- hooks Review collected by and hosted on G2.com.

- quite poor documentation

- not so many built-in functions which support model handling

- revision Review collected by and hosted on G2.com.

In my 10+ years of experience as a web developer Wagtail is hands down the best CMS I've ever used or worked on. We've been using Wagtail in production for about a year in an organization with an annual budget of 4M. I thought winning over the content editors would be a challenge, instead they turned into huge advocates after the initial training.

But to leverage its full potential you really need to agree with the philosophy behind the technology. I've read other Wagtail reviews with the complaint that editors "cannot update the HTML code". This is by design. The philosophy (named The Zen of Wagtail) is in my opinion the best part of the CMS. You can read the official details here (http://docs.wagtail.io/en/latest/getting_started/the_zen_of_wagtail.html).

But to summarize:

The CMS should get content out of an admin/editors head and into a database as effortlessly as possible, the designer should call the shots on how things look (with html/css), and the programmer should be using a programming language (not a user interface).

That philosophy sounds basic: make things efficient for all roles involved. But it has lead to design decisions for how the CMS works that are just brilliant.

From an editor standpoint it is a dream come true. Every entry screen is custom coded to accept the data they need to enter. Custom data entry screens means the editor can make fast work of the task. And the editors I work with all agree that they really like this kind of system.

From a technology standpoint, this puts the programmer in control of a modern MVC platform that is designed to get stuff done quickly. And they get to use all the tools they're familiar with (git, python, database migrations, unit tests, etc).

The way the custom entry screens for the editors are built produce two outcomes: 1. they are ridiculously easy to build and 2. they keep all the design files (html/css) in a place that lets the designers modify them with ease. (We have web designers that do layout work.)

By recognizing the three roles and requiring them to work efficiently you get a race car of a CMS. Review collected by and hosted on G2.com.

Wagtail is a relative new comer, and even a year ago I was afraid it was more of a toy than a mature software product. I'm convinced that it is not a toy. And the problems that it solves are solved extremely well. However, being new means there isn't the plethora of pre-built components that are available from the PHP counterparts. The Awesome Wagtail list is okay (https://github.com/springload/awesome-wagtail) but I really wish there was an equivalent to wordpress.org/plugins. Review collected by and hosted on G2.com.

The streamfields feature radically simplifies the job of designing templates. You don't have to do so much work in advance, you can just create flexible page types and add the content you need. The interface itself is quick and enjoyable to use. Review collected by and hosted on G2.com.

As with any CMS there are a few features we wish were already included such as it being less possible for one user to overwrite another users's changes, etc (in my mind two editors shouldn't be able to open a page at once). Review collected by and hosted on G2.com.