Follow up story of EZP-28811

Context

Even if there are discussions about SEO impacts with uppercase URLs, users generally prefer lowercase URLs.
The goal is to make lowercase URLs default configuration of the system

New project

When starting a new project, the system will use the default lowercase configuration.

Migration to new system URL

There are 3 cases during a software update:
Case 1: I want to keep the uppercase URL formatting.
Case 2: I don’t change anything (missed migration steps or not important)

Case 1:

ezpublish:
    url_alias:
        slug_converter:
            transformation: < urlalias >
            separator: 'dash'

No BC break.

Case 2:

ezpublish:
    url_alias:
        slug_converter:
            transformation: < urlalias_lowercase >
            separator: 'dash'

This configuration will end up with a mix of uppercase and lowercase URLs:

• new content objects will have lowercase URLs
• old content objects will have uppercease URLs
• updated content objects will have lowercase URLs

Edge case (will not be covered in this story)

Case 3: I want to use the lowercase urls now available despite my previous url where "anycase". As a developer I can use a script during migration to convert all my urls.
Case 3

ezpublish:
    url_alias:
        slug_converter:
            transformation: < urlalias_lowercase >
            separator: 'dash'

In order to not have mixed URLs, we need a script to convert all the old URLs (uppercase) to the new formatting (lowercase)

Documentation

We will have to document this change on the release notes and warn the developers to be careful about this.