This is a Feature Proposal

🎩 Description

• What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.

Currently, for a translated field all languages are required. This can cause problems sometimes:

• An admin wants to create a process but does not know some of the required languages, so the process cannot be created.

Currently, organizations have a default_locale and some available_locales. We should make the translations for the default_locale required, and any other language should be optional. When accessing a locale that does not have an explicit translation, we should fallback to the default_locale and render that content.

These changes affect the form validations and the translated_attribute helper that renders the translated content in the views.

📌 Related issues

https://github.com/AjuntamentdeBarcelona/decidim/issues/1126#issuecomment-286757298 and talked offline with @josepjaume a few times too.

📋 Additional Data

None