# Feature COMMS-1104 - Add document title slug to URLs

Project: Stream Communicator
Status: in specification
URL: https://community.openproject.org/work_packages/COMMS-1104

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Documents |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a user getting a link to a document  
**I want to** see right from the link what the document is about  
**so that** I don't have to click the link to know what the document is about

Example: [https://community.openproject.org/documents/143-sprint-ideation](https://community.openproject.org/documents/143-sprint-ideation) instead of [https://community.openproject.org/documents/143](https://community.openproject.org/documents/143)

**Acceptance criteria**

*   document links include the title as slug behind the ID (so that when a document is open in the browser, the document title slug is added behind the ID in the URL)
    
*   resolving the document is only done by the ID; opening a link with an outdated slug works fine
    
*   the slugified title only uses `a-z`, `A-Z`, `0-9`, `-`, spaces are replaced by `-` . All other special characters are stripped
    
*   anchors in documents still work well
    
*   **tbd**: Do we want to add the project identifier to the URL as well? In case of semantic identifiers this also carries meaning, but makes the URL longer.
    

**Technical notes**

*   prefer to use some standard slugify method over building something own