RFC: Backend translations about architecture

[balloob]

We will just need another script in the backend to upload translations to lokalise. I guess we should do that to a separate lokalise project. (but still just include the project in the frontend)

[andrey-git]

Unless I'm missing some missing something, I think (1) is much better.

First HA (backend) should be usable in non-English for users of UIs other than the official one.
Second, even for official UI it would be great if custom (backend) components were supported. If all texts come from lokalise - this is impossible.
Last, I think project separation is nice - i.e. don't mix frontend and backend where not necessary.

[balloob]

Option 1 👍

[balloob]

Since they are never shown in the backend, I think it's fine to keep them as part of the frontend. Let's just make sure that they can be loaded on demand.

With config entries we're going to have a lot of strings in the backend that need to be shown in the frontend. Although for now I have them as text, I plan on replacing them with translation keys before the official release of config entries.

[emlove]

So it sounds like we're leaning towards option 1?

@andrey-git's point about custom components certainly is enough to tip the scales for me. Updated the summary to also include @balloob's point that this will be a second project in Lokalise.