Context

• Wagtail – is a popular CMS third party library that wraps around Django. It exists as a full suite of software to refine the admin and product tracking. It's a popular web framework on top of Django and highly leveraged in the enterprise Django space. They often have keynotes or major talks at Django Conferences, so integrating into this space would be a good way to garner interest from users.
• Bakery [Demo|https://github.com/wagtail/bakerydemo] – Is a specific Wagtail project – similar to the djangoproject.com tutorial – that flexes the main features and functions of Wagtail. Getting this to work serves two purposes:
  • It gives MongoDB users a clear guide on how to build a Wagtail application using the Django-MongoDB-Backend
  • It serves as a vetted (approved by the Wagtail dev team) method for figuring out any critical issues we would need to fix to ensure we are compatible with the Wagtail CMS library.
• Why we need to get this working
  • We cannot say we support Wagtail if the Bakery Demo cannot be complete. This is in response to the comments https://github.com/wagtail/wagtail/discussions/12843#discussioncomment-12222103.

Acceptance Criteria

Get the Wagtail Demo working with documentation on how to get it up and running (this can be in a cloneable repo or a DevRel article even). Once that is done, declare support for Wagtail CMS via, our MongoDB documentation, Django-MongoDB-Backend ReadTheDocs and django-mongodb-cli ReadTheDocs.

Pitfalls

• This is an EPIC level task. We need bucketed investigation time, technical design time, and possibly a GTM strategy once we get it functioning.
• We may rely on Wagtail core developers for upstream fixes
  • jib.adegunloye@mongodb.com cites they are willing to help, but first we need a working reference point.