What is the problem you are trying to solve?
When creating a new CSM Space in Liferay DXP, the system does not automatically assign a friendly URL that matches the Space’s name. Although it is technically possible to configure a friendly URL afterward, the current process is indirect and requires navigating to the associated Asset Library to get the name of space as /asset-library-3265 and modifying its friendly url by hack name replace for Site friendlyUrl configuration e.g. change it to /myspace. This workflow is unintuitive, requires multiple manual steps, and does not align with the user’s expectation that a Space’s friendly URL should be created automatically based on its name.
As a result, document URLs inside newly created Spaces are less readable and less predictable unless administrators perform additional configuration.
What is your project about?
The project involves a content‑centric solution built on Liferay DXP where CSM Spaces are used to organize documents and digital assets. Clean, human‑readable URLs are important for usability, navigation, and internal communication. The platform is used as an enterprise content management environment, where teams expect consistent URL patterns such as:
Kód
/documents/d/myspace/mydocument
To achieve this today, administrators must manually adjust the Asset Library’s Site name and friendly URL after the Space is created, which is not ideal for scalable or repeatable workflows and also is not guarantied to work as expeced
What is your proposed solution?
Introduce a native feature that automatically sets the friendly URL of a newly created CSM Space to match the Space’s name. This should happen directly during Space creation, without requiring any additional configuration in the Asset Library or Site settings.
Desired behavior:
-
Creating a Space named “MySpace” automatically results in a friendly URL:
Kód
/myspace -
Documents inside the Space automatically receive clean URLs such as:
Kód
http://localhost:8080/documents/d/myspace/mydocument
Benefits:
-
More intuitive and predictable URL structure
-
Reduced administrative overhead
-
Improved readability and user experience
-
Better alignment with modern content management expectations