[MURLTRANS-5] Allow translation for any workspace Created: 06/Sep/18 Updated: 21/Dec/23 |
|
| Status: | Open |
| Project: | URL Translation |
| Component/s: | None |
| Affects Version/s: | 5.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Currently the module is only for the website workspace. |
| Comments |
| Comment by Antony Hutchison [ 11/Oct/22 ] |
|
One consideration we would like taken into account for this improvement is that we have custom content apps that already use the property 'name'. I know it's configurable, but ideally it could be set per-workspace, so we can use 'name' in 'website', and define a different property in our 'services' app workspace. I also recommend changing it in the documentation from 'name' to something less generic, more specific for the semantic purpose, some suggestions: 'pageName' or 'urlName' or 'path' or 'urlPath'. Name has a specific meaning in JCR and in YAML that has the potential for confusion. |