This site uses cookies. By continuing to browse the site, you agree to our use of cookies. Find out more about cookies.
Skip to main content
Metadecidim's official logo
  • English Triar la llengua Elegir el idioma Choose language
    • Català
    • Castellano
Sign Up Sign In
  • Home
  • Processes
  • Assemblies
  • Initiatives
  • Consultations
  • Conferences
  • Help

Propose new functionalities for Decidim software

#DecidimRoadmap Designing Decidim together

Phase 1 of 1
Open 2019-01-01 - 2030-12-31
Process phases Submit a proposal
  • The process
  • Debates
  • Propose new features
  • News
chevron-left Back to list

Improve the UX for multi-lingual fields when the organization has multiple languages

Avatar: Marc Riera Marc Riera
30/04/2020 12:48  
Accepted / In progress

**Is your feature request related to a problem? Please describe.**

The current solution for multi-languages fields works well when the organization has 3, 4 or 5 languages, but we'll be working with a client that has a much higher number of languages, and the current solution does no escale

**Describe the solution you'd like**

We propose improving the UX for these fields and we have two suggestions:

  1. Use a dropdown per each field. This wouldn't change much of the current behavior, only that locales would be hidden in the dropdown.
  2. Use a dropdown for the whole form. On top of each form, show a dropdown that will change the fields shown to use the selected language version. Non-translatable fields will be shown anyway. This implies a bigger change of behavior and more work, dev-wise.

We're not sure about what's the best approach, or if we should find even another approach to this problem.

**Describe alternatives you've considered**

None.

**Additional context**

None.

**Does this issue could impact on users private data?**

No.

  • Filter results for category: Multi-language Multi-language

This proposal has been accepted and is under development

List of Endorsements

Avatar: Pau Parals Pau Parals verified-badge
Avatar: Pauline Bessoles Pauline Bessoles verified-badge
Avatar: Alexandru Emil Lupu Alexandru Emil Lupu
Endorsements count3
Improve the UX for multi-lingual fields when the organization has multiple languages Comments 1

Reference: MDC-PROP-2020-04-15239
Version number 2 (of 2) see other versions
Check fingerprint

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: aa49a1472398ed9242573c848d1c4abbedd1991cedc48867dfe5187df05ea18b

Source: {"body":{"en":"<p><strong>**Is your feature request related to a problem? Please describe.**</strong></p><p>The current solution for multi-languages fields works well when the organization has 3, 4 or 5 languages, but we'll be working with a client that has a much higher number of languages, and the current solution does no escale</p><p><strong>**Describe the solution you'd like**</strong></p><p>We propose improving the UX for these fields and we have two suggestions:</p><ol><li>Use a dropdown per each field. This wouldn't change much of the current behavior, only that locales would be hidden in the dropdown.</li><li>Use a dropdown for the whole form. On top of each form, show a dropdown that will change the fields shown to use the selected language version. Non-translatable fields will be shown anyway. This implies a bigger change of behavior and more work, dev-wise.</li></ol><p>We're not sure about what's the best approach, or if we should find even another approach to this problem.</p><p><strong>**Describe alternatives you've considered**</strong></p><p>None.</p><p><strong>**Additional context**</strong></p><p>None.</p><p><strong>**Does this issue could impact on users private data?**</strong>\r\n</p><p>No.</p>"},"title":{"en":"Improve the UX for multi-lingual fields when the organization has multiple languages"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

Share:

link-intact Share link

Share link:

Please paste this code in your page:

<script src="https://meta.decidim.org/processes/roadmap/f/122/proposals/15239/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/15239/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Report inappropriate content

Is this content inappropriate?

Reason

Comment details

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed
You are seeing a single comment

View all comments

Avatar: Carol Romero Carol Romero verified-badge
07/05/2020 13:00
  • Get link Get link

Thanks for the proposal @mrcasals! A priori I would say that the second option would be more comfortable to use from the translator/administrator's point of view. Maybe we can do some user testing when the development progresses to make a decision

Loading comments ...

  • Terms and conditions of use
  • About the community
  • Download Open Data files
  • Metadecidim at Twitter Twitter
  • Metadecidim at Instagram Instagram
  • Metadecidim at YouTube YouTube
  • Metadecidim at GitHub GitHub
Creative Commons License Website made with free software.
Decidim Logo

Confirm

OK Cancel

Please sign in

decidim Sign in with Decidim Barcelona
Or

Sign up

Forgot your password?