The native TableBlock that ships with Wagtail is great, but sometimes we need to go deeper.
On being pleasantly surprised when using some new tech.
I built my first website in June 1996, and I haven't looked back. Until now of course.
Multilingual Wagtail sites need a little help to conform to the Google Search Console sitemap format - here's how to do it.
Enhance the CMS UX experience when using Wagtailtrans by adding action menu buttons to edit translated page siblings.
Write a little extra code to help your CMS editors navigate the maze of content editing.
Design your editing screens to help guide a new editor through the process as much as possible from the start.
Keep everyone happy by making everything editable, reducing the need for developer input into minor text changes.
Keep your UI field names simple for the CMS editor, whilst protecting against namespace collisions in the code.
Ease the cognitive load by reusing familiar patterns.
Tips which I find make life that little bit easier and understandable for CMS editors, and hopefully lead to better websites all round.
Ever wanted to pass a dynamic queryset to a Wagtail FieldPanel instead of static choices? Here's how to do it.
Adventures in adding a new footnote entity type to the native Wagtail rich text editor, Draftail.
Some thoughts on coming out of a seven year long stint as owner and technical director of UX agency fffunction.