Easier URLs by permalinks
Is your feature request related to a problem? Please describe. At the moment in collectives the URLs are built from titles of the collectives and of the pages: https://nextcloud-instance.com/index.php/apps/collectives/new%20collective/New%20Page This is very easy but has two big disadvantages imho: 1. urls built with blanks and/or umlauts (which are quite frequent in German e.g.) work but are very ugly and more important: people which are not very familiar with code are confused by that. 2. If you dynamically develop your knowledge base in a team, titles of pages for some time change quite often, what leads to changed URLs. Yes, URLs still works after changing them, thanks to ?fileId= but they would be much easier, pleasing and less technical without that.
So all in all I would like to say that the URLs at the moment come with some barriers in usage, which could (hopefully) easily avoided by introducing permalinks
Describe the solution you'd like
- Add a permalink field directly underneath the title-field of pages. The field should be filled automatically from the title-field. blanks should be replaced by en-dashes, german umlaut ä by ae, ö by oe, ü by ue and ß by ss (don't know that for other languages).
- Maybe the easiest way would be a checkbox right besides this field to fix the link als permalink. The alternative would be a general setting within collectives app settings or within the settings of each collective.
- After fixing the link als permalink a change of the title should not result in a change of the URL anymore. But it must be possible to change the permalink manually by editing it in the permalink-field. Maybe a dialog „are your sure to change the permalink“ should appear.
- The same permalink field for the collectiges name should be place in the collective’s settings.
- Additional I would be happy with an option to disable the fileId-addition of urls.
This way collectives could get even more powerful and the use of collectives as knowledge base would get even nicer and easier for lot of people (at least if the contents are well maintained).
What do you think? Could that come reality in the not so far future? (I will be glad to help testing but cannot code…)
Describe alternatives you've considered —
Additional context —
btw I just realized another problem which could occur with the actual solution: If you publish an URL just to a collective and not to page there is no fileID. So change of the collective’s name could lead to not working URLs.
Still no opinions on this?
We're pondering to support app/collectives/CollectiveName/_f/FileId as a short permalink per page.
The link could be copied from a hint in the user interface.
That would be fine. But even better would be (additional) the ability to make user defined permalinks using short terms for Collectives' names as well as for pages.
e.g. the collective titled "Introduction for new colleagues" could be defined as /intro/ in the URL.