Matjaž Horvat

Support for Django 3.2 (LTS) that we currently use ends at the end of March. Let's upgrade to the next LTS release - 4.2. Resources: https://docs.djangoproject.com/en/5.0/howto/upgrade-version/ https://medium.com/@awaisq/upgrade-django32-to-django42-d581d272540e

Showing the string list first is more natural, as it allows to pick the string to edit.

Since we're unable to fit the project and the resource name in the navigation bar.

To improve overall quality of the application and to reduce regressions, let's look into setting up some automated browser testing framework. Resources: https://www.selenium.dev/ https://www.browserstack.com/automate/

`UserProfile.custom_homepage` is currently stored as a `Locale.code` in a `CharField`. We could probably just use `ForeignKey(Locale)` instead, which would handle changes to locale codes gracefully among other things (see #3023)....

Sometimes TM entries contain bugs and only Admins can fix them. Managers and Translators, who can create entries, should at least be allowed to delete them. Ideally they should also...

Google Cloud Translations supports [batch requests](https://cloud.google.com/translate/docs/advanced/batch-translation). Let's see if we can make use of that for pretranslation.

https://pontoon.mozilla.org/insights/

We use Slate editor in Translate frontend for comments editor. We should unify all of our frontend rich editors to all use CodeMirror.

Example: https://pontoon.mozilla.org/sl/firefox-accounts/all-resources/?string=285663 We should convert multiline strings into single line ones before pretranslating them, same as we already did for Fluent in #2810.