Closed friep closed 11 months ago
Generally this comes from the city
attribute in directus, so I think there are two options.
The second approach would also allow us to be a little more lenient when processing slugs. We could for instance allow both "Berlin" and "berlin" (or even BERLIN etc.) although this would only become relevant if the user types the city manually instead of using the links.
i'd prefer 2. because i think 1. could potentially have unexpected side effects (e.g. when we need the city name in other parts of the site)
Agreed, lets do 2. In the end the capitalized versions are the proper names after all, so it makes sense that the CMS stores these. Any name mangling is essentially business logic on and should go into the code.
I deployed the general feature that the lc city names etc. are lowercase in the url, and the internal
Currently the static page does not feature routes that are differently capitalized, i.e. Berlin
or BERLIN
instead of berlin
. The preview site already features a little bit of this logic, but this does not transfer directly to the static build. Do we also want multiple capitalization options as a feature. If so, I see three options for this.
I think all lower case would be sufficient for Isabel and me. this is how it is now on production right? then we can close this issue.
https://correlaid.org/community/correlaidx/berlin is not found, only https://correlaid.org/community/correlaidx/Berlin . for the sake of consistency and easier writing, i think we should lowercase the names in the urls.