[MGNLCT-112] Augment external content in an app Created: 13/Feb/19 Updated: 02/Apr/19 |
|
| Status: | Open |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | 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)
|
| Release notes required: |
Yes
|
| Documentation update required: |
Yes
|
| Epic Link: | External Content |
| Description |
An author should be able to use the standard Magnolia editing tools on external content, but the external content is not changed, rather the changes (the "augmentation") is stored locally (in JCR). For example:
It should be possible to add additional fields (not just to change existing fields) to external items. (A developer would need to configure that additional fields are available.) For example:
Acceptance Criteria:
|