[MGNLDAM-809] New assets app UX polish Created: 25/Oct/19 Updated: 23/Oct/20 Resolved: 24/Feb/20 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Anja von Gunten | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d 58m | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | Migrate apps to new UI framework | ||||||||||||||||||||||||||||||||||||
| Sprint: | UI Framework 16, UI Framework 17 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||||||
| Description |
|
A few polish items to ensure a smooth UX:
Magnolia Assets
3rd party DAMS naming
See also UX guidelines for migrated apps at https://wiki.magnolia-cms.com/display/DEV/Migration+of+Magnolia+stock+apps+to+M6
|
| Comments |
| Comment by Roman Kovařík [ 09/Dec/19 ] |
|
For the record, most of these issue might be solved by extracting JCR part as a separate app. |
| Comment by Roman Kovařík [ 17/Dec/19 ] |
Only JCR has an activation state, other asset providers don't have such state for its items.
As this browser is read only, which actions it should have?
Doesn't 2. solves 1. and 3.? And in the end it actually means that JCR assets app could be separated which would solve all the issues. For the assets chooser it would still use the dam-all app, just dam-all doesn't have to be in the app launcher. The biggest problem when mixing multiple browsers is returning to the first tab after closing a provider specific detail.E.g
That is good idea (no matter if we decide to have separate apps or just subapps). |