Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
Currently it's possible to choose the url slug for the participatory spaces.
It would be great to be able to enter aliases (like it's possible on wordpress or drupal) so that we are able to communicate on simpler urls and get rid of the /processes/url-slug or assemblies/url-slug.
Furthermore /processes and /assemblies are english terms we cannot translate in i18n.
Ex : meta.decidim.org/roadmap/
Report inappropriate content
Is this content inappropriate?
9 comments
Conversation with Virgile Deville
@product can we get feedback on this please ?
huho seems like the @product doesn't work. Pinging @carol instead
Hi Virgile,
We've been discussing it with @andres. Technically it's tricky to get rid of /processes or /assemblies. There could be a situation where someone uses the alias, for example: meta.decidim.org/admin/ for a process, and then we would already have a problem.
One solution would be to shorten the names of the spaces, and instead of /processes or /assemblies we can leave /p or /a.
Hello @carol,
We did draw to the same technical conclusion. Unfortunately, our client seems eager to have a quotation on this one so we have to dig a little deeper ... and I'm pretty sure that they will reject this since it might be expensive to implements ...
Anyway, the goal here is to see if something could be merged to the core.
• The short space name path (/p instead of /processes) is definitely a good idea and we will make another dedicated proposal
• We will update this proposal with more detailed specs and an estimated quotation as soon as we finish our analysis
Hi @moustachu,
Ok, let us know when you have the updated proposal. Thanks!
@carol unexpectedly our client has accepted our proposal. We are going to work with Coditramuntana on this one. Most likely we'll be making an external module for this one. The approach so far :
+ Creation of external Module
+ Install Redirector Gem and modifiy to accept domain
+ Create a CRUD interface for admins to manage the redirect rules.
We will be discussing detailled specs on this issue https://github.com/OpenSourcePolitics/dev/issues/4
Pinging @paarals in here !
Requirements on this one should be :
• make a list of forbidden keywords for custom path ("admin", "processes", "signup" ...)
• custom path contains only one segment ( no "/" )
I think this could be solved by adding a centralized database table for all resources that can be linked to. Ideally, all resources that have a public URL would have a row in that table in which case the conflicts could be resolved simply by doing a lookup for the new URL in that table.
Alternatively, there could be a registry of "reserved" URL patterns that would cause the matches to these reserved patterns to cause a validation error on the proposed URLs.
As mentioned in the proposal, I would also very much like to have the possibility for unique multilingual URLs as well (for improved user experience and SEO), this has been requested many times:
Multilingual URLs for language versions
Add your comment
Sign in with your account or sign up to add your comment.
Loading comments ...