[MGNLCT-75] Too hard to tune the editor controls Created: 19/Sep/18 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Critical |
| 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)
|
| Epic Link: | Content Types evolution |
| Sprint: | later |
| Description |
|
User Story:
With current state of CT, the model definition is very easy and clear, but if a developer needs a small modification to the UI it is confusing because they need to provide configuration in a confusing way in an app definition file. Its important that evaluators are not confused or disappointed by complexity of common CT-related tasks in Magnolia, compared to our competitors products.
Acceptance Criteria:
Some things would ideally be tunable with CT - but dont make sense to tune in a "presentation" context because they actually affect the data model. Such as:
|