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

Multilingual URLs for language versions

Avatar: Antti Hukkanen Antti Hukkanen
16/04/2020 10:12  

**Is your feature request related to a problem? Please describe.**
Currently the different language versions are indicated using a URL parameter, e.g. "?locale=fi". This is not optimal for:

  • The user, they generally do not understand what these are and they may remove the relevant information from the URL when they copy-paste it somewhere
  • Google, as they say different URLs should be used for different langauge versions: https://support.google.com/webmasters/answer/182192?hl=en
  • Marketing, e.g. when you write the service URL to a marketing banner, e.g. "Participate now at meta.decidim.org/es" looks much nicer than "Participate now at meta.decidim.org?locale=es".


We have been also requested that each section could also have different URL names, e.g. "meta.decidim.org/processes" would be "meta.decidim.org/fi/prosessit" in the Finnish version. Some accessibility experts claim that this is even required for accessible services. Pretty standard feature in many CMS systems but this is is completely another problem that boils down to the overall improvement of the CMS features in Decidim:

  • Allow defining static page content using the content blocks
  • Allow adding multiple same type of content blocks on page
  • Possibility to configure the top level navigation
  • Possibility to configure the participatory space navigation
  • Adding icons to pages and topics


**Describe the solution you'd like**
The primary (default) language URLs should be intact as they are now.

The secondary languages should be indicated with a sub-path in the URL, such as "meta.decidim.org/es/...".

Implementing this also requires adding 301 redirections to the old parameter URLs, so that old Google results, social media shares and document links will still point to the correct location.

**Describe alternatives you've considered**
There are really no alternatives as the suggested is the accepted common "standard" / convention for defining language versions in public web. Common conventions should be followed as that makes the overall experience better for everyone, people and machines. This will also bump the site's SEO relevance.

You can of course add redirections manually for the sub-path URLs simply for marketing purposes but this seems clunky and it's not the right way to go.

**Additional context**
The URL parameter convention may be acceptable for services which are not facing the public web, i.e. they require logging in from the user.

However, for system such as Decidim, we should follow the commonly accepted convention for public websites as most of Decidim's content is meant to be visible in the public web.

This issue applies to multiple categories (but I can only select one):

  • UX / PX / Usability
  • Accessibility
  • SEO / Search Engine

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

  • Filter results for category: PX (Participant eXperience) / Usability PX (Participant eXperience) / Usability

List of Endorsements

Avatar: Pauline Bessoles Pauline Bessoles verified-badge
Endorsements count1
Multilingual URLs for language versions Comments 0

Reference: MDC-PROP-2020-04-15227
Version number 1 (of 1) 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: 6d3ac6682de18436d6f41ae32d95ce6019c3f44ac11f04e17fe80825063d3a97

Source: {"body":{"en":"<p>**Is your feature request related to a problem? Please describe.**\r\nCurrently the different language versions are indicated using a URL parameter, e.g. \"?locale=fi\". This is not optimal for:</p><ul><li>The user, they generally do not understand what these are and they may remove the relevant information from the URL when they copy-paste it somewhere</li><li>Google, as they say different URLs should be used for different langauge versions: <a href=\"https://support.google.com/webmasters/answer/182192?hl=en\" target=\"_blank\">https://support.google.com/webmasters/answer/182192?hl=en</a></li><li>Marketing, e.g. when you write the service URL to a marketing banner, e.g. \"Participate now at meta.decidim.org/es\" looks much nicer than \"Participate now at meta.decidim.org?locale=es\".</li></ul><p><br></p><p>We have been also requested that each section could also have different URL names, e.g. \"meta.decidim.org/processes\" would be \"meta.decidim.org/fi/prosessit\" in the Finnish version. Some accessibility experts claim that this is even required for accessible services. Pretty standard feature in many CMS systems but this is is completely another problem that boils down to the overall improvement of the CMS features in Decidim:</p><ul><li><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/14371\" target=\"_blank\">Allow defining static page content using the content blocks</a></li><li><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/14370\" target=\"_blank\">Allow adding multiple same type of content blocks on page</a></li><li><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/13126\" target=\"_blank\">Possibility to configure the top level navigation</a></li><li><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/14319\" target=\"_blank\">Possibility to configure the participatory space navigation</a></li><li><a href=\"https://meta.decidim.org/processes/roadmap/f/122/proposals/15219\" target=\"_blank\">Adding icons to pages and topics</a></li></ul><p><br></p><p>**Describe the solution you'd like**\r\nThe primary (default) language URLs should be intact as they are now.</p><p>The secondary languages should be indicated with a sub-path in the URL, such as \"meta.decidim.org/es/...\".</p><p>Implementing this also requires adding 301 redirections to the old parameter URLs, so that old Google results, social media shares and document links will still point to the correct location.\r\n\r\n**Describe alternatives you've considered**\r\nThere are really no alternatives as the suggested is the accepted common \"standard\" / convention for defining language versions in public web. Common conventions should be followed as that makes the overall experience better for everyone, people and machines. This will also bump the site's SEO relevance.</p><p>You can of course add redirections manually for the sub-path URLs simply for marketing purposes but this seems clunky and it's not the right way to go.\r\n\r\n**Additional context**\r\nThe URL parameter convention may be acceptable for services which are not facing the public web, i.e. they require logging in from the user.</p><p>However, for system such as Decidim, we should follow the commonly accepted convention for public websites as most of Decidim's content is meant to be visible in the public web.</p><p>This issue applies to multiple categories (but I can only select one):</p><ul><li>UX / PX / Usability</li><li>Accessibility</li><li>SEO / Search Engine</li></ul><p>\r\n\r\n**Does this issue could impact on users private data?**\r\nNo.</p>"},"title":{"en":"Multilingual URLs for language versions"}}

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/15227/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/15227/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Report inappropriate content

Is this content inappropriate?

Reason

0 comments

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed

Add your comment

Sign in with your account or sign up to add your comment.

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
Or

Sign up

Forgot your password?