Use Case or Problem
In Obsidian Publish, the alias functionality allows users to access pages via simplified URLs, such as www.beto.group/about. While this provides an intuitive way to navigate to pages, the browser’s address bar reverts to displaying the full file path upon page load, such as https://www.beto.group/888/PROJECTS/888/_OPERATION/PUBLIC/ABOUT.
This behavior undermines the purpose of aliases, as the full file path is not user-friendly, makes URLs harder to share, and detracts from the professional appearance of published sites. Users expect the alias-based URL to remain consistent in the address bar for a better user experience.
Proposed Solution
Introduce a feature within the Obsidian Publish settings that includes a toggle to enable persistent alias-based URLs. When this setting is enabled, the URL displayed in the address bar would remain as the alias (e.g., www.beto.group/about) throughout the user’s interaction with the page, regardless of the file’s actual location or file path in the vault.
This solution would ensure that the user-defined aliases are reflected in the URLs consistently, enhancing readability, usability, and shareability without additional complexity for users.
Current Workaround
Currently, there is no workaround for maintaining persistent alias-based URLs. Users can only use aliases to navigate to pages, but the browser reverts to displaying the full file path once the page is loaded.
Related Feature Requests
The Obsidian Forum previously discussed the ability to specify permalinks in frontmatter. This feature introduced aliases to simplify navigation and create user-friendly, shareable URLs. However, aliases currently revert to full file paths upon page load, limiting their effectiveness.
Conclusion
Allowing persistent alias-based URLs in Obsidian Publish would fully realize the potential of aliases, improving both usability and professionalism for content creators and their audiences.
Best regards,
b.
b.