[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:

As a developer or business analyst, I want to easily specify details for how the controls should be presented in the GUI, so that I can succeed in fulfilling my business requirements.

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:

  • Developer can tune the GUI of the controls in the same file as the CT model definition.
  • Controls are tuned with the same properties as the normal FieldTypeDefinitions.
  • The following GUI items can be achieved:
    • Field types
      • Tags
      • Twin Column (Multiselect)
      • Option group (Radio buttons)
      • Password
      • Code
    • Validation
      • HTML validation (email, phone, etc)
    • Rows property for Text input.
    • Tuning content previews (contentPreviewDefinition)
    • Specify "targetTreeRootPath"
    • Specify "fieldEditable"

 

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:

  • Tuning data storage (identifierToPathConverter)

 


Generated at Mon Feb 12 00:36:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.