[MGNLRES-229] Rethink actions in resource app Created: 29/Sep/15 Updated: 29/Mar/22 Resolved: 21/Oct/15 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Epic Link: | Phase out in-place templating app |
| Sprint: | Basel 15 |
| Story Points: | 2 |
| Team: |
| Description |
|
The resources app (since 2.4) uses its own flavors of Container/Items, based on the new resources APIs from Magnolia 5.4. We currently customize almost every action and workbench component for this purpose, just to do one same thing:
It feels quite sub-optimal; we're looking for a more elegant approach to arouse reuse of the content-app framework altogether, for JCR resources (thus removing need for most action & component customizations). |
| Comments |
| Comment by Mikaël Geljić [ 21/Oct/15 ] |
|
Too late, therefore no longer critical; we reached a level where current app is consistent. |