Dan Braghiș

That would be great. The biggest thing will be header markup and overall styling. At the moment we still retain the teal colours whereas the 4.0 UI is much lighter

> Not to question fundamentals too much but is there a particular reason why the translation editor is implemented in React? This was one of the first questions I had...

this was fixed in #602 and the follow up #613 It is far from feeling native, but it is much closer to the Wagtail 4.0 interface than before

Hey @hallpower, I... cannot reproduce this locally. See https://youtu.be/uWctc6HyOIY using a barebones Wagtail project (as in `wagtail start projectname`) with a `HomePage` and a `Partners` model simply inheriting from `Page`....

Thank you for pitching in, @enzedonline! We could improve documentation as a starting point. The `unique_together = ("translation_key", "locale")` constraint comes from core via `TranslatableMixin`. I feel that `TranslatableMixin` should...

@ruilvo thank you for the suggestion. A PR would very welcome too

@kaedroho if you have the time, then yes please!

The least invasive fix would be a try/except around ``` wagtail_localize/views/edit_translation.py", line 318, in get_segment_location_info field = source_instance._meta.get_field(field_path_components[0]) ``` Happy to review a PR

🪄 go for staging

:shipit: