[MGNLUI-2505] Add a prototype configuration valid for all content apps Created: 09/Dec/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: content app, framework
Affects Version/s: 5.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Obsolete 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)
Date of First Response:

 Description   

Currently, for content app, you have to configure even basic things such as the basic list of actions available. The idea of this improvement is to come up with a basic configuration for all content apps, which contains this basic list and possibly a set of additional, typical settings, which you could then extend and overwrite from. Kind of like the JS "prototypes".

Could we even extend this to regular apps as well?



 Comments   
Comment by Christopher Zimmermann [ 27/Jan/14 ]

While we are at it - maybe this would be a good time to simplify the delete actionbar items. So that its just one action instead of two (one for the confirmation, one for the delete.).

Comment by Andreas Weder [ 27/Jan/14 ]

Christopher: yes. If I'm getting this right, this is what Espen was talking about when he asked for chaining actions.

See here: http://wiki.magnolia-cms.com/display/UX/MGNLUI+Feedback#MGNLUIFeedback-General

As far as I know, there's no issue for this topic yet, though.

Comment by Roman Kovařík [ 09/Mar/21 ]

Implemented as "Content Types".

Generated at Mon Feb 12 08:57:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.