[MGNLCT-167] DOC: Developer do not know how to use content types in 6.2 Created: 26/Nov/20  Updated: 03/May/23  Resolved: 03/May/23

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Martin Drápela
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:
Story Points: 3
Team: DeveloperX

 Description   

So far I have seen two external developers struggling with not knowing how to use content types on 6.2. 

Here is one example: https://groups.google.com/a/magnolia-cms.com/g/user-list/c/6OCJFiFqWcc/m/q1I2N39yAgAJ

Please review the documentation on Content types

Ensure that the following 2 cases are met:

  • As a developer using Magnolia 6.2+ I know how to work with content types which generate M6UI apps.
  • As a developer migrating a project to 6.2+, I know how to make my old apps and content types work with minimal changes - AND I know how to convert them to M6UI apps.


 Comments   
Comment by Christopher Zimmermann [ 26/Nov/20 ]

I see that it is documented here: 
https://documentation.magnolia-cms.com/display/DOCS62/Content+type+Model+definition#ContenttypeModeldefinition-MigratingCT-baseddefinitions

But then probably this needs to be more prominent, and probably also include an example of "!content-type", not just of "!content-type-m5".

Comment by Christopher Zimmermann [ 26/Nov/20 ]

Should at least be mentioned on these pages:

https://documentation.magnolia-cms.com/display/DOCS62/Changes+in+Magnolia+6+UI

https://documentation.magnolia-cms.com/display/DOCS62/Migrating+an+app+to+Magnolia+6+UI

 

Comment by Martin Drápela [ 26/Nov/20 ]

We also mention that here:

https://documentation.magnolia-cms.com/display/DOCS62/Upgrading+to+Magnolia+6.2.x#UpgradingtoMagnolia6.2.x-Migratingcontenttypebaseddefinitions

In Magnolia 6.2.x, the !content-type directive generates a Magnolia 6 UI app. This means that any overriding or decoration of a content-type based app needs to be updated to match the 6 UI. As an alternative, you can use the new !content-type-m5 directive, which generates a 5 UI app.

 

But let's make it more prominent on a page whose focus is not on Upgrading.

I'd probably also add it here: https://documentation.magnolia-cms.com/display/DOCS62/App+descriptor

Comment by Christopher Zimmermann [ 03/May/23 ]

Closing as obsolete. Not relevant now, vast majority of projects are on 6.2. And documengtation on migrating to 6..2 exists now as well.

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